Understand Pinned Events API error responses, status codes, validation errors, authentication failures, forbidden channel access, conflicts, and rate limits.
Error response format
{
"error": {
"code": "invalid_request",
"message": "Request validation failed.",
"requestId": "req_01J...",
"details": {
"field": "classifications",
"issue": "Unknown classification slug \"gig\". Use GET /api/public/v1/classifications to list supported values."
}
}
}Status codes
| Status | Meaning |
|---|---|
| 400 invalid_request | The request body, query, or headers are invalid. |
| 401 invalid_api_key | The API key is missing, malformed, revoked, disabled, or expired. |
| 403 forbidden or insufficient_scope | The key is valid but lacks scope or channel access. |
| 404 not_found | The requested resource does not exist or is not accessible. |
| 409 conflict | The request conflicts with existing state, usually idempotency. |
| 429 rate_limited | The request exceeded a route or policy limit. |
| 500 internal_error | An unexpected server error occurred. |
How to debug
- Check the requestId in logs when contacting support.
- Confirm the API key is active and has the required scope.
- Confirm the key owner still has access to the target channelId.
- Validate classifications with GET /api/public/v1/classifications.
- Use stable Idempotency-Key values for retries.
Related pages
TroubleshootingDiagnose authentication failures, forbidden channel access, validation errors, duplicate events, and rate limits.Create eventsCreate draft or published events with required fields first, then add location, media, ticketing, and publishing options.IdempotencyUse stable Idempotency-Key headers so webhook retries and import jobs do not create duplicate event listings.Rate limitsUnderstand 429 responses, Retry-After handling, and retry strategies for busy integrations.