The BriteVerify Bulk Verification API is a simple JSON-based REST Web Service built for performing email address verifications at speed and scale. It's ideal for verifying databases or lists.
Below are some recommended best practices for you and your development team to consider when implementing:
- Check out the documentation
It's worth looking through our documentation before you start. There you can find examples of method calls and responses to guide implementation.
- Keep your API key(s) safe
You are responsible for verifications processed through your API key(s), so you should them safe. Don't hardcode them into your front-end code where they can be scrapped by a bad actor. Store them in your back-end code and make a variable that can be made available where you need it.
- Upload one list at a time
Every BriteVerify account has a set processing capacity. Loading up your account with too many lists at one time will impact your processing performance. It's best to wait for one to finish before uploading the next one.
- Upload fewer lists
Organize your lists so that you have a few large lists, rather than many smaller lists. If you're collecting data from external sources like a CRM or MAP for verification, you should buffer the data locally and submit it as a single job rather than submitting each chunk of data separately. The Bulk Verification API supports paging (up to 1,000 pages), so take advantage of it.
- Don't exceed 1 million email addresses per list
Lists this large fall outside the parameters of what this API is designed for, and are considered abuse. Violating this policy can result in having your account disabled. If you have a list that exceeds 1 million email addresses, please take advantage of the paging function. To learn more, refer to the documentation.
- Read through the documentation for the API that you want to use.
- Review the best practice guidelines:
- Create a BriteVerify account.
- Create an API key in the API Keys tab, and make sure that it is active.
- Get verifying!
We're here for you
If you or your developers have any specific questions or problems, please let us know and we'll be happy to help.