---
title: "Update an existing remote callback."
method: PUT
path: "/fleets/{fid}/remote/callbacks/{cbid}"
tags: ["Remote"]
---

# Update an existing remote callback.

`PUT /fleets/{fid}/remote/callbacks/{cbid}`

Update an existing ```Callback``` that has been posted (and accepted previously) for this fleet. The callback object (body) provided should be complete (aggregation is not supported for the update). This object can be retrieved  using the ```GET /fleets/{fid}/remote/callbacks/{cbid}``` API then modify it and finally publish it (via this ```PUT API```)

## Path parameters

- `fid` string, required
- `cbid` string, required

## Request body

- RemoteCallbackSubscribe — Remote access callback subscription parameters.
  - `retryPolicy` object — The retry policy to apply when notification failed.
    - `policy` 'None' | 'Bounded', required — Defines the retry rules following a notification failure (ie the return code is not HTTP 2XX for WebHook mode). ```None``` means with a single try, ```Bounded``` with a limited number of tries.
    - `retryNumber` integer — Maximum number of attempts (to be used with a retryPolicy set to ```Bounded```).
    - `retryDelay` integer — Time to wait (expressed in seconds) before retrying to push a notification (ignored if retryPolicy is set to ```None```).
  - `batchNotify` object — Notification batch of events defined by a time window and batch size. If this field is not set, the callback will post only one event by call. * **At least, the ```size``` parameter should be provided.** * **If the time window is not set then the default value will be applied.**
    - `size` integer, required — Batch size (positive value and not zero).
    - `timeWindow` integer — Notification batch window size (expressed in seconds).
  - `callback` object, required
    - `webhook` object, required — Defines the webhook for htp notification .
      - `target` string, required — URL format follows [RFC 3986](https://tools.ietf.org/html/rfc3986) and usually looks like this ` scheme://host[:port][/Path] `
      - `name` string, required — Webhook name.
      - `attributes` object[] — Additional attributes-set as key/value pairs wich will be added to the request when sending the event. It can be used as http header enhancement (such as headers can be used as an authentication parameter when posting the event) or simply added to the notification event body (as set of key/values) or finally as additional query parameters.
        - `type` 'Header' | 'Body' | 'Query', required — 3 attributes type: |Attribute-type|Role| |----------|-------------| |Header|-Will be add as http header extension "x-######:"| |Body|-Will be simply add to event body map attribute (see monitor event definition in template document)| |Query|-Will set as http query parameter when invoking the Webhook|
        - `key` string, required
        - `value` union, required
          - string
          - 'vin' | 'callbackID' | 'remoteType' | 'fleetID' — Set of variables that will be contextually valued and used as attribute value. To reference the variable, prefix its name with the dollar sign ($) * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'monitorID' | 'fleetID' | 'vid' — A value that will be associated with the provided key as is if expressed as literal value or contextually valued if prefixed with the dollar sign ($). * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'fleetID' — Set of variables that will be contextually valued and used as attribute value. To reference the variable, prefix its name with the dollar sign ($) * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'monitorID' | 'fleetID' | 'vid' — A value that will be associated with the provided key as is if expressed as literal value or contextually valued if prefixed with the dollar sign ($). * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'fleetID' — Set of variables that will be contextually valued and used as attribute value. To reference the variable, prefix its name with the dollar sign ($) * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'monitorID' | 'fleetID' | 'vid' — A value that will be associated with the provided key as is if expressed as literal value or contextually valued if prefixed with the dollar sign ($). * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
          - 'vin' | 'fleetID' — Set of variables that will be contextually valued and used as attribute value. To reference the variable, prefix its name with the dollar sign ($) * Disclaimer: if the var "vin" is used as a query parameter, the batchnotify will be no more possible and each event will be sent through a separated request!. * example: Having a vin=VIN123456, the following attribute set: ```"attributes": [ { "type": "Header", "key": "X-vehicle-id" "value":"$vin" } ]``` will be valued as http header extension: *"X-vehicle-id: VIN123456"*
  - `label` string
  - `remoteTypes` RemoteType[], required

## Response `202`

Remote callback creation or update success response

## Other responses

- `default` — unresolved $ref

---

[API](https://skmtc.net/groupe-psa/apis/groupe-psa-connected-car-b2b-api.md) · [All operations](https://skmtc.net/groupe-psa/apis/groupe-psa-connected-car-b2b-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/groupe-psa/groupe-psa-connected-car-b2b-api/revisions/023ff3e3fe51/schema)