for fleet owner



    With our APIs, you are able to browse data about vehicles and receive custom notifications. Now, the remote APIs allow you to send online commands to connected vehicles.


    Available features:

    • Charging: Start the recharge of the vehicle.
    • Stolen: Set the vehicle as stolen.
    • Lights: Turn on/off vehicle lights.
    • State: Refresh and retrieve vehicle status info.
    • Preconditioning: Program heater or AC before the vehicle is being used.
    • DoorsState: Lock/unlock the doors remotely.
    • Horn: Honk the horn, maybe you will be able to find your car in the car-park this time.
    • Immobilization: Immobilize the vehicle until you let it go again.


    Step1: create a callback

    First, you will have to set up a remote callback. If you are already working with monitors, it is almost the same as posting a monitor.

    Callback is where you define the parameters of your webhook (URL, authentication) and the structure of the HTTP request you will receive as a notification.

    Callbacks are specific to certain remotes, as you can subscribe them to one or more actions & they are reusable as you can use the same callback every time you need to execute a similar command.

    It is possible to set a retry policy with a specific number and frequency, it’s useful in case of your webhook is temporary unavailable. You can also set a batch notify policy.


    Note: At least one callback is required to post a remote action. But you can use only one callback for all your remote actions if you need only one webhook configuration. Indeed, if you need to have different webhook or notification policies, you can set several callbacks.

    Step2: send a remote action

    Once your callback is created, you will be able to send remote request to your vehicle (through Groupe PSA’s network). While the command is being processed by the vehicle, you will receive callback reports in your webhook.


    When you send a remote action to a vehicle, you will receive several notifications as the action is processing:

    • Pending: The remote action is in process (Accepted, Waking-Up, Send etc). You can receive several pending events.
    • Done: The remote action is complete (Success, Failure etc).



    Before being able to send a remote action, you have to configure the HTTP callback that will be sent to your webhook.

    This callback specifies your webhook config, a retry policy and a batch notification policy. You can set up several callbacks. You will then execute a remote action using the callback the most appropriate for the situation.

    Here is an overview of an HTTP request intended to create a remote callback.

      "retryPolicy": { },
      "batchNotify": { },
      "callback": { },
      "label": "callback-name",
      "extendedEventParam": [ ]

    Below is a description of the JSON models explaining how to configure a callback. Please refer to API Reference models to read a full description of the callback configuration.

    • RemoteCallbackSubscribe: this JSON object allow you to configure your remote callback:
      • retryPolicy: this where you set retry policy, it’s in case your webhook has not received the callback, whatever is the reason.
      • batchNotify: you can set this object in case you need to receive notification in batch instead of one by one.
      • callback>webhook: this required object is where you will set the address and name of your webhook. This is also where you can customize the HTTP notification (example: for authentication purpose).
    • notificationTypes: this array of remotes allow you to subscribe this callback to one or more actions.


    This request ask to create a callback named “my-post-callback” with the following parameters:

    • If the callback notification is not received, the request will be sent again every 120s until it’s properly delivered.
    • The callback will be sent once 10 callback notifications are ready to be sent or 300s after triggering.
    • The callback will be sent to your https://my.post.callback webhook with the vin of the vehicle as a query path param and your Basic authentication in HTTP header.
    • This callback can be used in order to send remote actions: ThermalPreconditioning & ElectricBatteryChargingRequest.
       "retryPolicy": {
          "policy": "Always",
          "maxRetryNumber": 3,
          "retryDelay": 120
       "batchNotify": {
          "size": 10,
          "timeWindow": 300
       "callback": {
          "webhook": {
             "target": "https://my.post.callback",
             "name": "My_Webhook",
             "attributres": [
                "value":"Basic QWxhZGRpbjpvcGVuIHNlc2FtZQ=="
       "label": "my-post-callback",
        "notificationTypes": [


    Here is an example of HTTP response after POSTING a new remote callback.

        "_links": {...},
        "callbackId": "c7eeaafdf0ab9683d5a1b8d51572014996540m0021",
        "status": "Running"

    The callback have been created with id=c7eeaafdf0ab9683d5a1b8d51572014996540m0021. This callbackId will be sent with every notification to your webhook.

    Important: You will need this ID to POST a remote action to a vehicle with this callback.



    Once you have a dedicated callback, you are able to POST a remote action to a vehicle. Choose a vehicle id (you can retrieve it with the API status), then send this kind of request:

      "label": "remote_name",
      "door": {
        "state": "Unlocked"

    In this API you have to replace this fields:

    • {fid} is the id of your fleet.
    • {vid} is the id of the vehicle to which you want to send the remote action.
    • {cbid} is the id of one of your callbacks (see 1. Post remote Callback).

    You can browse the Remote Object in the reference section to have more info about how to send a specific remote action:

    Object Name Description Example
    RemotePreconditioning Choose between immediate preconditionning or not, and set a program with recurrence or not, start time, occurence during the week then, choose to enable or not this program. Note: Using the key/value Slot you can register up to 4 PreconditionPrograms. { "label": "string", "preonditionning": { "airConditioning": { "immediate": false, "programs": [ { "recurrence": "Daily", "start": "PT14H30M", "occurence": { "day": [ "Mon" ] }, "slot": 0, "enabled": true } ] } } }
    RemoteSetImmobilization Set to activate to true if you need to immobilize a vehicle. You can use this feature in addition to “RemoteSetStolen”. { "immobilization": { "activate": true } }
    RemoteDoorsState Set state to Locked or Unlocked. { "door": { "state": "Unlocked" } }
    RemoteHorn Choose the number of times the horn will honk and if the remote is "state": "Activated" or "state": "Unactivated". { "horn": { "number": 0, "state": "Activated" } }
    RemoteCharging You can choose between immediate recharge or nextDelayedTime with a timestamp RFC3339 before the charge activation. { "charging": { "nextDelayedTime": "string", "immediate": false } }
    RemoteSetStolen Set stolen to true if you want the vehicle to be in stolen state. It’s mean that it will stay awake and refresh lastPosition on a regular basis. { "stolen": { "stolen": true } }
    RemoteLights Set on or not the vehicles lights. If you turn it on, you can choose a duration expressed using ISO-8601. { "ligths": { "on": true, "duration": "PT20S" } }
    RemoteState Set action: state to retrieve an updated status of the vehicle. { "state": { "action": "state" } }

    Be careful: you can send only one Remote Action at once. If you need to send several Remote Actions you have to send several HTTP POST requests to /fleets/{fid}/vehicles/{vid}/callbacks/{cbid}/remotes. However, you can use the same callback for those Remote Action.


    This is an example of HTTP response when you POST remote action:

      "_links": { ... },
      "remoteActionId": "909bkqacjb3bfhdhjanahbc244jj2lixfbe2e52u5y",
      "type": [

    RemoteActionID is the unique identifier of the remote. This id will be sent to your callback with your remote action reports.


    You have to develop on your side a dedicated webhook able to receive our event.

    This web server needs to be configured to read & process our events in order that you get informed about the processing of the remote. Below is the webhook template specification, it describes the HTTP callback you will receive.

    Note: HTTPS must be supported and a certificate issued by a trusted public and known CA must be provided. Indeed, the URL of your webhook have to be the same as the one specified in when you created the callback.

    SEE ALSO #


    Want to see what it’s look like ? Browse our Preview.

    TRY OUT!

    Retrieve reference of this API, go to the API List.