Authenticate to the Event Temple API using the OAuth 2.0 Authorization Code grant for public 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
Register your integration to obtain a client_id, then redirect users to https://client.eventtemple.com/oauth/authorize with client_id, redirect_uri, scope, and response_type=code
Capture the code parameter Event Temple appends to your redirect_uri after the user grants access
Exchange the code via POST https://api.eventtemple.com/oauth/token with grant_type=authorization_code, code, redirect_uri, client_id, and client_secret
Store the returned access_token and refresh_token, then call the API with Authorization: Bearer <access_token> and an X-API-ORG header
Refresh expired tokens with a POST to /oauth/token using grant_type=refresh_token, and revoke tokens via POST /oauth/revoke when access should end
Known gotchas
Public apps built for a wide audience must eventually be published by the Event Temple team — you develop and test against a private app first, then Event Temple converts it to public
Access tokens are short-lived (2 hours); integrations that don't implement the refresh flow will silently start failing after 2 hours
The authorize URL host (client.eventtemple.com) differs from the API/token host (api.eventtemple.com) — don't send token requests to the authorize subdomain
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?