Retrieves queued SMS messages sent by all M2M MC devices associated with an account.
When HTTP status is 202, a URL will be returned in the Location header of the form /sms/{aname}/history?next={token}. This URL can be used to request the next set of messages.
Authorization
thingspace_oauth VZ-M2M-Token This is the ThingSpace token, from Credentials and Tokens is used
In: header
M2M Session Token (How to generate an M2M session token?)
In: header
Path Parameters
Account name.
Query Parameters
Continue the previous query from the URL in Location Header.
int64Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/m2m/v1/sms/0252012345-00001/history"{ "messages": [ { "deviceIds": [ { "id": "09623489171", "kind": "esn" } ], "message": "testmessage1", "timestamp": "2016-01-01T12:29:49-08:00" }, { "deviceIds": [ { "id": "09623489171", "kind": "esn" } ], "message": "testmessage2", "timestamp": "2016-01-01T12:31:02-08:00" } ], "hasMoreData": false}Sends an SMS message to one or more devices. POST
The messages are queued on the ThingSpace Platform and sent as soon as possible, but they may be delayed due to traffic and routing considerations.
Starts delivery of queued SMS messages for the specific account. PUT
Tells the ThingSpace Platform to start sending mobile-originated SMS messages through the EnhancedConnectivityService callback service. SMS messages from devices are queued until they are retrieved by your application, either by callback or synchronously with GET /sms/{accountName}/history.