List files
GET /projects/:projectid/library/files
Returns metadata for the files directly inside a Library directory. It does not download content, search file text, or recurse into subdirectories.
Authentication and request
Use a project key with library.read in Authorization, without Bearer. Replace :projectid with the key's project ID.
The optional path query parameter is a case-sensitive directory path relative to the Library root, such as Reports/Monthly. Omit it for the root. Do not pass a directory ID or add leading/trailing slashes.
Using the Quickstart environment variables:
curl --include --get \
--header "Authorization: ${INTELLECTIBLE_PROJECT_API_KEY}" \
--data-urlencode "path=Reports/Monthly" \
"${INTELLECTIBLE_PUBLIC_API_URL}/projects/${INTELLECTIBLE_PROJECT_ID}/library/files"
Remove the --data-urlencode line to list the root. This endpoint has no pagination or filename-filter parameters.
Response
200 OK returns a files array. For example:
{
"files": [
{
"id": "example-file-id",
"name": "report.pdf",
"mimeType": "application/pdf",
"size": 84213
}
]
}
size is in bytes. Use id for downloads and deletion. Metadata may be incomplete for older or pending files; the listing is not an upload-completion signal.
A directory with no files returns {"files":[]}, even if it contains subdirectories. Use List directories to discover those. Do not rely on a particular listing order.
Errors
- 401: missing, invalid, disabled, or wrong-project key.
- 403: missing
library.read. - 404: no directory matches the supplied path.
- 429: request-rate limit reached.
- 500: the listing could not be retrieved.
A missing directory returns a JSON error message; other failures may be plain text. See Errors, limits and retries.