Remove the API connection identified by connection_id from integrations.ListApiConnections. This prevents Brigg from making new calls through that connection; it does not delete records in the external system.
Allow integrations.DeleteApiConnection on your API key.
Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.
Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.
connection_idstringRequired
Use connection_id from the outbound connection catalogue. This does not identify your calling Brigg API key. integrations.ListApiConnections.
At least 1 character. At most 41 characters.
Response
Returns 200 OK with a JSON body.
okbooleanRequired
Whether the action completed successfully.
Errors & retries
Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.
Use the complete schemas for validation or client generation.
Full request JSON schema
{"type":"object","properties":{"connection_id":{"type":"string","minLength":1,"maxLength":41,"description":"Use connection_id from the outbound connection catalogue. This does not identify your calling Brigg API key. [integrations.ListApiConnections](/developers/reference/integrations/ListApiConnections)."}},"required":["connection_id"],"additionalProperties":false,"examples":[{"connection_id":"e_example"}]}
Full response JSON schema
{"type":"object","properties":{"ok":{"type":"boolean","description":"Whether the action completed successfully."}},"required":["ok"],"additionalProperties":false,"examples":[{"ok":true}]}