Disconnect a connection

DELETE

/v1/integrations/{type}/connections/{id}

Disconnects (soft-disables) a connection. Its data and stored credentials are retained — this stops all cleansing/processing for the connection and removes it from subsequent reads (it disappears from GET /v1/integrations and GET .../connections/{id}). Returns 200 with a small confirmation { id, type, status: "disconnected", disconnected_at }; no credential fields are returned. A connection id that does not exist, belongs to another org, or is already disconnected → 404 not_found (so a repeated DELETE is a safe 404). A connection with Instafloss (Superfloss) enabled is refused with 409 conflict — its live real-time webhooks must not be left pointed at a disabled connection, so disable Instafloss first, then disconnect (mirrors the dashboard). Reconnecting a connection is a future additive endpoint.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢200

application/json

Disconnect confirmation

Bodyapplication/json

🟠401

🟠403

🟠404

🟠409

🟠429

🔴500

🔴503

Request Example

Shell

JavaScript

Java

Swift

curl --location --request DELETE 'https://api.mailfloss.com/v1/integrations//connections/' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Success

{
    "id": "conn_5d4c3b2a1e0f9z",
    "type": "mailchimp",
    "status": "disconnected",
    "disconnected_at": "2026-06-20T14:30:00Z"
}

Modified at 2026-10-20 13:54:45

Update a connection's settings

Re-sync a connection's audiences