Shortcut
Published on May 25th, 2026Introduction
The Context Store has several Shortcut templated Data Sources to allow users to quickly pull relevant data into their Data Store. These templates are a starting point and often you'll want to apply filters or chained Data Sources to modify these templates to suit your needs.
Authentication
The built-in shortcut integration uses token/header auth.
Shortcut API tokens do not expose fine-grained per-endpoint scopes in the same way as OAuth scope systems; access is based on the token's workspace/user permissions.
For least privilege:
- Use a dedicated Shortcut token owned by a service account/member with read access to the required workspace entities.
- Ensure the token identity can see members/groups/projects in the relevant workspace(s).
- Rotate token credentials regularly and store them in your secrets manager.
Pre-built Data Sources
This table lists the Shortcut API permissions needed for the Shortcut data source seeds currently defined in this repo.
| Data source seed | Shortcut endpoint(s) used | Required token permission(s) |
|---|---|---|
Shortcut iterations | GET /api/v3/iterations | Workspace token with read access to iterations |
Shortcut epics | GET /api/v3/epics | Workspace token with read access to epics |
Shortcut members | GET /api/v3/members | Workspace token with read access to members |
Shortcut groups | GET /api/v3/groups | Workspace token with read access to groups |
Shortcut projects | GET /api/v3/projects | Workspace token with read access to projects |
