API reference

344 operations across 27 groups. Every operation has its own page, so you can link straight to one.

The raw document is published at /openapi.json. Responses shared by nearly every operation are documented once, understandard errors (31 of them).

• CI50 operationsCI workflow / run / runner control plane (ADR 0014, 0017).
• Repositories46 operationsRepository discovery, creation, views, and projections.
• Sessions42 operationsPassword login and browser session lifecycle.
• Pull Requests32 operationsChange request (pull request) lifecycle, reviews, and revisions.
• Issues25 operationsTeam-scoped (KEY-N) and repo-bound (acme/api#42) issue lifecycle.
• GitHub23 operations
• Organizations22 operationsOrg workspaces and their member rolls.
• Labels11 operationsRepo- or team-scoped labels and their attachment to issues.
• Teams11 operationsWorkspace-scoped teams. Owners of issue numbering and planning surfaces.
• Packages9 operations
• Users9 operationsUser profiles and per-user repository listing.
• Webhooks9 operationsWebhook management and delivery history.
• Cycles8 operationsTeam-scoped planning windows. Issues bind to at most one cycle.
• Mirrors6 operationsPush-only mirror replication to GitHub / GitLab / generic git hosts.
• Notifications6 operationsPer-recipient inbox: mentions, review requests, assignments, status changes.
• Releases6 operations
• CLI4 operationsBrowser-mediated CLI login session flow.
• Comments4 operationsPolymorphic comments — issue / PR / review-thread replies.
• Events4 operationsServer-sent repository activity streams.
• Owners4 operationsUnified handle lookup — resolves to a user or org.
• Tokens4 operationsPersonal access token management.
• SSH Keys3 operationsSSH public key management for Git+SSH access.
• System2 operationsService health and process-level metadata.
• Attachments1 operation
• Feedback1 operation
• Search1 operationPostgres FTS over issues, pull requests, and comments.
• Sync1 operationNative jj sync protocol — pull, push, and object transfer.