Public registry URLs
Fetch published OpenAPI, schemas, and rulesets from registry.pinnate.dev.
Published registry documents are available on https://registry.pinnate.dev (or your deployment’s registry host).
URL shape
https://registry.pinnate.dev/@{orgSlug}/{type}/{slug}
https://registry.pinnate.dev/@{orgSlug}/{type}/{slug}@{version}
Segment | Values |
|---|---|
| Organization slug |
|
|
| Resource slug |
| Optional published version label (for example |
Omit @{version} to fetch the current published document.
Examples
GET https://registry.pinnate.dev/@acme/apis/payments
Accept: application/json
GET https://registry.pinnate.dev/@acme/apis/[email protected]
GET https://registry.pinnate.dev/@acme/schemas/money
GET https://registry.pinnate.dev/@acme/rulesets/spectral-baseline
Content negotiation
Request JSON or YAML via Accept (or the registry’s documented format query). The response body is the published OpenAPI / JSON Schema / Spectral document.
Public vs private
Visibility | Access |
|---|---|
Public | Readable without authentication |
Private | Requires organization membership (browser SSO) or an authorized API key / session |
Tools that pull specs in CI should use a public API or an organization API key when the document is private.
Caching
Treat URLs without a version as “latest” — they can change when you publish. Pin @{version} in production installs and code generators for reproducibility.