Using the API
Request IDs
Every response carries an X-Request-Id; log it, or send your own, to trace a request end to end.
Every response, success or error, has an X-Request-Id header naming that request:
HTTP/1.1 401 Unauthorizedcontent-type: application/jsonx-request-id: 2fd60418-f920-48e9-a27a-d3f074d4e36fLog it next to your own records. When you contact support about a request that failed or did something you didn't expect, include its request ID: it finds that exact request in Anyrow's logs.
Send your ownLink to section
Set X-Request-Id on the request and Anyrow uses it instead of making one, so one ID follows a
request from your system through Anyrow and back:
curl "https://api.anyrow.ai/v1/projects/$PROJECT_ID/tables" \ -H "Authorization: ApiKey $ANYROW_API_KEY" \ -H "X-Request-Id: import-2026-10-16-0042" \ -iThe response's X-Request-Id is the one you sent. Use an ID that is unique per request, such as
a UUID.
Read it in an SDKLink to section
curl -s -D - -o /dev/null "https://api.anyrow.ai/v1/projects/$PROJECT_ID/tables" \ -H "Authorization: ApiKey $ANYROW_API_KEY" | grep -i x-request-idEvery SDK call also takes extra headers, so you can send your own ID the same way you set any other header.