Programmable Wireless
Last updated
Was this helpful?
Last updated
Was this helpful?
The Programmable Wireless REST API enables you to programmatically manage global fleets of cellularly connected IoT devices.
Using this REST API, you can:
Exchange .
Obtain real-time insights to your SIM's connectivity with .
Manage SIM capabilities and data metering with .
Manage .
Obtain .
Obtain .
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.
The following lists the resources exposed by the Wireless REST API.
Resource
Description
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.
This resource represents an M2M SMS message.
This resources returns data session information for a SIM over a period of 30 days or under, presented as an aggregated list.
This resource describes the capabilities and restrictions that will apply to any SIMs that are associated with the specified Rate Plan.
A Sim resource (note the case) represents a physical SIM card that is capable of connecting to a wireless network.
This resource is used to query the usage of a SIM. You can query multiple dimensions by providing query filters.
The API documentation presents the appropriate parameter formatting for the language or tool that you select in the code column.
Errors are signaled by 4xx and 5xx HTTP response status codes and a JSON response body. The error data is a standard KORE structure. For example:
Many errors are generic to platform — the one shown above, for example. However, Programmable Wireless-specific error codes are in the range 33000-33999.
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 KORE 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 KORE does not receive a success response from your callback URL.
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 . 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:
This contrasts with responses from the API, in which properties are referenced using . For example, getting that same Sim's details will return:
If you use one of KORE's Helper Libraries or , properties' cases may differ from those outlined above for the base API. The API documentation always shows the correct case for a given library
HTTP requests made to the REST API are protected with . To learn more about how KORE handles authentication, please see our . You use your KORE Auth Token as the token for HTTP Bearer authentication.
You can find your Auth Token in the .
To learn more about authentication and interaction with the KORE REST API, see our documentation for and .
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 . The value of code is a KORE error code, and is referenced again in the more_info URL.
You can see a list of all such codes in the and as a .