Preview Catalog Operations
Preview the operations of a catalog entry's spec (capped, offset-paginated).
tag and q filter the spec's operations server-side before windowing, so the UI's search box covers every operation in the spec and pages the filtered set via offset/limit ("Load more").
Path parameters
Query parameters
Response
Successful Response
Example response
{
"data": [],
"info": {
"description": "Payments.",
"title": "Stripe",
"version": "2024-01-01"
},
"offset": 0,
"security_schemes": {},
"total": 42,
"truncated": true
}Changes
Changed in 3 of the 85 revisions of this API.329
- ▲
the response's body type/format changed from
/toobject/for status200response-body-type-changed
- ▲
the
detailresponse's property type/format changed fromarray/tostring/for status422response-property-type-changed
- ○
api operation id
preview_catalog_operations_catalog__api_id__operations_getremoved and replaced withpreviewCatalogOperationsapi-operation-id-removed
- ○
the endpoint scheme security
BearerAuthwas added to the APIapi-security-added
- ○
the endpoint scheme security
AgentOauthAccessTokenwas removed from the APIapi-security-removed
- ○
the endpoint scheme security
HumanLoginwas removed from the APIapi-security-removed
- ○
the endpoint scheme security
JenticApiKeywas removed from the APIapi-security-removed
- ○
api tag
Catalogaddedapi-tag-added
- ○
api tag
catalogremovedapi-tag-removed
- ○
added the new optional
queryrequest parameterqnew-optional-request-parameter
- ○
for the
queryrequest parameterlimit, the min was decreased from1.00to0.00request-parameter-min-decreased
- ○
media type
application/jsonwas changed to a more specific media typeapplication/problem+jsonfor the response status422response-media-type-name-specialized
- ○
added the non-success response with the status
400response-non-success-status-added
- ○
added the non-success response with the status
401response-non-success-status-added
- ○
added the non-success response with the status
403response-non-success-status-added
- ○
added the non-success response with the status
500response-non-success-status-added
- ○
added the non-success response with the status
503response-non-success-status-added
- ○
added the optional property
codeto the response with the422statusresponse-optional-property-added
- ○
added the optional property
errorsto the response with the422statusresponse-optional-property-added
- ○
added the optional property
instanceto the response with the422statusresponse-optional-property-added
- ○
added the optional property
statusto the response with the422statusresponse-optional-property-added
- ○
added the optional property
titleto the response with the422statusresponse-optional-property-added
- ○
added the optional property
typeto the response with the422statusresponse-optional-property-added
- ○
the response property
detailbecame required for the status422response-property-became-required
- ○
added the required property
datato the response with the200statusresponse-required-property-added
- ○
added the required property
infoto the response with the200statusresponse-required-property-added
- ○
added the required property
offsetto the response with the200statusresponse-required-property-added
- ○
added the required property
security_schemesto the response with the200statusresponse-required-property-added
- ○
added the required property
totalto the response with the200statusresponse-required-property-added
- ○
added the required property
truncatedto the response with the200statusresponse-required-property-added
This revision also has 61 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲
- ○
endpoint added
endpoint-added
- ○
- ▲
api path removed without deprecation
api-path-removed-without-deprecation
This revision also has 179 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ▲