List resources in a collection
/collections/{ref}/resourcesResources 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.
Authorization
apiKey Issued to you when your integration is provisioned. Determines which catalogue resources are visible and which AI tools are available.
In: header
Path Parameters
Collection id.
Query Parameters
1 <= value <= 100480 <= value0Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/collections/0/resources"{ "data": { "items": [ { "ref": 101, "title": "A Book of Verse", "resourceType": 0, "resourceTypeName": "Document", "fileExtension": "epub", "created": "string", "archive": 0 } ], "total": 0, "limit": 48, "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" }}{ "success": false, "status": "fail", "message": "string", "error": { "message": "API key is required", "code": "NO_API_KEY" }}Remove a resource from a collection DELETE
Removes the resource from the collection (the resource itself is untouched). Requires the `write` scope and modify access to the collection. Returns 404 when the resource is not in the collection, so retries of an already-applied delete fail loudly rather than silently — treat 404 after a retry as "already removed".
List collections visible to the api-key GET
Collections the linked user can see: their own, public ones, and those shared with them or their usergroup. Ordered by name. Requires the `read` scope.