Get Catalog Model
Changed onOne model and every offering of it this caller may use.
The whole merged catalog is built and grouped to answer for one model. That is deliberate: the identity a model is found by is a property of the group, so narrowing the build to one model would need the grouping done first. The query count is constant; the cost is CPU per page view, growing with the size of the catalog rather than with the number of readers.
A model the caller may not see answers 404, the same as one that does not exist, so the route cannot be used to probe the catalog behind an allow-list. A signed-in caller's offerings also carry their organization's own usage of each over the last 30 days.
Request
- The document declares no server URL.
- Auth: one of:
- API key in header Otari-Key
- API key in header x-api-key
Path parameters
Response
Successful Response
Changes
- info
added the optional property
to the response with the status
- info
- info
endpoint added
- info