GET /v2/triggers/accounts/{accountName}
Retrieving a trigger for MDNless is similar to retrieving any trigger in Connectivity Management. The only difference is a few new values added in the response for MDNless. This page will cover the new values and provide examples of what responses look like with the new values.
The request header must contain a current ThingSpace authorization bearer token and a valid VZ-M2M session token, and must set the content-type to JSON.
Parameter Name | Data Type | Description |
---|---|---|
Authorization required |
string | HTTP Authorization bearer token. |
VZ-M2M-Token required |
string | A valid session token returned by POST /session/login. |
Content-Type required |
string | Must be application/json . |
Parameter Name | Data Type | Description |
---|---|---|
accountName required |
string | The name of the account. An account name is usually numeric and must include any leading zeros. |
GET https://thingspace.verizon.com/api/m2m/V2/triggers/accounts/0000123456-00001
Status 200
{
"triggers":[
{
"triggerId":"2874DEC7-26CF-4797-9C6A-B5A2AC72D526",
"triggerName":"PromoAlerts_0000000000-00001_23456789",
"accountName":"0000123456-00001",
"organizationName":"MdnLessTest",
"triggerCategory":"PromoAlerts",
"triggerAttributes":[
{
"key":"ServicePlan"
},
{
"key":"DataPercentage50",
"value":"False"
},
{
"key":"DataPercentage75",
"value":"False"
},
{
"key":"DataPercentage90",
"value":"False"
},
{
"key":"DataPercentage100",
"value":"True"
},
{
"key":"SmsPercentage50",
"value":"False"
},
{
"key":"SmsPercentage75",
"value":"False"
},
{
"key":"SmsPercentage90",
"value":"False"
},
{
"key":"SmsPercentage100",
"value":"True"
},
{
"key":"NoOfDaysB4PromoExp",
"value":"0"
},
{
"key":"EnablePromoExp",
"value":"True"
}
],
"createdAt":"2021-12-06T20:32:021.830Z",
"modifiedAt":"2021-12-06T20:32:021.830Z"
}
]
}
Parameter Name | Data Type | Description |
---|---|---|
triggerId |
string | The system assigned ID of the Trigger. |
triggerName |
object | The system assigned name of the trigger. When the trigger is associated with MDNless, the name will show "PromoAlerts". |
accountName |
string | The name of the account. An account name is usually numeric and must include any leading zeros. |
organizationName |
string | An optional group name added when the trigger is created. |
triggerCategory |
string | The category of the trigger. For MDNless this category will always be "PromoAlerts" |
triggerAttributes |
array | This array contains the relevant keys for the trigger. |
key.ServicePlan |
string | The customer's service plan associated with the trigger. |
key.DataPercentage50 |
boolean | Whether or not the usage has exceeded 50% of the account's total usage allowed.
|
key.DataPercentage75 | boolean | Whether or not the usage has exceeded 75% of the account's total usage allowed.
|
key.DataPercentage90 | boolean | Whether or not the usage has exceeded 90% of the account's total usage allowed.
|
key.DataPercentage100 | boolean | Whether or not the usage has exceeded 100% of the account's total usage allowed.
|
key.SmsPercentage50 | boolean | Whether or not the number of SMS messages has exceeded 50% of the account's total usage allowed.
|
key.SmsPercentage75 | boolean | Whether or not the number of SMS messages has exceeded 75% of the account's total usage allowed.
|
key.SmsPercentage90 | boolean | Whether or not the number of SMS messages has exceeded 90% of the account's total usage allowed.
|
key.SmsPercentage100 | boolean | Whether or not the number of SMS messages has exceeded 100% of the account's total usage allowed.
|
key.NoOfDaysB4PromoExp | integer | The number of days until the promotional billing rate for MDNless ends. |
key.EnablePromoExp | boolean | Whether or not the promotional billing rate will expire.
|
createdAt | string(date-time) | The time stamp of when the trigger was created. |
modifiedAt | string(date-time) | The time stamp of the most recent time the trigger was modified. |
All failure responses are 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.