# Deregister a Callback Listener ### `DELETE /callbacks/{accountName}` Deregisters the callback endpoint and stops ThingSpace from sending FOTA callback messages for the specified account. ## HTTP Request DELETE [https://thingspace.verizon.com/api/fota/v2/callbacks/{accountName}](/docs/standard-apis/connectivity-management/api-endpoints/connectivity-callbacks/deregister-callback/deregistercallback) ## Resource Path Parameters You must include the name of the account in the path. | Parameter Name | Data Type | Description | |:----------------|:-----------|:-------------| | accountName <br> *required* | string | The name of the billing account that is registered to receive callback messages. An account name is usually numeric, and must include any leading zeros. | ## 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](https://thingspace.verizon.com/documentation/api-documentation.html#/http/session-management/guides/getting-started). | Parameter Name | Data Type | Description | |:-----------------------|:-----------|:-----------------------------------------------------------------------------| | **Authorization** <br> _required_ | string | HTTP Authorization bearer token: <br> `Authorization: Bearer {token}` | | **VZ-M2M-Token** <br> _required_ | string | A valid session token: <br> `VZ-M2M-Token: {M2Mtoken}` | ## Request Body None. ## Success Responses **Status 200** ## Example Success Response ```json { "success": true } ``` ## Failure Responses **Status 400** All error messages are returned in this format: ```json { "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.