Shortcut

REST API at api.app.shortcut.com/api/v3 with clean resource-oriented endpoints. Stories support full CRUD with filtering by workflow state, owner, project, epic, iteration, and label. Search uses a query endpoint with Shortcut's query language. Bulk operations via stories/bulk endpoint enable batch create/update/delete — a notable advantage for agents doing mass operations. The Story object includes estimate, deadline, story type (feature, bug, chore), and linked branches/PRs. Epics group stories across projects. Iterations are time-boxed sprints. Webhook events cover story and epic lifecycle. Response payloads are consistent and well-typed. Labels serve as the primary categorization mechanism (no custom fields). Pagination uses cursor-based tokens.

API errors return JSON with message field and standard HTTP status codes (400, 401, 403, 404, 422, 429). Rate limits are documented at 200 requests per minute per token — adequate for most agent workloads but requires throttling for bulk operations. 429 includes Retry-After. Bulk story operations (up to 25 stories per request) reduce the rate limit impact significantly. Validation errors on story creation are descriptive — invalid workflow state, missing required fields, and invalid references are clearly reported. Webhook delivery retries failed webhooks. The API is generally reliable with good uptime. Story search query syntax errors return helpful messages indicating the syntax issue.

Shortcut (formerly Clubhouse) is a project management tool built specifically for software teams, positioned between Jira's enterprise complexity and Trello's simplicity. For agents, the REST API v3 covers stories (tasks), epics, iterations, milestones, labels, workflows, and members. The data model is clean: stories have a workflow state, belong to a project, can be organized in epics and iterations. GitHub/GitLab integration automatically links branches and PRs to stories, making it natural for agents that coordinate code changes with issue tracking. The API is well-designed with consistent patterns across resources. Main limitations: no built-in time tracking, no custom field types (stories have fixed fields plus labels), and smaller ecosystem than Linear or Jira.

API tokens are generated in Settings → API Tokens. Tokens use the Shortcut-Token header (not Bearer). Each token has full API access — no permission scoping. Tokens persist until revoked. No OAuth for third-party apps (the integration model is simpler than marketplace platforms). For agents, it's one token per user, full access, straightforward. No temporary credentials, no role-based token restrictions. Webhook verification uses a signing secret. The simplicity is appropriate for the tool's target audience (small-to-medium engineering teams) but limits multi-tenant agent architectures. IP restriction is not available.

API documentation at shortcut.com/api is clean, well-organized, and complete. Every endpoint is documented with parameters, response shapes, and curl examples. The documentation includes a comprehensive data model reference showing relationships between resources. OpenAPI spec is available for client generation. Python and Node community SDKs exist but the API is clean enough that most agents can use raw HTTP. The migration guide from Clubhouse to Shortcut branding is complete. Developer community is smaller than Jira's or Linear's but the API's simplicity reduces the need for community support. Webhook documentation lists all event types with payload examples. For agents, the documentation-to-production path is fast — the API surface is small enough to learn entirely.