Request IDs

Every API response includes an X-Request-Id header. Use this identifier to correlate a client operation with server logs and support requests.

The API generates a UUID when the request does not provide an identifier. A client can instead send its own unique value, which the service returns in the response.

Client-generated IDs

Generate a different identifier for each logical request and retain it with the response status. A readable prefix can identify the integration job or workflow, while a UUID or similarly unique suffix prevents collisions.

Do not place credentials or personal data in a request ID because it can be recorded in logs.

Support and diagnostics

Include the request ID when contacting célula.in about a failed or unexpected operation. For a retry, generate a new request ID and retain a link to the original attempt in your own logs.

X-Request-Id is for tracing. Supplying the same value again does not make an operation idempotent.

Client-generated request ID

curl https://api.celula.in/v1/people/me \
  --header "X-CIN-API-Token: $CELULAIN_CLIENT_TOKEN" \
  --header "Authorization: Bearer $CELULAIN_ACCESS_TOKEN" \
  --header "Accept: application/vnd.api+json" \
  --header "X-Request-Id: integration-job-20260817-00042"

Response header

HTTP/1.1 200 OK
Content-Type: application/vnd.api+json
X-Request-Id: integration-job-20260817-00042