List collections visible to the api-key
/collectionsCollections the linked user can see: their own, public ones, and
those shared with them or their usergroup. Ordered by name.
Requires the read scope.
Authorization
apiKey Issued to you when your integration is provisioned. Determines which catalogue resources are visible and which AI tools are available.
In: header
Query Parameters
Page size (max 100).
1 <= value <= 100250 <= value0Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/collections"{ "data": { "items": [ { "ref": 55, "name": "Spring catalogue", "resourceCount": 12, "created": "2026-07-01 10:00:00" } ], "total": 1, "limit": 25, "offset": 0 }}{ "success": false, "status": "fail", "message": "API key is required", "error": { "code": "NO_API_KEY", "message": "API key is required" }}{ "success": false, "status": "fail", "message": "This API key does not have the 'write' scope", "error": { "code": "INSUFFICIENT_SCOPE", "message": "This API key does not have the 'write' scope" }}List resources in a collection GET
Resources in the collection, in the collection's own sort order. Includes both active and archived resources (see each item's `archive` flag). Requires the `read` scope and read access to the collection.
Add resources to a collection POST
Adds up to 100 resources per call. Requires the `write` scope and modify access to the collection (owner, or the collection allows changes). Each ref is validated for visibility to the api-key's linked user before adding; the response reports a per-ref status: - `added` — newly added to the collection. - `already_present` — was already in the collection (no-op). - `not_found` — the resource doesn't exist **or** isn't visible to the linked user (not distinguished). Adding is naturally idempotent: retrying the same request reports the previously added refs as `already_present`.