Deprecation of id Field in Storage API Events Endpoints

We are deprecating the id field in the Keboola Connection Storage API Events endpoint. Effective June 1, 2025, the id field will be removed from all event API responses. The already-existing uuid field serves as the unique identifier for each event and should be used instead​.

When calling list endpoints always add forceUuid=true in query string, this option will ensure events ordering by uuid. This option will become default on deprecation date.

The uuid field is present in events, so any scripts or integrations still relying on the numeric id should switch to using uuid immediately. After the removal date, the id field will no longer appear in event data (it will simply be absent from the JSON response).

Example: An event object currently includes both an id and a uuid. For instance, a token creation event might look like:

{
  "id": 2080005325,
  "event": "storage.tokenCreated",
  "component": "storage",
  "tokenId": 47949,
  "tokenDescription": "Write-only token",
  "params": {},
  "results": {},
  "created": "2024-07-01T10:15:20Z",
  "uuid": "550e8400-e29b-41d4-a716-446655440000"
}

After the deprecation, the same event will be returned without the id field (using uuid as the primary identifier):

{
  "uuid": "550e8400-e29b-41d4-a716-446655440000",
  "event": "storage.tokenCreated",
  "component": "storage",
  "tokenId": 47949,
  "tokenDescription": "Write-only token",
  "params": {},
  "results": {},
  "created": "2024-07-01T10:15:20Z"
}

Going forward, please use the uuid field to identify events. This change ensures that every event is referenced by a unique identifier (the uuid), in line with our documentation’s guidance to discontinue use of the deprecated id field​.

Endpoints affected by this change

• POST /v2/storage/events – Documentation
• POST /v2/storage/branch/branch_id/events – Documentation
• GET /v2/storage/events – Documentation
• GET /v2/storage/branch/branch_id/events – Documentation
• GET /v2/storage/events/event_id – Documentation
• GET /v2/storage/branch/branch_id/events/event_id – Documentation
• GET /v2/storage/buckets/bucket_id/events – Documentation
• GET /v2/storage/tables/table_id/events – Documentation
• GET /v2/storage/tokens/token_id/events – Documentation

All customers currently using the affected Storage API Events endpoints will be contacted directly. We will provide detailed guidance to assist with the transition.

If you have any questions, please reach out to our support team.