Digital Footprint checks Eventbrite from an email address as part of every lookup, alongside 885+ other platforms, breach history and public web mentions - one request, one shape of answer. A hit means an account exists for that input; account contents are never collected.
Standard tier - checked on every full lookup
Eventbrite is checked from an email address. The response says whether that address has a Eventbrite account - registered: true or registered: false - with the moment that was established in checkedAt. A username on its own cannot reach Eventbrite, so username lookups do not include it.
Eventbrite is checked on every full lookup (?wait=true or streaming), alongside every other platform. It is not in the sub-second instant subset, which is reserved for the highest-value platforms for each input type.
If Eventbrite blocks the check, times out, or answers ambiguously, it is omitted from results[] entirely rather than returned as registered: false. Absence from the response means "unconfirmed", never "no account".
Shopping and marketplace accounts are checked by e-commerce and payment teams scoring orders. A buyer with real purchase history on established marketplaces is materially lower risk than an email that exists nowhere, which is why marketplace presence sits alongside breach history and email age in order and payout fraud scoring.
More on this: Order and payment fraud.
curl -X POST "https://api.digifootprint.dev/v2/lookup?wait=true" \
-H "Authorization: Bearer dfp_your_key" \
-H "Content-Type: application/json" \
-d '{"email": "someone@example.com"}'{
"platform": "eventbrite",
"registered": true,
"checkedAt": "2026-10-15T09:53:22.217Z",
"identity": "email"
}The full response shape - breaches, web mentions, matches versus socialMatches, and what method means - is in running a lookup.
Every one of these is checked in the same request as Eventbrite.
Free to start, no card. Then pay as you go, or pick a plan when your volume grows.