Email Verification API — Check Gmail, Outlook & Disposable Emails
Website ychecker.com is built on Sonjj.com's API system. With Sonjj's powerful API system, this website operates very stably and can withstand high traffic without having to spend extra money on servers.
Most email verification tools answer one question: does this mailbox exist? That's a start, but it misses everything that actually breaks production workflows — a Gmail account locked behind a phone-number gate, a Microsoft address that's been deactivated, a sign-up form getting hammered with throwaway domains.
The YChecker API covers all of it. One authentication header. No SDK to install. Works with any HTTP client.
What the API Checks
Email existence and type — Whether an address is real, active, and which provider it belongs to: Gmail, Outlook, or other.
Phone verification status — For Gmail and Microsoft accounts, whether the account requires phone number verification to log in. Critical for any workflow that automates account access or tests sign-up flows.
Account status — Whether an account is live, disabled by Google or Microsoft, or simply doesn't exist.
Disposable email detection — A risk score per domain, not a binary flag. You set the threshold that fits your product.
Gmail avatar — Profile image URL for Gmail accounts where a public avatar exists, useful for enriching user profiles.
Who Uses It
Developers building sign-up flows — Block throwaway email registrations at the point of entry without adding friction for legitimate users.
Email marketers — Clean a list before a campaign send. Sending to disabled or non-existent addresses tanks deliverability; catching them beforehand doesn't.
QA and automation engineers — Verify that test accounts are in the expected state before a workflow runs. A Verify status on a Gmail account means the flow will hit a phone gate — better to know before the test fails silently.
Growth and ops teams — Enrich CRM data by validating contact email quality without manual effort.
How Authentication Works
Every request requires a single header:
X-Api-Key: your_api_key_here
Get your key from my.sonjj.com. No OAuth, no token refresh, no SDK. If your tool can make an HTTP GET request, it can call this API — cURL, Python, JavaScript, n8n, Make, Zapier, or anything else.
Credits are charged only on a successful response. Failed requests, validation errors, and timeouts cost nothing.
Common Integration Patterns
Pre-filter disposable domains first — The domain-level disposable check is the cheapest call in the API. Run it before anything else to eliminate obvious throwaway addresses without spending on a full verification.
Use provider-specific endpoints when the provider is known — Checking a Gmail address? The Gmail-specific endpoint returns richer data at a fraction of the cost of the general check. Same logic applies to Microsoft addresses.
Chain calls only when needed — Start with the cheapest check that answers your question. Escalate to a fuller check only when the result is ambiguous or you need more fields.
Frequently Asked Questions
Does a "Not Exist" result cost credits?
Yes — the API successfully determined the address doesn't exist, which is a valid result. What's not charged: 4xx validation errors, 5xx server errors, and timeouts.
Can I run this in a bulk workflow?
The API is request-based. For bulk processing, loop over your list inside your automation tool or script. The domain-level disposable check is particularly efficient at scale due to edge caching on frequently-queried domains.
Do credits expire?
No. Credits never expire across any Sonjj product. Details at sonjj.com/pricing.
What Microsoft domains are supported?
Outlook, Hotmail, Live, and MSN.
Is this the same credit balance as SmailPro and other Sonjj products?
Yes. One shared wallet covers the full Sonjj API ecosystem.