API Overview
Understand the supported Done Bear API surface, including REST endpoints, API keys, GraphQL reads, and the sync transport.
The Done Bear API has three layers: REST for workspace and API-key management, GraphQL for curated reads, and sync for advanced clients. Start with REST. Use GraphQL for reads. Use sync only if you need transport-level behavior.
Base URL
Use the production API host:
curl https://api.donebear.com/api/workspaces \
-H "Authorization: Bearer <token>"Authentication
Send bearer credentials in the Authorization header. The API accepts:
- Supabase JWTs
- Done Bear API keys that start with
db_
Example:
curl https://api.donebear.com/api/workspaces \
-H "Authorization: Bearer <token-or-api-key>"Choose the right surface
| Surface | Best for | Start here |
|---|---|---|
| REST | Workspace management and API-key lifecycle | REST API reference |
| GraphQL | Curated reads for tasks, projects, teams, labels, users, and workspaces | GraphQL reference |
| Sync | Bootstrapping, delta polling, mutations, and live updates | Sync API reference |
Support notes
These docs cover the supported subset of the API. REST is the stable starting point. GraphQL is documented as a curated read surface. Sync is documented as an advanced transport layer.
Next steps
- Follow Authenticate API requests to send the right bearer credentials.
- Use REST API reference for workspace and API-key operations.
- Use GraphQL reference for read queries.