The browser generates an OpenAPI 3.1 document describing the API as it exists on your installation.
Downloading
From the admin browser, click OpenAPI (JSON) or OpenAPI (YAML) in the page actions. The URLs are:
| Format | Admin (everything your role can see) | Public (chosen resources, read-only) |
|---|---|---|
| JSON | /admin/api-browser/openapi.json |
/api-browser/openapi.json |
| YAML | /admin/api-browser/openapi.yaml |
/api-browser/openapi.yaml |
The admin URLs require a logged-in admin session. The public URLs are available to anyone and contain only the resources selected under Configuration.
What the document contains
- A
serversentry pointing at your site's/apibase URL. - For each resource, the collection and item paths with the operations available:
getfor search and read,post,put,patchanddeletewhere permitted. - Query parameters for search operations, taken from the same catalog the browser displays.
- A component schema per resource built from its JSON-LD keys and entity fields, referenced by the responses.
- An API key security scheme using the
key_identityandkey_credentialquery parameters.
Using it
The document works with the usual OpenAPI tooling: import it into Postman or Insomnia, feed it to a client generator, or publish it with Swagger UI or Redoc. Regenerate it after installing or removing modules so it reflects the current set of resources.