Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.croma.run/llms.txt

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

​
1. Get an API key

Croma keys are issued per organization from your Croma dashboard. A key looks like croma_live_… (or croma_test_… outside production). Treat it as a secret. It carries your org’s full API access.
Personal keys are rejected. The API only accepts organization-scoped keys. See Authentication for details.

​
2. Make a request

Every data endpoint is a POST to https://api.croma.run, with the key in an Authorization: Bearer header. 
curl https://api.croma.run/co/rama-judicial/cases/search/v1 \
  -H "Authorization: Bearer $CROMA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "PEDRO CIFUENTES", "person_type": "nat", "page": 1 }'

​
3. Read the response

Successful responses wrap the payload under data: 
{
  "data": { }
}
Your rate-limit state and a request id arrive as response headers; there’s no meta object in the body: 
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 99
X-RateLimit-Reset: 2026-05-23T18:00:00.000Z
X-Request-Id: req_8f3c…

Next: Authentication

How keys, scopes, and the bearer scheme work.