website logo
⌘K
Email Verification API
API Overview
Authentication
Rate Limits
Response Headers
Response Codes
Reference
Code Examples
Data Privacy API
Data Privacy API Overview
Reference
Code Examples
Webhooks
Webhooks Overview
Retries and Errors
Managing Webhooks
Verifying Webhooks
Event Triggers
JavaScript Widget
JavaScript Widget Overview
Installing the Widget
Widget Configuration Options
Docs powered by
Archbee
Email Verification API

Response Codes

1min

The API makes use of standard HTTP response codes to indicate the success or failure of a request. The 2xx series of response codes indicate success, 4xx indicates an error from the client-side, and a 5xx error indicates a server-side error.

Please check response codes and handle accordingly. Contact us if you run into repeated issues, especially in the 5XX error range.

Here are the HTTP response codes the mailfloss API utilizes:

  • 200 - Success
  • 400 - Email address or Id not supplied
  • 401 - Invalid API key
  • 402 - Insufficient credits
  • 403 - No API key provided
  • 404 - Job not found or job not finished
  • 405 - Method not allowed
  • 413 - Payload too large. Too many email addresses
  • 414 - Request Entity Too Large
  • 415 - Invalid Content Type. Must be application/json
  • 429 - Rate limit exceeded
  • 500 - Timeout
  • 502 - Bad Gateway
  • 503 - Failed to create job
  • 504 - Gateway Time-out



Updated 11 Apr 2023
Did this page help you?
PREVIOUS
Response Headers
NEXT
Reference
Docs powered by
Archbee
Docs powered by
Archbee