Skip to main content
This reference covers the structural elements shared across all Online Presence products — match values, match sources, how data is organized differently across integration paths, and how to distinguish the various website-related fields in a response. For field-level documentation of individual sub-products, see the product guides:

​
Match values

These fields appear at the top level of both POST /searches and POST /web_presence_requests responses. They summarize how well the submitted data aligns with what Baselayer independently discovered online.

​
Match sources

Every *_match field has a paired *_match_sources array that lists where Baselayer found the matching data. Use these to understand the strength and provenance of each match — a phone number confirmed across FOUND_WEBSITE, REVIEW, and DIRECTORY is a much stronger signal than one sourced from a single location. Fields with a paired *_sources array: business_address_match_sources, business_website_match_sources, email_match_sources, phone_number_match_sources, people_match_sources.

​
Response shape by integration path

The underlying field structures are identical across both paths — a website_analysis object looks the same regardless of how you requested it. What changes is where data sits and how you access it.

​
The website fields, demystified

Several fields relate to websites and it is easy to confuse them. Here is what each one is: When do you get two website analyses? When a website is submitted and Baselayer discovers a different domain, both are analyzed. On /web_presence_requests this produces both website_analysis and input_website_analysis inline. On /searches it produces two WebsiteAnalysisRequest entries in orderables[] — indistinguishable in the array; call GET on each to identify which domain was analyzed via website_analysis.url.

​
Request states

COMPLETED, FAILED, and CANCELLED are terminal — once a request reaches one of them, its state never changes.