GET /subscriptions/{account}
Returns information about an account’s Software Management Services subscription status.
See also:
Get License Status
GET https://thingspace.verizon.com/api/fota/v1/subscriptions/{account}
You must include the account name in the path.
Parameter Name | Data Type | Description |
---|---|---|
account required |
string | The name of the account for which you want the Software Management Services subscription status. An account name is usually numeric, and must include any leading zeros. |
The request header must contain a current ThingSpace authorization token and a current VZ-M2M session token.
Parameter Name | Data Type | Description |
---|---|---|
Authorization required |
string | HTTP Authorization request header containing a valid Bearer token. |
VZ-M2M-Token required |
string | A valid session token returned by a Connectivity Management POST /session/login request. |
None.
Request the subscription status for an account:
curl https://thingspace.verizon.com/api/fota/v1/subscriptions/$ACCOUNT -H 'Authorization: Bearer $AUTH_TOKEN' -H 'VZ-M2M-Token: $M2M_TOKEN'
Status 200
A success response includes the type of Software Management Services subscription, the number of total licenses (if applicable), and the registered callback endpoint.
Parameter Name | Data Type | Description |
---|---|---|
accountName | string | The name (number) of the billing account. |
purchaseType | string | Comma-separated list of subscription models used by the account:
|
licenseCount | integer | The number of monthly licenses in an MRC subscription. This will be zero for accounts that only have Event subscriptions. |
licenseUsedCount | integer | The number of licenses currently assigned to devices. |
updateTime | string | The date and time of when the subscription was last updated. |
{
"accountName":"0402196254-00001",
"purchaseType": "TS-HFOTA-EVNT,TS-HFOTA-MRC",
"licenseCount": 9000,
"licenseUsedCount": 1000,
"updateTime": "2018-03-02 19:50:06.534 +0000 UTC"
}
Status 400
All error messages are returned in this format:
{
"errorCode": "error code string",
"errorMessage": "error message string"
}
Error codes and messages are listed on the Error Messages page, along with explanations and suggestions for corrective actions.