Reference

This section is the single source of truth for facts about Aura that show up everywhere else in the docs: webhook event names, API key scopes, pipeline stage definitions, supported integrations, and validation rules.

Every page here is auto-generated from the same TypeScript files that validate live production traffic. A CI gate enforces that the page content stays in lockstep with its source — if an engineer changes the underlying code without regenerating this section, the build fails until they do.

Use this section when you need an authoritative answer to:

• "What webhook events does Aura emit?" → Webhook Events
• "What scopes can an API key have?" → API Key Scopes
• "What are the pipeline stages?" → Pipeline Stages
• "Which integrations are supported?" → Supported Integrations
• "What are the booking link length limits?" → Booking Link Constraints

How this section stays accurate

1. Engineers change a constant in the codebase (e.g., add a new webhook event type).
2. CI runs the facts drift check; it fails because the snapshot is out of date.
3. The engineer runs bun run --filter=@aura/docs facts:snapshot to regenerate the snapshot and these pages.
4. They commit the updated snapshot + pages alongside the code change.
5. CI passes; the new fact is now visible to customers AND to support tooling that grounds on these docs.

Total cost of keeping docs accurate: one extra step in the PR. Total cost of NOT having this gate: stale customer-facing claims (e.g., "scoped permissions coming soon" when they shipped 6 months ago).

Stats at a glance

• 14 webhook event types
• 3 API key scopes
• 13 pipeline stages
• 10 supported integrations
• 3 webhook retry attempts with backoff at 1 second, 5 seconds, 15 seconds