Fix common Pinned Events API integration issues including 401, 403, validation errors, wrong channelId, duplicate events, revoked keys, and missing scopes.
403 Forbidden
- Confirm the API key has the required scope.
- Confirm the key owner can still access the target channelId.
- Confirm the channelId belongs to the account that created the key.
Missing scope
A missing scope produces a 403 response after the API key is authenticated. Check the route documentation for the required scope and add only that permission to the integration key.
Wrong channelId
If the channelId is valid but not accessible to the key owner, the API rejects the request. Call GET /api/public/v1/channels with the same key and use one of the returned channel IDs.
Validation errors
Validation errors usually mean a required field is missing, a date or timezone is invalid, a public classification slug is unknown, or an ID refers to a resource the key cannot use.
Duplicate events
- Send an Idempotency-Key header on create-event requests.
- Use the same key when retrying the same source event and action.
- Do not generate a new random idempotency key on every retry.
Rate limits
A 429 response means the request exceeded a route, IP, key, or key-management policy limit. Honor Retry-After when present and retry with backoff.
Lost API key secret
Full API key secrets are shown only once. If a secret is lost, create a replacement key, deploy it, verify the integration, then revoke the old key.
Event not visible
- Check whether the event was created as a draft or published listing.
- Check the event date, timezone, and channel placement.
- Check ticket links, images, and required moderation or review states.