Our API is designed to accept both one-off verification requests as well as bulk verification requests. To ensure the most accurate results and efficiency of the verification, it's important to know when each option should be used and the respective limits of both.

Single Verification

  • Should be used in response to an action, like a form submission or button click
  • Do NOT use single verification for verifying emails in an existing list or database one-by-one. Your account may be locked and API access disabled if used for this purpose. Use the bulk verification for this purpose.

Bulk Verification

  • We allow each account to run 10 concurrent jobs and a maximum of 50 runs per day
  • Should be used to verify databases or lists of several emails
  • If you have fewer than 1 million emails to verify, you should submit all the data you have for verification in a single job rather than multiple jobs. It's more efficient to submit a single 50k list rather than five 10k lists.
  • If you have millions of emails to verify, you should split the data into 1 million email chunks and create a job for each chunk. A database of 25 million emails should be submitted as 25 separate 1 million item chunks.
  • If you're collecting data from external sources like a CRM or ERP, you should buffer the data locally and submit it as a single job rather than submitting each chunk of data separately.
  • Do NOT create more than 10 jobs for every 100k items per hour. Sending too many small jobs in a short amount of time can result in your account being locked and API access disabled.
  • If sending data to us using the supplied_data method there is a maximum payload of 25MB enforced. If you surpass this limit you'll receive a 413 error code.

Exceptions can be made for some use cases, please contact us with your scenario if you'd like this exception to be made.