1. Integrations
mailfloss API
  • Verification
    • Verify a single email address
      GET
  • Batch
    • Submit a batch of emails for async verification
      POST
    • Get batch job status
      GET
    • Get batch job results (paginated)
      GET
    • Cancel a batch verification job
      POST
    • List verification jobs
      GET
    • Get a verification job
      GET
  • Account
    • Account activity timeline
      GET
    • Verify an API key
      GET
    • Read the authenticated account holder
      GET
    • Update the authenticated account holder
      PATCH
    • Read the authenticated organization
      GET
  • Team
    • List team members
      GET
    • Get the account owner as a team member
      GET
    • Get a team member
      GET
  • Reports
    • Get verification usage analytics
  • Webhooks
    • List webhook subscriptions
    • Create a webhook subscription
    • Get a webhook subscription
    • Update a webhook subscription
    • Delete a webhook subscription
  • Integrations
    • List all integrations (connected + disconnected)
      GET
    • Read one integration with all of its connections
      GET
    • Connect a new connection (with credentials)
      POST
    • Read one connection
      GET
    • Update a connection's settings
      PATCH
    • Disconnect a connection
      DELETE
    • Re-sync a connection's audiences
      POST
    • Test a connection's credentials
      POST
    • List a connection's keyword rules
      GET
    • Add keyword rules
      POST
    • Delete a keyword rule
      DELETE
  • Privacy
    • Erase stored verification records (data privacy)
  • Schemas
    • ErrorEnvelope
  1. Integrations

List all integrations (connected + disconnected)

GET
/v1/integrations
Returns the full set of 41 ESP integrations, with connected: true for those the org has actively connected. Each entry carries connection_count and a deterministic primary summary because (org, type) is 1:N — customers can connect multiple accounts of the same ESP. primary is the connection with the lowest createdAt (or null when connection_count: 0); use it for chatbot shortcuts like "is X connected?" without a follow-up DETAIL request. Always paginated with a cursor envelope, even though the underlying set is bounded — so SDKs and chatbots use one pagination code path across every collection endpoint. Default per_page = 10, max 100. Cursor is opaque (base64url JSON); clients MUST NOT parse it. Sort order: connected ESPs first (alphabetical by type), then disconnected.

Request

Authorization
Bearer Token
Provide your bearer token in the
Authorization
header when making requests to protected resources.
Example:
Authorization: Bearer ********************
or
Query Params

Responses

🟢200
application/json
Paginated integration summaries
Bodyapplication/json

🟠400
🟠401
🟠403
🟠429
🔴500
🔴503
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api.mailfloss.com/v1/integrations?per_page=&cursor=' \
--header 'Authorization: Bearer <token>'
Response Response Example
200 - Success
{
    "data": [
        {
            "type": "mailchimp",
            "connected": true,
            "connection_count": 1,
            "primary": {
                "id": "conn_5d4c3b2a1e0f9z",
                "name": "Main Marketing List"
            },
            "disconnected_count": 0
        },
        {
            "type": "klaviyo",
            "connected": false,
            "connection_count": 0,
            "primary": null,
            "disconnected_count": 0
        }
    ],
    "pagination": {
        "next_cursor": null,
        "has_more": false
    }
}
Modified at 2026-10-20 13:54:45
Previous
Delete a webhook subscription
Next
Read one integration with all of its connections
Built with