Delete car

DELETE

/cars/{carId}

const url = 'https://api-uat.flinkey.de/v3/cars/1';
const options = {
  method: 'DELETE',
  headers: {
    'Customer-ID': 'example',
    'flinkey-API-Key': '<flinkey-API-Key>',
    Authorization: 'Bearer <token>'
  }
};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request DELETE \
  --url https://api-uat.flinkey.de/v3/cars/1 \
  --header 'Authorization: Bearer <token>' \
  --header 'Customer-ID: example' \
  --header 'flinkey-API-Key: <flinkey-API-Key>'

Purpose

Delete an existing car from the selected customer context.

A car represents the vehicle access object used by the flinkey API.

For developer integrations, the flinkey BLE Box is abstracted behind the Car concept.

Use this operation only when a car should no longer be available for future access or assignment operations.

When to use this operation

Use this operation when the partner backend needs to remove an existing flinkey car.

Typical situations:

a vehicle is removed from the partner fleet,
a test car should be cleaned up,
an incorrectly created car should be removed,
a vehicle mapping is being retired,
a car should no longer be used for future assignment creation.

Before deleting a car, check whether the car is still referenced by active partner processes.

In most integrations, the partner backend should persist a mapping between the partner vehicle ID and the flinkey carId.

After successful deletion, update or remove the local mapping.

Do not delete a car only because a customer currently has no active assignment.

Validation notes

PROD validation result:

DELETE /cars/{carId} returned 204 No Content without a response body.
A subsequent GET /cars/{carId} returned 404 Not Found.
The post-delete lookup message was Unable to find a car for the given carId which is assigned to the given customerId.
The full create, update, get and delete lifecycle was repeated with a second controlled test car to confirm the response codes.
The operation completed synchronously and produced no webhook.

Async behavior

Synchronous.

The delete result is returned directly in the API response.

Webhook result

No.

This operation does not produce a webhook result.

Security notes

Never log:

flinkey-API-Key,
bearer token,
full request headers.

Car identifiers are environment-specific.

Do not mix UAT and PROD car IDs.

Use placeholders in documentation, examples, screenshots and AI prompts.

Authorizations

apiKey
bearerAuth

Parameters

Path Parameters

carId

required

number

Database ID of the car to delete

Header Parameters

Customer-ID

required

string

Customer database ID

Responses

204

Car was deleted successfully

401

Invalid subscription key or missing / invalid access token

Recommended handling: Check flinkey-API-Key, bearer token and environment configuration

404

API Manager, customer context or car was not found

Recommended handling: Check credentials, Customer-ID and local carId mapping

500

Server-side error

Recommended handling: Retry later if appropriate and escalate if persistent