Using the Account Finder API for email lookups
Run account discovery programmatically. The endpoint, the JSON shape, rate limits, and how to wire it into your own tools via RapidAPI.
Published 2026-05-14 · 6 min read · Account Finder Blog
The web form is built for one-off checks. When you need to enrich a list of leads, score sign-ups for fraud, or fold account discovery into an existing pipeline, use the API instead. It returns the same matches and profile enrichment as the UI, as clean JSON you can parse.
Account discovery is a single GET request: GET /api/search?email={email}. It responds with JSON describing the matched services and whatever profile fields each one exposes. An interactive playground is published on RapidAPI so you can try requests and copy ready-made client code before writing any of your own.
- Open the Account Finder API on RapidAPI and subscribe to a plan — the free tier is enough to test with.
- Copy your RapidAPI key and the generated snippet for your language from the playground.
- Send a GET request to /api/search with the email as a query parameter.
- Parse the JSON: iterate the matched services, read the per-service enrichment, and map it into whatever your application needs.
- Handle HTTP 429 by backing off — it signals you've hit the rate limit for your tier.
Each matched service comes back with the fields that service exposes: username, display name, avatar, bio, linked emails and phones, user IDs, account-creation date, last-login date, and email-verified status where available. Fields that a service doesn't publish are simply absent, so write your parser defensively and treat every enrichment field as optional.
Free and paid tiers each have a request ceiling; when you exceed it the API returns HTTP 429. That's your cue to throttle, queue, or upgrade — not to retry in a tight loop. For batch enrichment, space requests out and cache results you've already fetched, since searches aren't stored server-side for you.
Anything you can do in the search box, you can do in a loop. The API is just the form without the form — same data, no clicks.
Account Finder groups every match by service category — social, professional, developer, gaming, shopping, messaging, and more — and attaches whatever profile details each service exposes: full name, username, avatars, bio, linked emails and phones, user IDs, account-creation date, and last-login date. A match means an account exists for that email on that service. On its own it does not tell you how actively that account is used.
- Categories show the shape of an online footprint — the kinds of services an email is registered on.
- Per-service fields (usernames, display names, bios, creation and last-login dates) help you confirm the match is the person you actually care about.
- Treat an old, dormant account differently from one with a recent last-login. Existence is a lead; recent activity is a signal.
Account Finder indexes publicly observable account metadata — the same kind of information you could assemble by hand with enough patience and the right searches. It does not return passwords, private messages, or anything hidden behind a login. Use it for authorized work: OSINT, fraud investigation, due diligence, or auditing your own footprint and accounts you have permission to investigate. Do not use it for harassment, doxxing, stalking, or unauthorized surveillance. If you need a deeper investigation with extended source coverage and breach intelligence, Checkmate (checkmate.bio) is IASolutions' companion platform for full deep search.