Stay organized with collections
Save and categorize content based on your preferences.
On Android 10 and higher, the Wi-Fi infrastructure includes the Wi-Fi suggestion
API for internet connectivity and the Wi-Fi network request API for peer-to-peer
connectivity. On Android 11 and higher, the Settings Intent API lets you
ask the user to approve adding a saved network or Passpoint configuration.
APIs
The three APIs target different use cases and have different capabilities and
constraints:
Suggestion API: targets apps that
provision and provide internet-capable configurations. These configurations
are not individually owned by the user. Users can disable specific
configurations or disable the suggesting app, but can't delete
them.
User approval is required per app, not per network suggested by the app.
Intended for carrier Wi-Fi offload configuration apps and other apps that
may actively manage offload networks.
Network request API: targets
apps that need to connect to a peer device, such as when configuring an IoT
device or transferring files to a camera. In such cases, the peer device
starts up a SoftAP and the API allows the app to guide the user to connect to
the device. The resulting network is not intended to provide internet access,
can't be used by the system, and can't be used by any app except the
configuring app.
User selection and approval is required the first time a connection is made
to a new peer.
Intended for IoT configuration apps and IoT file transfer apps.
ACTION_WIFI_ADD_NETWORKS
API: allows
apps (with user approval) to add networks or Passpoint configurations to the
saved network or subscription list. These configurations are then treated as
if the user added them directly. For example, the user can later delete them.
User approval is required for every request to add saved networks.
Intended for apps that configure a home Access Point and need to add the
configuration to the user's saved network list. Apps that provision a
user-account Passpoint configuration, such as Enterprise, federated
networks, and educational institutions.
Secure Wi-Fi Enterprise configuration
On Android 11 QPR1 and higher, the system mandates strict security
configurations for TLS-based Wi-Fi Enterprise connections. For more
information, see
Secure Wi-Fi Enterprise configuration.
Content and code samples on this page are subject to the licenses described in the Content License. Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
Last updated 2025-08-26 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-26 UTC."],[],[],null,["On Android 10 and higher, the Wi-Fi infrastructure includes the Wi-Fi suggestion\nAPI for internet connectivity and the Wi-Fi network request API for peer-to-peer\nconnectivity. On Android 11 and higher, the Settings Intent API lets you\nask the user to approve adding a saved network or Passpoint configuration.\n\nAPIs\n\nThe three APIs target different use cases and have different capabilities and\nconstraints:\n\n- [Suggestion API](/develop/connectivity/wifi/wifi-suggest): targets apps that\n provision and provide internet-capable configurations. These configurations\n are not individually owned by the user. Users can disable specific\n configurations or disable the suggesting app, but can't delete\n them.\n\n - User approval is required per app, not per network suggested by the app.\n - Intended for carrier Wi-Fi offload configuration apps and other apps that may actively manage offload networks.\n- [Network request API](/develop/connectivity/wifi/wifi-bootstrap): targets\n apps that need to connect to a peer device, such as when configuring an IoT\n device or transferring files to a camera. In such cases, the peer device\n starts up a SoftAP and the API allows the app to guide the user to connect to\n the device. The resulting network is not intended to provide internet access,\n can't be used by the system, and can't be used by any app except the\n configuring app.\n\n - User selection and approval is required the first time a connection is made to a new peer.\n - Intended for IoT configuration apps and IoT file transfer apps.\n- [`ACTION_WIFI_ADD_NETWORKS`\n API](/develop/connectivity/wifi/wifi-save-network-passpoint-config): allows\n apps (with user approval) to add networks or Passpoint configurations to the\n saved network or subscription list. These configurations are then treated as\n if the user added them directly. For example, the user can later delete them.\n\n - User approval is required for every request to add saved networks.\n - Intended for apps that configure a home Access Point and need to add the configuration to the user's saved network list. Apps that provision a user-account Passpoint configuration, such as Enterprise, federated networks, and educational institutions.\n\n| **Note:** These APIs are a replacement for the deprecated `WifiManager.addNetwork(WifiConfiguration config)` and related APIs. The other deprecated APIs allowed apps to directly add and manage a Wi-Fi configuration in the saved network list. The replacement APIs provide use-case-targeted alternatives.\n\nSecure Wi-Fi Enterprise configuration\n\nOn Android 11 QPR1 and higher, the system mandates strict security\nconfigurations for TLS-based Wi-Fi Enterprise connections. For more\ninformation, see\n[Secure Wi-Fi Enterprise configuration](/develop/connectivity/wifi-enterprise)."]]
