Skip to main content

POST /web_presence_requests is an independent product

The Web Presence API accepts the same kind of inputs as a Business Search but runs only the digital-footprint analysis. It operates independently of KYB: it doesn’t require a registration match, doesn’t influence KYB scores, and returns results regardless of whether the business appears in Secretary of State records. This makes it the right primary path for several common integration patterns, not just a fallback for failed Business Searches.

When standalone is the better default


Request fields

Required

Optional

Valid values for options

Order.Enhanced and Order.Pep are not supported on this endpoint. To get social profiles and reviews via /web_presence_requests, request each sub-product individually. If no options are submitted, Order.WebsiteAnalysis and Order.NaicsPrediction are requested by default.

Where the data lives in the response

A key difference from /searches: on this endpoint, website_analysis and industry_prediction are returned inline in the response. You do not need to call a separate GET endpoint to retrieve them.
No unified address or officer list. Unlike /searches with Order.Enhanced, this endpoint does not merge discovered addresses and officers into a single business object. Discovered addresses and officers are nested within each sub-product result (e.g., inside website_analysis or individual found_social_profiles entries).

Sample request


Sample response


Sole proprietors

Web presence is the cornerstone of sole proprietor verification. Sole props typically lack SoS registration data, which means a Business Search alone cannot confirm their identity. Online presence (an active website, social media profiles, review history, and consistent contact information) fills that gap. For the complete sole proprietor workflow covering TIN verification, web presence, and individual identity checks, see Sole Proprietorship Verification.

Webhooks

When a web presence request completes, Baselayer fires:
  • WebPresenceRequest.completed: signals the full request is done and all requested sub-products are available in the response.