Every integration request requires an Outlit API key:Documentation Index
Fetch the complete documentation index at: https://docs.outlit.ai/llms.txt
Use this file to discover all available pages before exploring further.
Provider IDs
Use the currently enabled public provider IDs below when calling integration routes.| Provider ID | Name | Category | Direct config support |
|---|---|---|---|
hubspot | HubSpot | CRM | Browser session |
attio | Attio | CRM | Browser session |
slack | Slack | Communication | Browser session |
fireflies | Fireflies.ai | Calls | apiKey |
granola | Granola | Calls | apiKey |
google-calendar | Google Calendar | Calendar | Browser session |
google-mail | Gmail | Communication | Browser session |
posthog | PostHog | Analytics | apiKey, region, projectId |
stripe | Stripe | Billing | apiKey |
supabase | Supabase Auth | Analytics | projectUrl, serviceRoleKey |
clerk | Clerk | Analytics | secretKey |
pylon | Pylon | Support | apiToken |
Use
google-mail for direct API requests. The CLI also accepts gmail as a convenience alias.List Integrations
When
true, only returns currently connected integrations.Example
Response
Get Setup Capabilities
Optional public provider ID or CLI alias. When omitted, returns all provider capabilities.
Response
Run Provider Setup Step
postConnectSteps reports a supported follow-up such as CRM mappings or webhooks.
Request Body
Public provider ID from setup capabilities.
Follow-up step token, such as
mappings or webhooks.Optional step-specific config. CRM mappings use
{ "mappings": [...] }; Stripe webhooks can use { "webhookSecret": "whsec_..." }; Fireflies webhooks can use { "webhookSecret": "..." }.config_required response. Webhook setup returns the URL, headers/secrets, required events, and status needed for manual provider setup without creating a browser session.
Connect Integration
Request Body
Public provider ID from the provider table.
Required for direct credential connections. Omit this field to create a browser-auth connection session.
Direct Credential Response
Browser Session Response
connectUrl in a browser where the user can complete the provider connection, then poll the connect status route with sessionId. Direct credential setup, such as Pylon API-token setup, returns the direct credential response and does not create a session ID.
Errors
Invalid providers or malformed JSON return400. Connection-limit failures return 403:
Poll Connection Status
Session ID returned by
POST /api/integrations/connect.Response
status is one of pending, connected, failed, or expired. Failed responses may include error.
Get Sync Status
Public provider ID from the provider table.