Known V1 Limitations
V1 is an intentionally scoped first release. This documents what V1 does not include and why.
V1 is an intentionally scoped first release. This page documents what V1 does not include and why.
No include or Expansion Parameter
V1 endpoints return a fixed response shape. There is no include or expand query parameter for sideloading related resources. If you need related data, make a separate request to the relevant endpoint.
No Prefixed IDs
V1 uses plain string IDs (e.g., "60d5ec49f1a2c8b1f8e4e1a1"). Resource type is conveyed by the object field on every response, not by an ID prefix.
No Document File Download or Upload
The Documents endpoint returns document metadata only — title, type, version, timestamps. There is no endpoint to download the file contents or upload new files.
No Webhooks
V1 does not support webhook subscriptions or event-driven notifications. To detect changes, poll the relevant list endpoints using cursor-based pagination.
No Fine-Grained Token Scopes
Personal access tokens inherit the full permissions of the user who created them. There is no way to restrict a token to specific boards, resources, or operations.
No OAuth or Third-Party Developer Platform
V1 does not include an OAuth2 authorization code flow, app registration, or any third-party developer platform. All API access is through personal access tokens.
Write Coverage Is Selective
V1 write operations (POST, PATCH) are available for Meetings only. All other resources are read-only in V1.
Planned Additions
- Webhook event subscriptions
- Fine-grained token scopes
- OAuth2 authorization code flow and app registration
- Document file download via signed URLs
- Write endpoints for additional resources
- Bulk operations and async jobs
- Field selection / sparse fieldsets
- WebSocket support for real-time updates