Deregister a Callback Listener:

DELETE /callbacks/{accountname}/name/{sname}

Stops the ThingSpace Platform from sending callback messages for the specified account and service.

Contents

See also:
About ThingSpace Callback Services
List Callback Listeners
Register a Callback Listener

Request Components

HTTP Request

DELETE https://thingspace.verizon.com/api/m2m/v1/callbacks/{accountname}/name/{sname}

Resource and Query Parameters

You must include the name of the account and the 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.
sname
required		 string The name of the callback service type that you want to stop. Valid values are:
  • AlertsService
  • CarrierService
  • DevicePRLInformation
  • DeviceService
  • DeviceSuspensionStatus
  • DeviceUsage
  • EnhancedConnectivityService
  • ExternalProvisioningChanges
  • NiddService
  • PromoChanges
  • ResumeTrackingNotification
  • SMSDeliveryConfirmation
  • StateService

Header Parameters

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.

Request Body

None.

Success Responses

Status 200

Parameter Name Data Type Description
accountName string The name of the billing account.
serviceName string The name of the callback service that was deregistered.

Example Success Response

{
  "accountName": "1223334444-00001",
  "serviceName": "CarrierService"
}

Failure Responses

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.

Try It Out!