Skip to main content
Connectors are the connected apps that chats and agents can use. The catalog describes available integrations; connection endpoints bind an account to the current user or an API-served external subject.
Catalog and connection endpoints are [User+Key]. API keys use connectors:read, connectors:write, or connectors:delete. The provider callback is public and validates its signed state.

​
Endpoints

MethodPathDescriptionAuth
GET/connectors/catalogList available connectors[User+Key]
POST/connectors/catalog/by-slugsGet catalog entries by slug[User+Key]
POST/connectors/statusCheck connection status[User+Key]
POST/connectors/addStart an account connection[User+Key]
DELETE/connectors/:slugDisconnect an account[User+Key]
GET/connectors/auth/callbackComplete provider authorization[Public callback]

​
List the catalog

GET /connectors/catalog
​
offset
number
Zero-based pagination offset.
​
limit
number
Page size from 1 to 100.
curl "$AUTOSAGE_URL/connectors/catalog?limit=25" \
  -H "Authorization: Bearer $AUTOSAGE_KEY"
The response contains connector records with their canonical slug, display name, description, logo, and category, plus pagination fields.

​
Get connectors by slug

POST /connectors/catalog/by-slugs
​
slugs
string[]
required
Between 1 and 100 canonical connector slugs.
curl -X POST "$AUTOSAGE_URL/connectors/catalog/by-slugs" \
  -H "Authorization: Bearer $AUTOSAGE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "slugs": ["gmail", "slack"] }'

​
Check connection status

POST /connectors/status
​
slugs
string[]
required
Connector slugs to inspect.
​
tenant_id
string
Tenant for an API-key-based connection.
​
external_subject_id
string
Non-PII identifier for the API-served end user who owns the connection.
curl -X POST "$AUTOSAGE_URL/connectors/status" \
  -H "Authorization: Bearer $AUTOSAGE_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "slugs": ["gmail"],
    "tenant_id": "TENANT_ID",
    "external_subject_id": "CUSTOMER_123"
  }'
Use a stable, non-PII external_subject_id. A different value resolves to a different connected-app identity and cannot access the original subject’s connection.

​
Connect an account

POST /connectors/add
​
slug
string
required
Canonical connector slug.
​
tenant_id
string
Tenant for API-key authentication.
​
external_subject_id
string
External end user who will own the connection.
​
redirect_url
string
Final destination after AutoSage completes the provider callback.
The response includes a redirect_url for the account authorization flow and an already_connected boolean. Open the URL in the user’s browser.

​
Disconnect an account

DELETE /connectors/:slug For API-key calls, pass tenant_id and external_subject_id as query parameters so AutoSage resolves the same connection owner used during setup. 
curl -X DELETE \
  "$AUTOSAGE_URL/connectors/gmail?tenant_id=TENANT_ID&external_subject_id=CUSTOMER_123" \
  -H "Authorization: Bearer $AUTOSAGE_KEY"

​
Authorization callback

GET /connectors/auth/callback This browser callback receives provider status, account information, and signed state. Applications normally do not call it directly: start with /connectors/add and follow the returned redirect URL.
Use /swagger for complete callback and response schemas. After connecting an account, verify it with /connectors/status before enabling its slug on an agent.

​
Next steps

Configure agents

Enable connected apps on a deployed agent.

Agents API

Check integration readiness and deploy connector slugs.