API Contract

CloudRepo’s REST API is specified per endpoint by a persona-aware behavior matrix: for every endpoint, every combination of persona and authentication mode has a documented expected outcome.

Those per-endpoint pages are not published at the moment. They are machine-rendered from the matrices, and the renderer is currently producing pages that describe our internal test fixtures rather than the API a customer calls. Publishing them would document the wrong thing, so the rendered set is withheld until that is fixed. Nothing has been removed from the product: an endpoint’s absence from this section means “not published today”, never “not supported”.

What to use in the meantime

The client guides under Repository Types & Clients cover every operation you drive with a package manager — docker push, npm publish, mvn deploy, pip install and their equivalents — including the repository URL and credentials each one needs. That is the right starting point for almost everything.

If you need to script directly against the REST API and the client guides do not cover it, contact support@cloudrepo.io.

Why a matrix?

Most artifact-repository vendors publish a flat REST reference and leave per-persona authorization behavior implicit. CloudRepo’s matrix makes the per-persona contract explicit: for every endpoint, every persona and auth-mode combination has a documented expected outcome that is continuously probed by our test substrate. If the contract says a readonly user gets 403 on DELETE, our regression suite proves it on every release.

That is what this section will publish, once the rendering of it is worth reading.