Repopack's programmatic clients, including rp, use /api routes. Browser UI uses separate session-authenticated routes. An authenticated browser session does not grant access to the API; clients must use the authorization required by the relevant endpoint.
Where to begin
The versioned API lives under https://repopack.com/api/v0/. Start with human-approved API credentials, then read a project and search or read visible tasks. For writes, understand guarded actions and why a submitted head and review verdict are different operations. Endpoint permissions differ by resource and operation. A request presenting invalid or expired credentials must not be treated as an anonymous request just because some Release data is public.
To explore an existing project workflow from a terminal, start with the rp reference. For the model of task submission and review, see task turns. The endpoint directory below lists verified contracts, not every route on the server. Use the CLI and its help for operations not yet documented here; do not infer that an unlisted route is supported for public integration.
Request body limits
Buffered JSON, URL-encoded form and text bodies are limited to 1 MiB by
default. Multipart and binary readers default to 16 MiB total. Oversized
bodies return 413 Payload Too Large, including when no Content-Length is
sent. A task-context force flag does not bypass the body limit. Release
prepare and publish accept up to
48 MiB of encoded JSON so existing base64 metadata attachments still fit;
their decoded limits remain 8 MiB per file and 32 MiB total. These are buffered
reader limits, not a streaming upload facility; proxy/transport limits can also
apply.
Release distribution
Programmatic Release distribution uses canonical paths under /api/v0/projects/<key>/releases/products/<product>/…. The permanent project key keeps generated URLs valid across display-name renames. Public channels can allow anonymous access to their eligible Releases; private resources require the appropriate API authorization. Browser routes under /project/<key>/releases/… use session authentication and are not URLs for programmatic clients.
Versioned schema documentation is tracked separately. The method directory above is curated, not a generated schema registry or a promise that every server route is a public integration contract.
CLI compatibility
RP-Version is optional. Requests without it (for example, from curl) proceed
normally. If present, it must be a SemVer version; malformed values return
400 invalid_rp_version. The minimum supported version is 0.3.0.
An older CLI receives 426 cli_version_unsupported with required_version
before its operation executes. Reads used by rp update remain available.