NetworkAccessProfile Resource
Control which mobile networks Super SIMs can connect to
Last updated
Was this helpful?
API Reference
Control which mobile networks Super SIMs can connect to
Last updated
Was this helpful?
NetworkAccessProfile resources control which public land mobile networks (PLMNs) your Super SIMs can connect to:
A NetworkAccessProfile resource can be referenced in the API by either by its unique Sid or UniqueName:
Each NetworkAccessProfile (NAP) resource has a Networks subresource (NAP Networks):
Each NAP Network resource represents a cellular network that Super SIMs can connect to — an allowed Network.
The allowed networks represented by the NAP Network resources will be a subset of all of the networks supported by Super SIM represented by the Network resources returned from the main Networks endpoint. You can add or remove NAP Network resources from the NAP Networks subresource at any time to change which cellular networks your Super SIMs can access.
If your Super SIM has already attached to a network, authentication and authorization information may be cached in that network to allow devices to continue to use that network without re-authenticating with our services. When you disable a network in a NAP, it may not take immediate effect for that Super SIM. The cached information for that Super SIM will need to expire before the Super SIM can no longer use that network. This may take up to a week, but varies by network.
To make use of a NetworkAccessProfile resource, it needs to be referenced by a Fleet resource. All of the Sim resources assigned to that Fleet will then e able to attach to the cellular networks allowed by the NetworkAccessProfile's Networks subresource.
A NetworkAccessProfile can be used by multiple Fleet resources.
The NAP Networks subresource serves as an allow list of the cellular networks to which Super SIMs can connect. Networks not present in the NAP Networks subresource are therefore blocked (i.e., forbidden).
When your device scans for available cellular networks to attempt to attach to, it may find a number of cellular networks. Super SIMs can only attach to a cellular network if the Network resource that represents the cellular network is present in a NAP's Networks subresource. If your device explicitly tries to attach to a cellular network that has not been allowed, the network will return the error 5004 / ROAMING_NOT_ALLOWED.
There will be some cellular networks for which there is no Network resource available. As such there is no way to add them to the list of allowed cellular networks in a NetworkAccessProfile resource. No Super SIMs will be able to attach to these cellular networks.
New Feature Customers can now delete unused and unwanted NAPs and their associated data. This can be done in Console: visit Super SIM > Network Access Profiles, click on the name of the NAP you wish to delete, and click the Delete Network Access Profile link at the bottom of the page. You will be asked to confirm your action before the NAP is deleted. NAPs which are currently assigned to Fleets cannot be deleted.
Create a new Network Access Profile
An application-defined string that uniquely identifies the resource. It can be used in place of the resource's sid in the URL to address the resource.
List of Network SIDs that this Network Access Profile will allow connections to.
Created
Fetch a Network Access Profile instance from your account.
The SID of the Network Access Profile resource to fetch.
OK
Retrieve a list of Network Access Profiles from your account.
How many resources to return in each list page. The default is 50, and the maximum is 1000.
The page index. This value is simply for client state.
The page token. This is provided by the API.
OK
Updates the given properties of a Network Access Profile in your account.
The SID of the Network Access Profile to update.
The new unique name of the Network Access Profile.
OK
Before you can make requests to this resource, you must have a valid bearer token. Review our API to learn how to generate a token. Here's a curl example on how to define your access token in a header:
The examples below do not show the required Authorization header due to a bug. We're working on fixing that. In the meantime, be sure to include that in all of your requests.
