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.curl --location 'https://api.mailfloss.com/v1/integrations?per_page=&cursor=' \
--header 'Authorization: Bearer <token>'{
"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
}
}