XDM API Changelog

XDM API Changelog

XDM API Changelog

November 10, 2026

Added Endpoints

1.2 POST /api/external/v1/AdminTemplates

Location: Section 1 – Admin Templates

Description: Create a new admin settings template.

Details:

  • Request: application/json

  • Response: 201 Created – Returns the ID and name of the created template.

  • Validation: 400 Bad Request

  • Authorization: Requires the external admin scope.

  • Hardware versions and dealers are referenced by their IDs.

  • Template names do not need to be unique.

  • For device templates, at least one hardware version must be specified. Script templates must not have hardware versions assigned.

  • Validation errors are returned together and identified by their corresponding JSON paths.

1.3 DELETE /api/external/v1/AdminTemplates

Location: Section 1 – Admin Templates

Description: Delete multiple admin settings templates.

Details:

  • Request: application/json – Contains the IDs of the templates to delete.

  • Response: 200 OK – Returns the deletion results, including IDs that were not found.

  • Validation: 400 Bad Request

  • Authorization: Requires the external admin scope.

  • Templates are deleted even if user settings templates were previously created from them.

  • IDs that do not exist are skipped and included in the notFoundIds response.

1.4 POST /api/external/v1/AdminTemplates/import

Location: Section 1 – Admin Templates

Description: Import admin settings templates from exported files.

Details:

  • Request: multipart/form-data

  • Form field: files – One or more .json files exported from the XDM web application (Download action).

  • Response: 200 OK – Returns the import results.

  • Validation: 400 Bad Request

  • Authorization: Requires the external admin scope.

  • Each file must contain one admin settings template.

  • Hardware versions are matched by name during import.

  • All files are validated before importing. If any file is invalid, none of the templates are imported.

  • Validation errors identify the corresponding file using its index (for example, files[0]).

  • Template names do not need to be unique.


September 8, 2026

Updated Endpoints

6.8 POST /api/external/v3/devicesSdk/multiple

Location: Section 6 – Devices SDK

Description: Added optional fields for specifying the configuration and firmware already installed on the devices.

Changes:

  • currentConfigId – ID of the configuration currently installed on the devices.

  • currentFirmwareId – ID of the firmware currently installed on the devices.

  • Both fields are optional.

17.1 GET /api/external/v1/scripts/filter

Location: Section 17 – Scripts

Description: Clarified the filtering behavior of the IsReleased parameter.

Changes:

  • true – Returns only released scripts.

  • false – Returns only unreleased drafts.

  • Omitted – Returns scripts regardless of their release status.

5.1 GET /api/external/v1/canfiles/filter

Location: Section 5 – CAN Files

Description: Updated the Model parameter documentation.

Changes:

  • Clarified that Model filters CAN files by the vehicle make/model they target.

5.2 GET /api/external/v3/canfiles/filter

Location: Section 5 – CAN Files

Description: Updated the Model and Version parameter documentation.

Changes:

  • Model – Filters CAN files by the vehicle make/model they target.

  • Version – Filters CAN files by a specific CAN file revision number.