Authenticate to the Event Temple API using the OAuth 2.0 Client Credentials grant for private/backend integrations
domain: api.eventtemple.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In your Event Temple sandbox, go to Settings > Developers > Apps (or Chain-level settings if managing multiple properties) and create a private OAuth app to get a client_id and client_secret
POST to https://api.eventtemple.com/oauth/token with grant_type=client_credentials, client_id, client_secret, and a space-delimited scope like "crm_read crm_manage"
Store the returned access_token (expires in 7200 seconds / 2 hours) and use it as a Bearer token on subsequent calls
Call endpoints such as GET https://api.eventtemple.com/v2/bookings with an Authorization: Bearer header
Include the X-API-ORG header with the target organization's API Org ID (found under Settings > Overview or via the organizations endpoint) on every request that needs it
Known gotchas
Client Credentials is for machine-to-machine/private apps only; to act on behalf of individual end users across multiple Event Temple customers, use the Authorization Code grant instead
Many endpoints require the X-API-ORG header to scope the request to the right property in a multi-property chain — a missing header can silently return the wrong org's data
Legacy API Key Authentication is marked Deprecated in the docs; new integrations should use OAuth 2.0
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?