Core guides
Choose a guide
Quickstart, reference, and operational guidance for Aurora integrations.
API quickstart
Get a token, validate it, run discovery, and make your first read and write calls without guessing at ids.
API reference
Browse endpoint families, supported methods, parameters, and operational notes for projects, issues, comments, and meetings.
Developer guide
Build retry-safe clients with caching, pagination, structured errors, automation queues, and agent-aware workflows.
Structure
What these docs cover
Quickstart material, endpoint reference, and operational guidance for authentication, retries, pagination, and automation.
Core API model
Understand the external API shape before you make your first call.
- Workspace-scoped authentication
- Natural key lookup for projects and issues
- Human and automation assignment models
- Comments and meetings in the same contract
Operational integration guidance
Build clients that stay correct when tokens, queues, retries, and pagination are in play.
- Discovery-first bootstrapping
- Idempotency patterns for create flows
- Cursor pagination and cache strategy
- Structured error recovery for agents
Documentation structure
Use cases
Common build paths
Representative integration shapes across automation, backend sync, agent workflows, and meeting pipelines.
Personal automation
Use a workspace token to script issue triage, reporting, comments, or project setup for one workspace.
Backend integration
Mirror Aurora data into another service or push execution updates in from your internal systems.
AI agent workflows
Treat Aurora as an execution system of record with discovery-first reads, idempotent writes, and visible follow-up comments.
Meeting-to-task pipelines
Use the meetings and agenda endpoints to convert discussions into issues while preserving owners and workflow state.
Guide order
Documentation map
Quickstart first, reference second, operational guidance after that.
1. Quickstart
Use /docs/api when you need a token, a first request, a discovery pass, and working cURL examples.
2. Reference
Use /docs/api/reference when you need paths, methods, and endpoint-family behavior in one place.
3. Developer guide
Use /docs/api/developer-guide when you are building long-lived clients, agents, or queue-driven workflows.