Fleet Resource
Organize and configure groups of Sim resources
Last updated
Organize and configure groups of Sim resources
Last updated
To avoid ambiguity throughout this page, Sim (initial cap) refers to the Sim API resource. SIM (all caps) refers to the physical Subscriber Identity Module (that is, a SIM card) associated with a Sim resource.
A Fleet resource organizes and configures group of Sim resources:
A Sim resource must be assigned to a Fleet resource by specifying fleet on the Sim resource before it can activated.
Some of a Fleet resource's properties are immutable. If you wish to change a Super SIM's behavior, you may need to create a new Fleet resource and reassign the Sim resource to the new Fleet resource.
Data limits allow you to limit how much data each Super SIM assigned to a Fleet can consume during each SIM's billing period (typically 1 month). Once the SIM has used more than its allowed data limit, it will be blocked from exchanging additional data until the current billing period expires. When a new billing period begins, the amount of data used towards the limit resets to 0 and the SIM is unblocked (if it was previously blocked).
Each SIM's data usage is measured independently and each gets the full amount of the data limit to consume before being blocked. For example, if you set the data limit on your Fleet resource to 5MB, every SIM assigned to that Fleet gets its own 5MBs of data to use. It is not a shared pool of data.
SIMs will not be blocked exactly at their data limit. Usage records are generated every 6 minutes while a data session is active or when the session terminates. The aggregated usage from these is used to evaluate if a SIM has exceeded its data limit. If your device uses a significant amount of data between usage records being generated, it is possible to exceed your data limit by large amounts. You will be charged for all data used by your devices.
If you update your Fleet's data limit, it will take a few moments, typically five minutes or less, for the Super SIMs assigned to that Fleet to respect the new data limit while the cached value expires. If you increase the data limit and have SIMs that are blocked because their data usage exceeded the previous data limit, they will automatically be unblocked when the new data limit takes effect. Similarly, SIMs whose data usage for the current billing period exceeds the new data limit will be blocked, if they were not already, when the new data limit takes effect. It should not take longer than 15minutes for the new data limit to take effect for all of the Super SIMs on your Fleet.
You can use the BillingPeriods subresource and UsageRecords resource to calculate how much of a SIM's data limit has been used. See more details here.
Customers can now delete unused and unwanted Fleets and their associated data. This can be done in Console: visit Super SIM > Fleets, click on the name of the Fleet you wish to delete, and click the Delete Fleet link at the bottom of the page. You will be asked to confirm your action before the Fleet is deleted. Fleets to which SIMs are currently assigned cannot be deleted.
Before you can make requests to this resource, you must have a valid bearer token. Review our API authorization guide 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.
Create a Fleet
The SID or unique name of the Network Access Profile that will control which cellular networks the Fleet's SIMs can connect to.
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.
Defines whether SIMs in the Fleet are capable of using 2G/3G/4G/LTE/CAT-M data connectivity. Defaults to true.
The total data usage (download and upload combined) in Megabytes that each Super SIM assigned to the Fleet can consume during a billing period (normally one month). Value must be between 1MB (1) and 2TB (2,000,000). Defaults to 1GB (1,000).
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an IP Command from your device to a special IP address. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to ip_commands_url. Can be one of POST or GET. Defaults to POST.
Defines whether SIMs in the Fleet are capable of sending and receiving machine-to-machine SMS via Commands. Defaults to true.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an SMS from your device to the SMS Commands number. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to sms_commands_url. Can be one of POST or GET. Defaults to POST.
Created
The SID of the Account that created the Fleet resource.
^AC[0-9a-fA-F]{32}$The unique string that we created to identify the Fleet resource.
^HF[0-9a-fA-F]{32}$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.
The date and time in GMT when the resource was created specified in ISO 8601 format.
The date and time in GMT when the resource was last updated specified in ISO 8601 format.
The absolute URL of the Fleet resource.
Defines whether SIMs in the Fleet are capable of using 2G/3G/4G/LTE/CAT-M data connectivity. Defaults to true.
The total data usage (download and upload combined) in Megabytes that each Super SIM assigned to the Fleet can consume during a billing period (normally one month). Value must be between 1MB (1) and 2TB (2,000,000). Defaults to 250MB.
Defines whether SIMs in the Fleet are capable of sending and receiving machine-to-machine SMS via Commands. Defaults to false.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an SMS from your device to the SMS Commands number. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to sms_commands_url. Can be one of POST or GET. Defaults to POST.
The SID of the Network Access Profile that controls which cellular networks the Fleet's SIMs can connect to.
^HA[0-9a-fA-F]{32}$The URL that will receive a webhook when a Super SIM in the Fleet is used to send an IP Command from your device to a special IP address. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to ip_commands_url. Can be one of POST or GET. Defaults to POST.
Fetch a Fleet instance from your account.
The SID of the Fleet resource to fetch.
OK
The SID of the Account that created the Fleet resource.
^AC[0-9a-fA-F]{32}$The unique string that we created to identify the Fleet resource.
^HF[0-9a-fA-F]{32}$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.
The date and time in GMT when the resource was created specified in ISO 8601 format.
The date and time in GMT when the resource was last updated specified in ISO 8601 format.
The absolute URL of the Fleet resource.
Defines whether SIMs in the Fleet are capable of using 2G/3G/4G/LTE/CAT-M data connectivity. Defaults to true.
The total data usage (download and upload combined) in Megabytes that each Super SIM assigned to the Fleet can consume during a billing period (normally one month). Value must be between 1MB (1) and 2TB (2,000,000). Defaults to 250MB.
Defines whether SIMs in the Fleet are capable of sending and receiving machine-to-machine SMS via Commands. Defaults to false.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an SMS from your device to the SMS Commands number. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to sms_commands_url. Can be one of POST or GET. Defaults to POST.
The SID of the Network Access Profile that controls which cellular networks the Fleet's SIMs can connect to.
^HA[0-9a-fA-F]{32}$The URL that will receive a webhook when a Super SIM in the Fleet is used to send an IP Command from your device to a special IP address. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to ip_commands_url. Can be one of POST or GET. Defaults to POST.
Retrieve a list of Fleets from your account.
OK
Updates the given properties of a Super SIM Fleet instance from your account.
The SID of the Fleet resource to update.
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.
The SID or unique name of the Network Access Profile that will control which cellular networks the Fleet's SIMs can connect to.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an IP Command from your device to a special IP address. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to ip_commands_url. Can be one of POST or GET. Defaults to POST.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an SMS from your device to the SMS Commands number. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to sms_commands_url. Can be one of POST or GET. Defaults to POST.
The total data usage (download and upload combined) in Megabytes that each Super SIM assigned to the Fleet can consume during a billing period (normally one month). Value must be between 1MB (1) and 2TB (2,000,000). Defaults to 1GB (1,000).
OK
The SID of the Account that created the Fleet resource.
^AC[0-9a-fA-F]{32}$The unique string that we created to identify the Fleet resource.
^HF[0-9a-fA-F]{32}$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.
The date and time in GMT when the resource was created specified in ISO 8601 format.
The date and time in GMT when the resource was last updated specified in ISO 8601 format.
The absolute URL of the Fleet resource.
Defines whether SIMs in the Fleet are capable of using 2G/3G/4G/LTE/CAT-M data connectivity. Defaults to true.
The total data usage (download and upload combined) in Megabytes that each Super SIM assigned to the Fleet can consume during a billing period (normally one month). Value must be between 1MB (1) and 2TB (2,000,000). Defaults to 250MB.
Defines whether SIMs in the Fleet are capable of sending and receiving machine-to-machine SMS via Commands. Defaults to false.
The URL that will receive a webhook when a Super SIM in the Fleet is used to send an SMS from your device to the SMS Commands number. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to sms_commands_url. Can be one of POST or GET. Defaults to POST.
The SID of the Network Access Profile that controls which cellular networks the Fleet's SIMs can connect to.
^HA[0-9a-fA-F]{32}$The URL that will receive a webhook when a Super SIM in the Fleet is used to send an IP Command from your device to a special IP address. Your server should respond with an HTTP status code in the 200 range; any response body will be ignored.
A string representing the HTTP method to use when making a request to ip_commands_url. Can be one of POST or GET. Defaults to POST.