API Reference / Knowledge - Integrations
Create integration
post
https://api.intelig.ai/api/v1/intelig/settings/integrations/knowledge
Auth: Authorization: ApiKey <key> (an API key sent as
Bearer is rejected) or Authorization: Bearer <jwt>
for a dashboard session. operationId: createIntegration
Creates a new knowledge provider integration. Validates the API key with the provider, automatically registers a webhook, and stores credentials. The integration starts in an inactive state.
Example request
curl -X POST "https://api.intelig.ai/api/v1/intelig/settings/integrations/knowledge" \
-H "Authorization: ApiKey $INTELIG_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"provider": "FATHOM",
"apiKey": "fathom_sk_live_9f2c4d1a8b3e"
}' Request body
application/json
| Field | Type | Required | Description |
|---|---|---|---|
provider | string | yes | Knowledge provider type One of: GITHUB, GITLAB, BITBUCKET, AZURE_DEVOPS, FATHOM, OTTER, FIREFLIES, ZOOM, TEAMS, LOOM, GRANOLA, MANUAL Example: FATHOM |
apiKey | string | yes | The provider's own API key, as issued by them. Stored encrypted and never returned by any read endpoint. Example: fathom_sk_live_9f2c4d1a8b3e |
Response 201
application/json · ApiResponseProviderIntegrationDto
| Field | Type | Description |
|---|---|---|
success | boolean | — |
message | string | — |
data | ProviderIntegrationDto | Provider integration configuration details |
Status codes
201— Integration created successfully400— Invalid request body or duplicate provider401— Organization context not set403— Insufficient permissions for Settings pillar429— —
Every response is wrapped in { success, message, data }. A 4xx means the request
is wrong — do not retry it unchanged. A 429 carries Retry-After in seconds.