Skip to main content

Result envelope

GET /searches/{search_id}/results and GET /enrichments/{job_id}/results return the same business shape. Search results appear as discovery imports them; standalone-enrichment rows appear as their supplied inputs are resolved and committed.

Business identity and rank

For standalone enrichment, a supplied name and website take precedence and become title and website. Supplied Maps identifiers are retained, but Maps-only location, rank, reputation, and place-identity fields can remain null when exact Maps resolution was unnecessary. Maps-only rows are resolved first and can contain the usual listing fields. position and rank preserve the submitted array order.

Location and reputation

Website, phones, and socials

People and emails

Enrichment states

The result exposes separate status fields because different sources can finish independently:
  • enrichment_status
  • owner_enrichment_status
  • facebook_enrichment_status
  • bbb_enrichment_status
  • yelp_enrichment_status
  • brave_owner_status
  • anymail_enrichment_status
Possible values depend on the stage and include waiting, pending, processing, completed, failed, skipped, and not_requested.
Arrays are returned as arrays even when empty. Optional scalar values use null. Do not substitute guessed field names: parse owner_emails, decision_maker_emails, and emails separately.

Interpret email verification

Look up each address in email_verifications. A result of ok with quality good is presented by Mapsdata as safe; catch-all, unknown, and lower-quality responses require caution. invalid should not be used. If the address has no terminal payload and the overall status is still active, wait for verification to finish.