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.

Every API response includes an Cula-Request-Id header containing a unique identifier for that request. This applies to all responses — successful and unsuccessful.

​
Response header

Cula-Request-Id: req_01kqzcjrpyf27tge33jwvjhkff
The value is a server-generated TypeID with the req_ prefix. It is unique per request.

​
Where request IDs appear

LocationWhen
Cula-Request-Id response headerEvery response (2xx, 4xx, 5xx)
error.request_id in the JSON bodyEvery non-2xx response
request_id in webhook payloadsEvents triggered by an API request
On error responses, the request_id in the JSON body and the Cula-Request-Id header always contain the same value.

​
Using request IDs

Log them. Store the Cula-Request-Id header from every response in your application logs. When something goes wrong, the request ID lets both you and Cula support trace the exact request through the system. 
curl -i -X POST "https://api.cula.tech/tracking/v1/material-sourcing" \
  -H "Authorization: Bearer $CULA_ACCESS_TOKEN" \
  -H "Cula-Org-Id: $CULA_ORG_ID" \
  -H "Content-Type: application/json" \
  -d '{ ... }'

# Response headers:
# HTTP/2 201
# Cula-Request-Id: req_01kqzcjrpyf27tge33jwvjhkff
# Content-Type: application/json
Always include the Cula-Request-Id value when contacting support about an issue.