Each API result has a qualification field. For emails, it is valid or invalid. For phone numbers, it is found or not_found. While the search is running, it is ongoing. Results stay available for 3 months: get them by webhook, or with the GET endpoint and the search id.
What each result means
Email Finder
valid: Enrow found the email and verified it. You can use it.invalid: Enrow didn't find a valid email for this person.
Email Verifier
valid: the address is valid. You can send to it.invalid: the address can't receive email. Don't send to it.
Phone Finder
found: Enrow found a phone number.not_found: Enrow didn't find a number.
All features
ongoing: the search isn't finished yet. Ask again a bit later.
The answer is always yes or no. There is no "catch-all", "risky" or "unknown" status: Enrow also verifies emails on catch-all domains. Learn more in Valid or invalid: understanding your results (catch-all included).
Get a result with its id
When you start a search, the POST response gives you an id. To get the result, call the GET endpoint of the same feature with this id, for example GET /email/find/single?id=….
Single search: if the
qualificationisongoing, wait a few seconds and ask again.Bulk search: the response has a
statusfor the whole batch:ongoing(still running),completed(all rows are done) orfailed. While it runs, you can follow the progress (rows finished out of rows requested). Once it'scompleted, each row ofresultscomes with itsindex(its position in the list you sent) and yourcustomvalue.
GET requests are free and have no rate limit. A webhook is still simpler: Enrow sends the result as soon as it's ready. See Receive API results with webhooks.
"Unknown id" errors
The API never returns a 404 error. If the id is unknown or has expired, a single GET endpoint returns a 500 error, and a bulk GET endpoint returns a 400 error. Check that you used the id from the POST response, with the GET endpoint of the same feature, and that the search is less than 3 months old.
How long results are kept
Enrow deletes searches and their results 3 months after they are created. This includes searches made with the API. After that, the GET endpoint returns an error. Save the results you need in your own system.
API searches don't appear in the search history of the Email Finder and Phone Finder pages. You see them only as figures in Analytics: set the Origin filter to API.
There is no endpoint that lists your past searches. Keep the id of every search, and send custom data (such as your own record ID) to link each result to the right contact.
Lost a result?
You have the
idand the search is less than 3 months old: call the GET endpoint again. This is free.You missed a webhook: same thing, use the GET endpoint with the
id.You don't have the
id: Enrow can't find the result for you. Run the search again. It is a new live search, so it costs credits again if Enrow finds something.