Remove car from group

DELETE

/groups/{groupId}/cars/{carId}

const url = 'https://api-uat.flinkey.de/v3/groups/1/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/groups/1/cars/1 \
  --header 'Authorization: Bearer <token>' \
  --header 'Customer-ID: example' \
  --header 'flinkey-API-Key: <flinkey-API-Key>'

Purpose

Remove one specific car from one specific group in the selected customer context.

A group is an entity represented by a group ID.

A group can contain cars, users, services and products.

Use this operation for operational grouping workflows where a car must be removed from an existing group.

This operation changes group membership only.

It does not delete the car.

It does not remove assignments.

It does not revoke vehicle access rights.

When to use this operation

Use this operation when the partner backend or operational backend needs to remove a car from a group.

Typical situations:

removing a car from an operational group,
correcting group membership after reconciliation,
cleaning up group membership after fleet-side changes,
maintaining group-based operational views,
removing a car from a support or setup group,
preparing a group for deletion.

Before removing a car from a group, the partner backend should have resolved:

the correct Customer-ID,
the flinkey groupId,
the flinkey carId,
whether the group exists,
whether the car exists,
whether the car is currently assigned to the group.

For standard access flows, partner backends usually work primarily with Car, User and Assignment.

Group membership is an operational grouping concept and should not be treated as the primary vehicle access permission.

Access permissions are managed through assignments between User and Car.

Validation notes

PROD returned 204 No Content with an empty body. A control GET returned an empty car array.

Async behavior

Synchronous.

The removal result is represented by the API response.

Webhook result

No.

This operation does not produce a webhook result.

Removing a car from a group does not trigger assignment lifecycle webhooks.

If vehicle access must be changed, use the appropriate assignment operation.

Security notes

Never log:

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

Group and car identifiers are environment-specific.

Do not mix UAT and PROD group IDs or car IDs.

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

For standard partner integrations, the mobile app must not receive API Manager credentials, backend bearer tokens or the flinkey-API-Key.

Authorizations

apiKey
bearerAuth

Parameters

Path Parameters

groupId

required

integer

Database ID of the group

carId

required

integer

Database ID of the car

Header Parameters

Customer-ID

required

string

Customer database ID

Responses

204

Car was removed from the group 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, group, car or group membership was not found

Recommended handling: Check credentials, token context, Customer-ID, local groupId mapping, local carId mapping and current group membership

500

Server-side error

Recommended handling: Retry later if appropriate and escalate if persistent