mocop
Browse · Docs · Guide · Analyze

mailfloss API

API by mailfloss · rest

mailfloss email verification API — version 1. Authentication Every request must include your API key as a Bearer token in the Authorization header: Authorization: Bearer YOUR_API_KEY This is the only accepted authentication scheme for v1. The legacy ?api_key= query parameter is not accepted on v1 endpoints. Conventions List endpoints return a { data, pagination } envelope. Errors return a stable machine-readable code (branch on it, not the message). Timestamps are ISO 8601 UTC.

Endpoint: https://api.mailfloss.com/

Verification: observed. Source: crawl.

Capabilities (33)

  • Read the authenticated account holder
  • Update the authenticated account holder
  • Account activity timeline
  • Submit a batch of emails for async verification
  • Cancel a batch verification job
  • Get batch job results (paginated)
  • Get batch job status
  • Verify an API key
  • Erase stored verification records (data privacy)
  • List all integrations (connected + disconnected)
  • Read one integration with all of its connections
  • Connect a new connection (with credentials)
  • Read one connection
  • Update a connection's settings
  • Disconnect a connection
  • List a connection's keyword rules
  • Add keyword rules
  • Delete a keyword rule
  • Re-sync a connection's audiences
  • Test a connection's credentials
  • List verification jobs
  • Get a verification job
  • Read the authenticated organization
  • Get verification usage analytics
  • List team members
About · Contact · Privacy