Snapchat Number, Email & Username Lookup APIs

Verify whether a single phone number is registered on Snapchat and, on a hit, enrich it with the account's public identity: username, userId, and displayName. Pass the full international number (digits, optional leading +); the API normalizes it to E.164. registered is three-state: true = registered, false = not registered, null = undetermined (transient — see message and retry after a short backoff). This is the recommended phone check: it is built for high-concurrency screening and resolves identity in the same call, so you do not need a second request to learn who the number belongs to.

Validate many phone numbers in a single request. Pass up to 50 comma-separated international numbers; one call classifies the whole batch and returns a per-number result with registered status plus username, userId, and displayName on hits. This is the most efficient path for list screening and bulk validation — 50 numbers cost one request instead of 50. Each row carries its own three-state registered flag, so a transient failure on one number does not fail the whole batch.

Full lookup for a phone number, email, or username: registration status plus the public identity the matching surface can see. Pass either number (phone) or target (email or username); if both are set, number wins, and a phone-shaped target is routed to the phone path. Phone hits return username, userId, and displayName; a username hit returns displayName and a snapcode image URL; an email hit returns a masked recovery address. The response always carries a machine status (found / not_found / invalid / error) and a human-readable message. Note: an email lookup uses an account-recovery probe, so a positive email hit may send a real recovery email to the owner — use it deliberately, not for bulk spraying.

Resolve a Snapchat username to its public profile: username, displayName, and a snapcode image URL when the account exists. Handles are matched against Snapchat's public profile pages, so this needs no phone number and returns a clear registered=true/false plus a machine status (found / not_found / invalid). Use it to confirm a handle is taken, enrich a known username with its display name, or fetch a scannable snapcode. Bio and Bitmoji avatar are not exposed on this public surface.

The lightest existence probe: pass a target and get back whether it is registered on Snapchat. A username-shaped target (e.g. teng_leo) is resolved against the public profile surface; an email address is checked via an account-recovery probe. exists is three-state: true = registered, false = not registered, null = undetermined (transient — see message, cool down, and retry). Ideal for real-time form validation and availability checks. Note: a positive email result may send a real recovery email to the address owner, so do not use this to spray large email lists.