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

​
List the catalog

GET /connectors/catalog
​
number
Zero-based pagination offset.
​
number
Page size from 1 to 100.
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
​
string[]
required
Between 1 and 100 canonical connector slugs.

​
Check connection status

POST /connectors/status
​
string[]
required
Connector slugs to inspect.
​
string
Tenant for an API-key-based connection.
​
string
Non-PII identifier for the API-served end user who owns the connection.
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
​
string
required
Canonical connector slug.
​
string
Tenant for API-key authentication.
​
string
External end user who will own the connection.
​
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.

​
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.