Modify a callback listener

Modify a Callback Listener URL

`PUT /callbacks/{accountName}`

Modifies the secure URL (HTTPS) at which an account receives messages from the Software Management FOTA callback service when new software versions are available and when upgrades start and finish.

This request replaces the previously registered FOTA callback listener if there is one.

Usage and Requirements

The callback messages will conform to the JSON callback schema shown on the About Callback Services page. You can follow these instructions to create a simple callback listener that will report the callback type and display any received callbacks on the console.

HTTP Request

PUT https://thingspace.verizon.com/api/fota/v2/callbacks/{accountName}

Resource Path and Query Parameters

The account name must be included in the path.

Parameter Name	Data Type	Description
accountName required	string	The name of the billing account for which you want 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.

Parameter Name	Data Type	Description
Authorization required	string	HTTP Authorization bearer token: `Authorization: Bearer {token}`
VZ-M2M-Token required	string	A valid session token: `VZ-M2M-Token: {M2Mtoken}`

Request Body

The body specifies the URL where the listening service is running.

Parameter Name	Data Type	Description
callback required	required string	The secure address on your server where you have enabled a listening service for Software Management Services callback messages. Specify a secure URL (HTTPS) that is reachable from the Verizon data centers.

Example Request Body

{    "url": "https://255.255.11.135:50559/CallbackListener/FirmwareServiceMessages.asmx"}

Success Responses

Status 200

Parameter Name	Data Type	Description
url	string	The secure address on your server where you have enabled the listening service for Software Management Services callback messages.

Example Success Response

{    "url": "https://255.255.11.135:50559/CallbackListener/FirmwareServiceMessages.asmx"}

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.

# Modify a Callback Listener URL ### `PUT /callbacks/{accountName}` Modifies the secure URL (HTTPS) at which an account receives messages from the Software Management FOTA callback service when new software versions are available and when upgrades start and finish. This request replaces the previously registered FOTA callback listener if there is one. ## Usage and Requirements The callback messages will conform to the JSON callback schema shown on the About Callback Services page. You can follow these instructions to create a simple callback listener that will report the callback type and display any received callbacks on the console. ## HTTP Request PUT [https://thingspace.verizon.com/api/fota/v2/callbacks/{accountName}](/docs/premium-apis/software-management/software-management-v2/api-endpoints/software-management-callbacks-v2/updatecallback) ## Resource Path and Query Parameters The account name must be included in the path. | Parameter Name | Data Type | Description | |:----------------|:-----------|:-------------| | **accountName** *required* | string | The name of the billing account for which you want 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** _required_ | string | HTTP Authorization bearer token: `Authorization: Bearer {token}` | | **VZ-M2M-Token** _required_ | string | A valid session token: `VZ-M2M-Token: {M2Mtoken}` | ## Request Body The body specifies the URL where the listening service is running. | Parameter Name | Data Type | Description | |:----------------|:-----------|:-------------| | **callback** *required* | required string | The secure address on your server where you have enabled a listening service for Software Management Services callback messages. Specify a secure URL (HTTPS) that is reachable from the Verizon data centers. | ## Example Request Body ```json { "url": "https://255.255.11.135:50559/CallbackListener/FirmwareServiceMessages.asmx" } ``` ## Success Responses **Status 200** | Parameter Name | Data Type | Description | |:----------------|:-----------|:-------------| | **url** | string | The secure address on your server where you have enabled the listening service for Software Management Services callback messages. | ## Example Success Response ```json { "url": "https://255.255.11.135:50559/CallbackListener/FirmwareServiceMessages.asmx" } ``` ## 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.

Verizon 5G Edge API Portal

Modify a callback listener