メニュー

Rate this page:

Thanks for rating this page!

We are always striving to improve our documentation quality, and your feedback is valuable to us. How could this documentation serve you better?

The Programmable Wireless API

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

Using this REST API, you can:

The API’s Base URL

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

https://wireless.twilio.com/v1

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.

Wireless 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 https://wireless.twilio.com/v1/Sims \
  -u '{Account Sid}:{Auth Token}'

You can find your Account SID and Auth Token in 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.

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.

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.

リソース

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.

リソース 概要
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.
Rate this page:

ヘルプが必要ですか?

誰しもが一度は考える「コーディングって難しい」。そんな時は、お問い合わせフォームから質問してください。 または、Stack Overflow でTwilioタグのついた情報から欲しいものを探してみましょう。