Rate this page:

The Programmable Wireless API

The Programmable Wireless REST API enables you to programmatically manage global fleets of cellularly connected IoT devices.

Using this REST API, you can:

The Programmable Wireless API base URL

All URLs in the reference documentation use the following base URL:

The Programmable Wireless REST API is served over HTTPS. To ensure data privacy, unencrypted HTTP is not supported. All responses are provided in JSON format.

You don’t need to use the .json file extension in API request URIs.

API resources

The following lists the resources exposed by the Wireless REST API.

To avoid ambiguity, 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.

Resource Description
Account Usage Record
This resource is used to query the combined usage for all of the SIMs in your account. You can query multiple dimensions by providing query filters.
Command This resource represents an M2M SMS message.
SIM Data Sessions This resources returns data session information for a SIM over a period of 30 days or under, presented as an aggregated list.
RatePlan This resource describes the capabilities and restrictions that will apply to any SIMs that are associated with the sepcified Rate Plan.
Sim A Sim resource (note the case) represents a physical SIM card that is capable of connecting to a wireless network.
Sim Usage Record This resource is used to query the usage of a SIM. You can query multiple dimensions by providing query filters.

API resource properties

When you create or update resources, you indicate the data that is being added or changed by specifying the appropriate resource property. All resource properties are case-sensitive and written in UpperCamelCase. For example, if you want to change a new Sim’s status from ready to active and receive an asynchronous notification of the change, you call:

curl{Sim SID} \
  -d 'Status=active' \
  -d 'CallbackUrl={Your notification URI}'
  -u '{Account_Sid}:{Auth_Token}'

This contrasts with responses from the API, in which properties are referenced using lower_snake_case. For example, getting that same Sim’s details will return:

  "unique_name": "unique_name",
  "commands_callback_method": "POST",
  "commands_callback_url": "{Your notification URI}",
  "date_created": "2021-04-01T20:00:00Z",
  "date_updated": "2021-04-01T20:00:00Z",
  "friendly_name": "friendly_name",
  "links": {
    "data_sessions": "",
    "rate_plan": "",
    "usage_records": ""
  "iccid": "iccid",
  "e_id": "e_id",
  "status": "active",
  "reset_status": null,
  "url": "",
  "ip_address": ""

The API documentation presents the appropriate parameter formatting for the language or tool that you select in the code column.

If you use one of Twilio’s Helper Libraries or SDKs, properties’ cases may be different from those outlined above for the base API. The API documentation always shows the correct case for a given library

API authentication

HTTP requests made to the REST API are protected with HTTP Basic authentication. To learn more about how Twilio handles authentication, please see our security documentation. You use your Twilio Account SID as the username and your Auth Token as the password for HTTP Basic authentication.

curl -G \
  -u '{Account Sid}:{Auth Token}'

You can find your Account SID and Auth Token in the Console.

To learn more about authentication and interaction with the Twilio REST API, see our documentation for requests to the API and Twilio’s response.

API errors

Errors are signaled by 4xx and 5xx HTTP response status codes and a JSON response body. The error data is a standard Twilio structure. For example:

  "code": 20003, 
  "detail": "Your AccountSid or AuthToken was incorrect.", 
  "message": "Authentication Error - No credentials provided", 
  "more_info": "", 
  "status": 401

As you can see, the JSON gives you a human- and machine-readable indication of the nature (the detail key) and cause (message) of the error, and a reference to a more detailed description of the error in Twilio’s documentation. The value of code is a Twilio error code, and is referenced again in the more_info URL.

Many errors are generic to platform — the one shown above, for example. However, Programmable Wireless-specific error codes are in the range 33000-33999.

You can see a list of all such codes in the error code documentation and as a JSON file.

Asynchronous resources

Certain operations in the Programmable Wireless REST API, such as changing the status of a Sim resource, can take some time to complete: anywhere from a few seconds to a minute or more. These operations will return an intermediate synchronous HTTP response — 202 Accepted — while the action completes in the background.

Requests that will be processed asynchronously allow you to specify a callback URL for Twilio to notify when the request has completed. A callback is sent to your server as either an HTTP POST or GET request, depending on your preference. Form parameters or query string parameters sent with the callback request describe the asynchronous outcome. Callback request formats are documented with each of the relevant REST API resources.

If your initial request completes synchronously, a 200 OK, 201 Created, or 204 No Content response will be returned and you should not expect an asynchronous callback, even if a callback URL was specified.

An event will be posted to your account’s Debugger in the Console with error details if Twilio does not receive a success response from your callback URL.

Twilio server-side SDKs (Helper Libraries)

You can learn how to use the Twilio server-side SDKs, also known as Helper Libraries, with Programmable Wireless in a variety of popular server-side programming languages on the SDKs section of the Twilio Docs.

Rate this page:

Need some help?

We all do sometimes; code is hard. Get help now from our support team, or lean on the wisdom of the crowd by visiting Twilio's Stack Overflow Collective or browsing the Twilio tag on Stack Overflow.

Thank you for your feedback!

Please select the reason(s) for your feedback. The additional information you provide helps us improve our documentation:

Sending your feedback...
🎉 Thank you for your feedback!
Something went wrong. Please try again.

Thanks for your feedback!