Validate Pixel
Checks whether the Whop pixel is installed for an account. Recent pixel events count as proof on their own, so an account that has sent data lately comes back installed without a url. Pass a url and events from that page settle it; if it hasn’t sent any lately the page is fetched and read for the pixel and the conversion events wired on it. installed is only true when the pixel was actually seen — in the account’s events or in the page.
Authorizations
A company API key, company scoped JWT, app API key, or user OAuth token. You must prepend your key/token with the word 'Bearer', which will look like Bearer ***************************
Headers
A unique key that makes this request safe to retry. See Idempotent requests.
255"d9105228-4a08-46b1-8b91-42fed586d383"
Pins the request to a dated API version.
"2026-07-27"
Body
Response
pixel validated
False when the event lookup failed, meaning installed_events and last_seen_days are incomplete.
True when the pixel was found — either the account has sent events recently, or the pixel is present in the page at url. False otherwise, including when the page couldn't be loaded.
Conversion event names detected on the page or fired recently, e.g. lead, purchase. Excludes the events the pixel fires automatically on every page.
Event name to whole days since that event last fired, e.g. { "lead": 3 }. Carries events that fired too long ago to count as installed, so you can prompt to re-check rather than report them missing.
Days since the pixel last sent an event, within a 30-day window. null when it hasn't sent one in that window — which includes a pixel installed moments ago.
True when the URL is a Whop-hosted store page for this account, which Whop tracks natively — no pixel snippet is required there.
Whether the page could be loaded. null when the request included no URL, and true when events settled the answer without a fetch.
The URL that was checked, after normalization. null when the request didn't include one.

