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 a connection's keyword rules

GET
/v1/integrations/{type}/connections/{id}/keywords/{list}
Returns the per-connection keyword rules for the chosen {list} (blacklist = always-remove, whitelist = never-remove). The universal settings object on GET /v1/integrations/{type} only reports the COUNTS (blacklist_count/whitelist_count); this endpoint returns the rules themselves. Each rule carries a stable id, the keyword, its match strategy (exact/contains), and the applies_to segment toggles (localpart/domain/email). Always paginated with the universal cursor envelope (default per_page = 50, max 100); the cursor is opaque — clients MUST NOT parse it. Unknown type or list, or a connection id that does not exist or belongs to another org, → 404 not_found.

Request

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

Query Params

Responses

🟢200
application/json
Paginated keyword rules
Bodyapplication/json

🟠400
🟠401
🟠403
🟠404
🟠429
🔴500
🔴503
Request Request Example
Shell
JavaScript
Java
Swift
curl --location 'https://api.mailfloss.com/v1/integrations//connections//keywords/?per_page=&cursor=' \
--header 'Authorization: Bearer <token>'
Response Response Example
200 - Success
{
    "data": [
        {
            "id": "kw_7f8e9d0c1b2a3f4e",
            "keyword": "noreply",
            "match": "exact",
            "applies_to": {
                "localpart": true,
                "domain": false,
                "email": false
            }
        },
        {
            "id": "kw_6e7d8c9b0a1f2e3d",
            "keyword": "mailinator",
            "match": "contains",
            "applies_to": {
                "localpart": false,
                "domain": true,
                "email": false
            }
        }
    ],
    "pagination": {
        "next_cursor": null,
        "has_more": false
    }
}
Modified at 2026-10-20 13:54:45
Previous
Test a connection's credentials
Next
Add keyword rules
Built with