Get event

GET

/events/{eventId}

const url = 'https://api-uat.flinkey.de/v3/events/1';
const options = {
  method: 'GET',
  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 GET \
  --url https://api-uat.flinkey.de/v3/events/1 \
  --header 'Authorization: Bearer <token>' \
  --header 'Customer-ID: example' \
  --header 'flinkey-API-Key: <flinkey-API-Key>'

Purpose

Retrieve one specific open or close event by event ID in the selected customer context.

An event represents an open or close event of a car.

Use this operation when the partner backend already knows the flinkey eventId and needs to retrieve the full event object.

Events are read-only records in normal partner workflows.

This operation does not create access rights.

This operation does not unlock or lock a vehicle.

This operation does not change assignments.

When to use this operation

Use this operation when the partner backend needs one specific event record.

Typical situations:

showing an event detail view,
checking a known event after retrieving an event list,
investigating support cases,
reconciling locally stored event data with the flinkey API,
validating whether a specific event still belongs to the selected customer context,
retrieving one event for audit or diagnostic purposes.

For list-based event history, use GET /cars/{carId}/events.

For a single known event ID, use this operation.

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

Events are operational records and should not be treated as the primary access permission model.

Access permissions are managed through assignments between User and Car.

Validation notes

The base request returned 200 OK with one event object matching the event previously returned by the car event collection.
Collection-style OData options returned 400 Bad Request with an OData error stating that the resource is not a collection.
The PROD error payload exposed internal exception and stack-trace details. Public documentation and partner logs must retain only the relevant status and message.

Async behavior

Synchronous.

The result is represented by 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.

Event data can contain operational access history.

Treat event records as sensitive operational data.

Car, user and event identifiers are environment-specific.

Do not mix UAT and PROD 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

eventId

required

integer

Database ID of the event

Header Parameters

Customer-ID

required

string

Customer database ID

Responses

200

Event was retrieved successfully

application/json

object

Database ID of the event

dateTime

Event date and time

utcDateTime

Event date and time in UTC

userId

Database ID of the user associated with the event

carId

Database ID of the car associated with the event

type

Event type. Observed values include CarOpened, CarClosed and an empty string; clients must tolerate unknown or empty values

userAgent

User agent recorded for the event

latitude

Latitude of the event, if available

longitude

Longitude of the event, if available

Example

{
  "id": 12345,
  "dateTime": "2026-07-01T10:15:30.000",
  "utcDateTime": "2026-07-01T08:15:30.000Z",
  "userId": 67890,
  "carId": 123,
  "type": "CarOpened",
  "userAgent": "partner-backend",
  "latitude": 51.2562,
  "longitude": 7.1508
}

401

Invalid subscription key or missing / invalid access token

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

404

API Manager was not found, or no event was found for the given eventId in the selected customer context

Recommended handling: Check credentials, token context, Customer-ID, local event mapping and environment

500

Server-side error

Recommended handling: Retry later if appropriate and escalate if persistent