Standard APIsConnectivity ManagementAPI EndpointsConnectivity CallbacksDeregister Callback

API Reference

Deregister a Callback Listener

DELETE /callbacks/{accountName}/name/{serviceName}

Deregisters the callback endpoint and stops ThingSpace from sending callback messages for the specified account.

Header Parameters

The request header must set the content-type to JSON, 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 NameData TypeDescription
Authorization (required)stringHTTP Authorization request header containing a valid Bearer token: Authorization: Bearer {token}
VZ-M2M-Token (required)stringA valid session token returned by a Connectivity Management POST /session/login request.
Content-Type (required)stringMust be application/json.

HTTP Request

DELETE https://thingspace.verizon.com/api/fota/v1/callbacks/{accountName}/name/{serviceName}

Request Parameters

The name of the account and the name of the callback service must be included in the path.

Parameter NameData TypeDescription
accountName (required)stringThe name of the billing account that is registered to receive callback messages. An account name is usually numeric, and must include any leading zeros.
serviceName (required)stringThe name of the callback service the listener is subscribed to and will be one of the following: AlertService , Fota , CarrierService , DevicePRLInformation , DeviceProfileService , DeviceService , DeviceSuspensionStatus , DeviceUsage , DiagnosticsService , EnhancedConnectivityService , ExternalProvisioningChanges , IntelligenceService , NiddService , PromoChanges , ResumeTrackingNotification , SMSDeliveryConfirmation , StateService or SubscriptionNotificationService .

Request Body

None.

Success Responses

Status 200 The response will show that the request has been successful (true) or has failed (false):

{
  "success": true
}

Failure Responses

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.

On this page