Quickstart

Prepare

• A Callabo account
• A workspace that allows PAT access
• A terminal with cURL

Issue a PAT

Callabo REST API accepts a personal PAT as a Bearer token.

Authorization header

Add this header to every request.

Authorization: Bearer <PAT>

Steps

1. 1

   Issue a PAT

   Choose a descriptive name and expiration in personal settings, then copy the token.

2. 2

   Store it in an environment variable

   Set CALLABO_PAT without committing it or leaving it in shell history.

3. 3

   Find your workspace slug

   Use the request below to list workspaces you can access. The list can include a workspace where PAT access is disabled.

4. 4

   Find a recent record

   Use the first item from the records list and note its id.

5. 5

   Include dialogs and insights

   Add include=dialogs,insights to the record detail request.

List your workspaces

curl --request GET \
  --url "https://api.callabo.ai/v2/workspaces?status=created&limit=20" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer $CALLABO_PAT"

Find a recent record

curl --request GET \
  --url "https://api.callabo.ai/v2/workspaces/your-workspace/records?order=rec_date&limit=20" \
  --header "Accept: application/json" \
  --header "Authorization: Bearer $CALLABO_PAT"

Next request

Use a returned slug and a record id to call /v2/workspaces/{slug}/records/{record_id}?include=dialogs,insights. A returned slug alone does not prove that workspace-scoped API calls are available to the PAT.

If something fails

• 401: Check for a missing, expired, or mistyped PAT. Also check whether PAT access is disabled for the target workspace.
• 403: After authentication, check the current role's permission for the resource.
• 404: Check slug, record_id, and the current user's access.

Use tokens safely

• Never paste tokens into Git repositories, logs, chat, or documents.
• Use environment variables or an approved secret manager.
• Revoke a PAT immediately and issue a new one if exposure is suspected.