RealPhoneValidation API Best Practices
We built our APIs to be easy to implement and fast to use. You can view complete documentation for each of our APIs here, but we also wanted to give you this best practices checklist. Following these tried-and-true techniques will ensure optimal API performance.
Never share or publish your API token insecurely.
Don’t email API tokens or publish them publicly. If you feel your token has been potentially compromised, you can regenerate a new one on the validation page of my.realvalidation.com. My.RealValidation.com
Use a different API token for optimal reporting for each domain or user.
Creating a dedicated account for each API integration will assign each account a unique token. This will make reporting simple and uncomplicated since you’ll easily see the number of validations per domain or user. Please get in touch with support if you are interested in setting up multiple accounts. Support
Whitelist @realvalidation.com in your email client.
This will ensure you receive important information, such as scheduled system maintenance or API updates. How to whitelist email
Create a Short Term Data Cache
If you use the RealPhoneValidation APIs to collect leads from web forms or a ping-post system to buy leads, we recommend caching anywhere from 2 to 7 days’ worth of submitted numbers. This will prevent you from being charged for accidental resubmissions. Github
Monitor HTTP codes
You should accept the lead if there is an HTTP code NOT 200.
A couple of things can cause a non-HTTP 200 code:
1) Our service is down – we run on AWS, which has an uptime of 99.95%, so although very unlikely it could happen, we would not want you to lose good leads because of us.
2) You are temporarily throttled because you exceed the recommended 10/sec API calls. A temporary block will return an HTTP 403.