Premium APIsDevice LocationAPI Reference
Deregister a Callback Listener
Deregister Callback Listener
DELETE /callbacks/{accountName}/name/{service}
Stops ThingSpace from sending callback messages for the specified account and service.
HTTP Request
DELETE https://thingspace.verizon.com/api/loc/v1/callbacks/{accountName}/name/{service}
Resource and Query Parameters
You must include the name of the account and callback service in the path.
| Parameter Name | Data Type | Description |
|---|---|---|
| accountName (required) | string | The name of the billing account that has registered to receive callback messages. An account name is usually numeric, and must include any leading zeros. |
| service (required) | string | The name of the callback service type that you want to stop. This must be Location for the Device Location Service callback. |
Header Parameters
The request header must contain a current ThingSpace authorization token and a current VZ-M2M session token. For more details on how to get these tokens, visit Getting Started.
| Parameter Name | Data Type | Description |
|---|---|---|
| Authorization (required) | string | HTTP Authorization bearer token: Authorization: Bearer {token}. |
| VZ-M2M-Token (required) | string | A valid session token returned by POST /api/m2m/v1/session/login. |
| Content-Type (required) | string | Must be application/json: Content-Type: application/json. |
Request Body
None.
Success Responses
Status 200
A response to a successful request contains a single Boolean value:
{
"success": true
}Example Success Response
{
"accountName": "0000123456-00001",
"serviceName": "Location"
}Failure Responses
All error messages are returned in this format:
{
"errorCode": "The 3-digit HTML error code",
"errorMessage": "string"
}Error codes and messages are listed on the Error Codes page, along with explanations and suggestions for corrective actions.