Debug
Keep the request ID
Every v1 response includes X-Greenroom-Request-Id. Include it when reporting a failed integration.
Connecting to Greenroom
Credentials and delivery
Create credentials, connect a calendar app, and choose where Greenroom sends change events.
API keys
A key acts as its owner and inherits that account's role. Store it as a secret, never ship it in browser code, and revoke it when the integration is retired.
Credentials
Keys act as your account. Keep them server-side and revoke anything you no longer use.
Connected apps
OAuth grants calendar-only access with S256 PKCE. Webhooks deliver signed calendar changes to a public HTTPS endpoint.
Debug
Every v1 response includes X-Greenroom-Request-Id. Include it when reporting a failed integration.
Retries
Send an Idempotency-Key with create requests. Greenroom remembers the result for 24 hours.
Agents
The MCP server checks the API key on every tool call, so revocation stays immediate.