Snapchat Number Lookup API: Phone, Batch, Email, or Username

Published August 24, 2026 · UpdatedOctober 16, 2026

Five Snapchat lookup operations share one project and one authorized key. They do not share a job. Match the identifier you actually hold — a single phone, a list of phones, an email, a username, or a public handle — to one row before you write a loop.

You holdCallWhy not the others
One phonecheck-phoneIdentity (username, userId, displayName) already comes back on a hit
Many phonescheck-phones-batchUp to 50 comma-separated numbers; looping check-phone wastes round-trips
Email or username, existence onlycheck-email-usernameLight exists flag; email uses a recovery probe
Mixed keys, need a machine statususer-infoRoutes number or target; phone wins if both are set
A known handle, public cardpublic-profileDisplay name and snapcode — not a phone registration check

Sign in and copy an active key from the dashboard. Curl examples use YOUR_API_KEY; Python reads OPENDATA_API_KEY. The key travels in the query string, so keep URLs out of screenshots, tickets and browser apps. Opening this page or copying a snippet does not send a lookup.

Pick the probe before you write a loop

The five paths live under https://api.opendata-api.com/api/project/snapchat/<operation>. HTTP 200 is not the answer. Every reply also carries a gateway code / message / data envelope, sometimes nested twice; unwrap until you are looking at the operation payload, and treat a non-200 code as a business failure even when the transport succeeded.

Registration flags are three-state. registered (phones) and exists (email or username) are true, false, or null. null is undetermined — a transient miss, explained in message — never a "not on Snapchat". Retry it after a short backoff. user-info and public-profile instead expose a machine status (found, not_found, invalid, and error on user-info); branch on that field, not on the prose in message.

A small dispatcher is the whole integration for most products. It does not call every operation.

import os
import time
import requests

API_KEY = os.environ["OPENDATA_API_KEY"]
BASE = "https://api.opendata-api.com/api/project/snapchat"


def get(operation, **params):
    params["key"] = API_KEY
    resp = requests.get(f"{BASE}/{operation}", params=params, timeout=30)
    resp.raise_for_status()
    body = resp.json()
    # Unwrap {"code", "data"} layers; HTTP 200 is not business success
    while isinstance(body, dict) and "code" in body and isinstance(body.get("data"), (dict, list)):
        body = body["data"]
    return body


def probe(phone=None, email=None, username=None):
    if phone:
        return get("check-phone", number=phone)
    if email:
        return get("check-email-username", target=email)
    if username:
        return get("public-profile", username=username)
    raise ValueError("need phone, email, or username")

Pass one identifier. Do not "enrich" a phone hit by calling user-info next — check-phone already returned the public identity when registered is true.

One phone, then fifty

check-phone takes number in international digits, optional leading +. The API normalizes it. On a hit you get username, userId and displayName in the same payload.

curl "https://api.opendata-api.com/api/project/snapchat/check-phone?key=YOUR_API_KEY&number=8613800138000"

When registered is null, wait and retry; do not store it as false.

def check_phone(number, retries=2):
    data = None
    for attempt in range(retries + 1):
        data = get("check-phone", number=number)
        if data.get("registered") is not None:
            return data
        time.sleep(2 * (attempt + 1))  # undetermined: back off, then retry
    return data

A list is a different operation, not a for loop. check-phones-batch classifies up to 50 comma-separated numbers per request and returns a per-row three-state registered flag, so one transient miss does not fail the batch. Hits still include username, userId and displayName. Billing is per number returned — read pricing before you pour a warehouse through it.

import json


def chunks(items, size=50):
    for i in range(0, len(items), size):
        yield items[i:i + size]


numbers = ["8613800138000", "8613900139000"]  # your normalized list
with open("snapchat_batches.jsonl", "a") as out:
    for batch in chunks(numbers):
        data = get("check-phones-batch", numbers=",".join(batch))
        out.write(json.dumps({"requested": batch, "result": data}) + "\n")

Keep the raw chunk. Afterward, collect rows whose registered is null and send them in a later batch. Do not re-issue the successful rows.

Email or username is a different door

Phones never go to check-email-username. That call takes target: a username-shaped value such as teng_leo is resolved against the public profile surface; an email is checked through an account-recovery probe. The answer is exists, again three-state.

curl "https://api.opendata-api.com/api/project/snapchat/check-email-username?key=YOUR_API_KEY&target=teng_leo"

Use the email form as a single, intentional check — a sign-up field, a support ticket, a CRM record you already have a lawful basis to touch. A positive email result may send a real recovery email to the address owner. That is not a list-cleaning primitive. There is no 50-email batch, and you should not invent one by looping.

When the identifier mix is messy (phone on some rows, email or username on others) and you want a machine status rather than exists, use user-info. Pass number or target; if both are set, number wins, and a phone-shaped target is routed to the phone path. What comes back depends on the surface: a phone hit returns username, userId and displayName; a username hit returns displayName and a snapcode image URL; an email hit returns a masked recovery address — and the same recovery-mail caveat applies. Branch on status.

info = get("user-info", number="8613800138000")
if info.get("status") == "found":
    print("identity", info.get("username"), info.get("displayName"))
elif info.get("status") in ("not_found", "invalid"):
    print("no account or bad input")
else:
    print("retry later", info.get("message"))

user-info is the mixed-key door. It is not a mandatory second hop after check-phone.

A public profile is not a registration check

public-profile resolves a username to username, displayName and a snapcode image URL when the handle exists. It needs no phone number. It returns registered plus status of found, not_found or invalid. Bio and Bitmoji are not on this surface.

curl "https://api.opendata-api.com/api/project/snapchat/public-profile?key=YOUR_API_KEY&username=teng_leo"

That is how you confirm a claimed handle, attach a display name, or fetch a scannable snapcode. It is not how you ask whether 8613800138000 is on Snapchat. Feeding a phone into username does not become a phone check. Feeding a username into check-phone does not become a profile card.

If the job is Stories, Spotlight or Lens rather than registration, stop here and use Snapchat profiles, Stories and Spotlight via API — a different project, not a sixth operation on this one.

What not to build from these five calls

Do not build a per-contact waterfall that hits all five operations "to be sure". One identifier, one probe. A phone list is check-phones-batch; a handle is public-profile; an email is a cautious check-email-username or user-info, never a spray.

Do not treat null or error as false, and do not treat HTTP 200 as true. Store undetermined rows for retry. Do not parse message as the contract.

Do not expect a send API, a friend graph, a Bitmoji, a bio, or a live location. These calls classify identifiers and, on some hits, return the public identity that surface already exposes.

Do not use Snapchat registration as the only KYC or anti-fraud signal. It is a channel flag.

Do not collapse Signal, Viber, WhatsApp and Snapchat into this project. Each channel has its own operations; the lead verification workflow is where you combine them. Large WhatsApp lists follow a different chunk-and-resume pattern in bulk verification for WhatsApp numbers. Channel-specific lookups: Signal, Viber, WhatsApp.

Product page: Snapchat Lookup.