List resource types visible to this api-key
/resources/typesAuthorization
apiKey Issued to you when your integration is provisioned. Determines which catalogue resources are visible and which AI tools are available.
In: header
Response Body
application/json
curl -X GET "https://example.com/resources/types"{ "success": true, "status": "success", "message": "Success", "data": {}}Search resources (lightweight) GET
Previous Page
Structured catalogue query (counts + listings) POST
Answers literal catalogue questions — counts and metadata listings — without a chat. This is the direct-REST door for the AI chat's `catalog_query` tool and reuses it verbatim, so results carry EXACT server-side totals (`totalRecords`, and `distinctTitles` for unique titles counted once across formats/editions). Use it for who/where/when and how-many questions: "how many books by Agatha Christie", "list our Avon titles", "what did we publish in 2023". For topic/theme intent ("books about vampires") use `POST /resources/search` with `mode: vector` instead. The primary interface is `filters` — a list of `{field, op, value}` conditions, ANDed together. A bare `query` string is a convenience: with no `filters` it maps to a single `title` contains condition. Call `GET /resources/fields` to discover the fields available on this tenant. All results are filtered by the linked user's usergroup — the same access walls the in-app search applies.