Reference5 min~81 words
Requests and responses
Headers, request identifiers, success envelopes and safe caching behaviour.
Request headers
| Header | Required | Purpose |
|---|---|---|
Authorization: Bearer <key> | Yes | Authenticates the API key. |
Accept: application/json | Recommended | Declares the expected response type. |
X-Request-ID | Optional | Supplies your own trace identifier when it matches the accepted safe format. |
Success envelope
HTTP 200
{
"ok": true,
"request_id": "9dbbe78b-5f5d-4e76-9ed3-77b7f7507c90",
"data": {
"projects": []
},
"meta": {
"pagination": {
"page": 1,
"per_page": 25,
"total": 0,
"total_pages": 0,
"has_more": false
}
}
}Every response includes X-Request-ID and Cache-Control: no-store. Rate-limited authenticated responses also include current limit headers.
Need project-specific help?
Open the private Help Center or create a support ticket with the affected project, route and request ID.