Quickstart
Make your first authenticated request by listing the files in your project's Library. This is a read-only operation: it does not upload, change, or delete anything, and it works even if the Library is empty.
You will need an Intellectible project, access to its API keys section, and a terminal with curl. The shell examples below work in Bash or Zsh.
1. Create a project API key
- Open your project and select API keys in the project navigation.
- Click Create API key and give it a name, such as
API quickstart. - Expand Library permissions and enable Browse for the project Library. This grants
library.read; no write or delete permissions are needed. - For this local example, leave Make available to code running on Intellectible off.
- Create the key and copy the complete token, which looks like
proj.KEY_ID.SECRET.
The secret is shown once. Store it securely and do not paste it into source files, logs, or agent conversations. See API keys for more about managing credentials.
2. Configure your terminal
Find your project ID in the app's URL: it is the value immediately after /project/, not the project's display name.
Set the base URL and replace YOUR_PROJECT_ID below with that ID:
export INTELLECTIBLE_PUBLIC_API_URL="https://app.intellectible.com/api/publicv1"
export INTELLECTIBLE_PROJECT_ID="YOUR_PROJECT_ID"
If you are using the test environment, use https://testapp.intellectible.com/api/publicv1 and a project and key from that environment.
Then run this block, paste the complete key at the prompt, and press Enter. The input is hidden and the key is not included in the command you type into shell history:
printf 'Project API key: '
read -r -s INTELLECTIBLE_PROJECT_API_KEY
printf '\n'
export INTELLECTIBLE_PROJECT_API_KEY
These variables apply to the current terminal session. Keep the credential on the server side when you move the example into an application; never expose it in browser code.
A configured module can receive these variables automatically. Grant its key Library → Browse, then use the supplied environment values instead of replacing them. See Using project services.
3. Make the request
Run this command in the same terminal:
curl --include --request GET \
--header "Authorization: ${INTELLECTIBLE_PROJECT_API_KEY}" \
"${INTELLECTIBLE_PUBLIC_API_URL}/projects/${INTELLECTIBLE_PROJECT_ID}/library/files"
The key goes directly in the Authorization header, without a Bearer prefix. This GET request has no request body. The --include option shows the HTTP status and response headers alongside the response body.
4. Read the response
A successful request returns 200 OK and a JSON object containing a files array. For example, a Library with a file in its root directory might return:
{
"files": [
{
"id": "example-file-id",
"name": "notes.txt",
"mimeType": "text/plain",
"size": 128
}
]
}
Your file IDs and metadata will differ. If there are no files in the root directory, this is also a successful response:
{
"files": []
}
This request lists files in the Library root, not files inside its subdirectories. An empty result does not mean authentication failed.
If the request fails
- 401 Unauthorized: check that you copied the entire key, did not add
Bearer, and used the project and environment it belongs to. A disabled, deleted, or rotated key will not work. - 403 Forbidden: check that the key has Library → Browse (
library.read). Save any permission changes and try again. - 404 Not Found: check the base URL and request path, including
/api/publicv1and the plural/projects/. - 429 Too Many Requests: pause and reduce your request rate before retrying.
Do not assume every error body is JSON. Check the HTTP status and response text when troubleshooting.
Next steps
You have now made an authenticated request to a project service. Choose the next operation your integration needs and grant only the permissions it requires:
- Workflows — call reusable logic from your application.
- Library — browse directories, upload files, and download content.
- Databases — read and update structured data.
- AI — generate responses and use other AI services.
For access rules and failure handling, continue with Authentication and permissions and Errors, limits and retries.
If you created a key only to try this example, disable or delete it in API keys when finished. Clear it from the current terminal session with:
unset INTELLECTIBLE_PROJECT_API_KEY