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

Re-sync a connection's audiences

POST
/v1/integrations/{type}/connections/{id}/sync
Re-runs the live list/audience fetch for a connection using its stored credentials and refreshes the connection's audiences — use it when lists were renamed/added upstream, or when the connect-time fetch came back empty. The stored credentials are validated against the ESP as part of the fetch: a rejected key → 400 invalid_credentials and nothing is changed; an unreachable ESP → 503. On success returns 200 with the refreshed connection (same shape as GET .../connections/{id}). A connection id that does not exist or belongs to another org → 404; a connection of a type that can't be managed via the API → 422 unsupported_integration.

Request

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

Responses

🟢200
application/json
Refreshed connection
Bodyapplication/json

🟠400
🟠401
🟠403
🟠404
🟠422
🟠429
🔴500
🔴503
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://api.mailfloss.com/v1/integrations//connections//sync' \
--header 'Authorization: Bearer <token>'
Response Response Example
200 - Success
{
    "id": "conn_5d4c3b2a1e0f9z",
    "name": "Main Marketing List",
    "status": "active",
    "created_at": "2026-02-10T14:20:00Z",
    "last_synced_at": null,
    "settings": {
        "aggressiveness": "normal",
        "manual_mode": false,
        "autofloss": true,
        "decay_protection": true,
        "instafloss": false,
        "action": "unsubscribe",
        "checks": {
            "disposable": true,
            "nonexistent": true,
            "deactivated": true,
            "inbox_full": true,
            "bounced": true,
            "banned_words": true,
            "role_based": true,
            "complainers": true,
            "spam": true,
            "failed_exchange": true,
            "unverified": true,
            "accept_all": false
        },
        "blacklist_count": 5,
        "whitelist_count": 2
    }
}
Modified at 2026-10-20 13:54:45
Previous
Disconnect a connection
Next
Test a connection's credentials
Built with