Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.cula.tech/llms.txt

Use this file to discover all available pages before exploring further.

All requests to the Cula Tracking API require a Bearer API key in the Authorization header.

​
Making authenticated requests

curl https://api.cula.tech/tracking/v1/sites \
  -H "Authorization: Bearer cula_key_live_..."

​
Key scoping

Each API key is scoped to:
  • One organisation — the key can only access resources belonging to that organisation.
  • A set of permitted sites — the key can only read and write resources associated with those sites.
Requests to resources outside the key’s scope return 403 Forbidden.

​
Key rotation

Each scope has two keys: a primary and a secondary. Both are valid simultaneously, allowing zero-downtime rotation:
  1. Generate a new secondary key in the Cula platform.
  2. Update your systems to use the new key.
  3. Revoke the old primary key.
  4. Promote the secondary to primary.
API keys are created and managed in the Cula platform UI under organisation settings. They cannot be created or rotated via the API.