Answers to common Pinned Events API questions about CMS integrations, CRM publishing, channelId, external ticketing, idempotency, frontend use, scopes, OpenAPI, and webhooks.
Common questions
| Question | Answer |
|---|---|
| What is the Pinned Events API? | A REST API for publishing events into Pinned Events channels for local discovery, RSVP, reminders, and social planning. |
| Can I create events from my CMS? | Yes. Use your backend or CMS webhook to create draft or published events through POST /api/public/v1/events. |
| Can I publish events from a CRM? | Yes. CRM or back-office records can map to Public API event payloads. |
| Do I need a channelId? | Yes. Every event is published into a channel owned or accessible by the API key owner. |
| Can I keep existing ticketing? | Yes. Use Pinned Events for discovery and planning while keeping external ticketing for checkout. |
| How do I avoid duplicate events? | Use a stable Idempotency-Key for retries of the same source event. |
| Can I use the API from frontend JavaScript? | No. API keys are bearer secrets and must stay on trusted server-side systems. |
| What scopes do I need? | New quickstart keys start with channels:read and events:create. Add read, update, or media scopes only when the integration needs them. |
| Does the API support OpenAPI? | Yes. The OpenAPI YAML is publicly available from /api/developer/openapi/public-api-v1. |
| Does the API support webhooks? | Inbound event publishing from your webhooks is supported through your backend. Outbound Pinned Events webhooks are not documented as part of this release. |
Related pages
Getting startedCreate an API key, find a channelId, publish your first event, and retry safely.AuthenticationAuthenticate Public API requests with bearer API keys from trusted server-side code.Create eventsCreate draft or published events with required fields first, then add location, media, ticketing, and publishing options.TroubleshootingDiagnose authentication failures, forbidden channel access, validation errors, duplicate events, and rate limits.