Discoverly V1 Person API Documentation

After getting consistent requests, we are very excited to be finally be able to deliver Dicoverly data via our Person API. You can buy your API credits and access token here.

In general our Person API is pretty simple. It behaves like our chrome extension does in Gmail, LinkedIn, Facebook, Twitter, etc.  Below you can see example queries with social URLs and email address and what person data you can expect to return.   Everything should be pretty straight forward, but you can also find an FAQ below the example.

API Endpoint

Example API Queries:

Example Response:

“full_name”:”Bob Wiley”},







{“current_position”:”Sailor at Lake Winnipesaukee”},

{“email_hash”:”0119350b2d8f12e435a8a90126170505c7deecf945aff5455e6eb286″}, {“email_hash”:”70e0b00dbb4530c168ef73b8960eccc36712847a5f4c505e3cf64f”},

{“location”:”Glendale, New Hampshire”},






FAQ – Frequently Asked Questions

What are tokens and credits and how do I get them?
API acccess tokens are granted when you purchase API credits. You can purchase credits hear and you will recieve an email with you token within 24 hours. As you use the api you can see how many credits you have left with each response.

What if Discoverly as no data for a particular email address or social URL?
Somtimes we won’t know anything about particular email or URL and somtimes there will be typo is the query.  In this event, the API will have an largely empy response.  Every API call consume one credit, regardless of how much data is return on the person.

What are the email hash(s) in API response?
The API does not respond with people’s email addresses by it currently provides encrypted email hashes for every email address we have on record for a person that can be used in ad (re)targeting.

Why are some fields in the example API response with strike-through?
You can ignore these fields. They are leftover response from our internal API. We plan to clean them out eventually.