RealPhoneValidation API Best Practices

We built our API’s to be easy to implement and fast to use. You can view complete documentation for each for our API’s 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

  • For optimal reporting use a different API token for each domain or user.

    By creating a dedicated account for each API integration each account will be assigned a unique token. This will make reporting simple and uncomplicated, since you’ll easily be able to see the number of validations per domain or user. Please contact 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 are using the RealPhoneValidation API’s to collect leads from web forms or using 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 resubmits. Github

  • Use SSL for all requests.

Get the data behind the number with Real Phone Validation