ArticlesNovember 18, 20254 min read

Disposable Email Detection API: Temp Mail Checker | AntiTemp

Detect disposable and temp mail addresses with POST /api/v1/email/check. Get a risk score and signals in one request, then try the free API today.

AntiTempMail Team
AntiTempMail Team
Updated November 18, 2025

AntiTemp's disposable email detection API checks one address at a time with POST /api/v1/email/check. Send an email address with your API key and the response returns a risk score, risk level, detection signals, explanation, and recommendation you can use in a signup or lead-quality workflow.

This guide shows the verified production endpoint and a practical integration path. It focuses on the API contract that is live today, without requiring a downloadable blocklist or a platform-specific SDK.

Quick start: call the disposable email detection API

Create an API key from your AntiTemp dashboard, keep it on your server, and make this request:

curl -X POST https://www.antitempmail.com/api/v1/email/check \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"user@example.com"}'

The single-email endpoint consumes one credit per call. A successful response contains the analyzed address in data plus fields such as:

  • risk_score: an integer from 0 to 100.
  • risk_level: safe, suspicious, danger, or unknown.
  • signals: weighted findings with evidence from the detectors that ran.
  • explanation and recommendation: readable context for your decision.
  • request, rate-limit, credit, and model metadata for operations and debugging.

Treat the response as an input to your policy rather than a universal yes/no rule. A low-risk signup might proceed automatically, a suspicious result might require another verification step, and a dangerous result might be rejected or queued for review.

What a temp mail detector checks

A temp mail detector evaluates whether an email address is associated with a short-lived or disposable inbox. Static domain lists are useful, but a production check also needs to handle domains that change, malformed addresses, mail-routing problems, and known exceptions.

AntiTemp runs multiple signals and combines their evidence into one result. The response is designed to be inspectable: your application receives the score and the underlying signals, so you can log the reason for a decision and tune your own thresholds.

Common integration points include:

  1. Account registration, before creating the user record.
  2. Free-trial or promotion enrollment, before granting benefits.
  3. Lead capture, before adding an address to sales or marketing automation.
  4. Risk review, where suspicious results need a second verification step.

Keep the API key in server-side code. If you need to check an address from a browser form, send it to your own backend first and let that backend call AntiTemp.

Temp mail checker response workflow

Start with a conservative policy and observe real traffic before tightening it:

  1. Validate the API response and retain the request ID for support or debugging.
  2. Read risk_level, risk_score, and signals together.
  3. Map the result to an action such as allow, challenge, review, or reject.
  4. Log the decision without exposing the API key or unnecessary personal data.
  5. Handle authentication, credit, rate-limit, and server errors separately from an email-risk result.

For a working product overview and current request examples, visit the disposable email detection API developer page. The AntiTemp documentation is the next stop for API-key and integration guidance.

API detection versus a disposable email blocklist

A disposable email blocklist answers whether a domain is already known. An API detector can return richer context and a policy-ready risk result, including signals that are not represented by a single list lookup.

AntiTemp does not publish its internal detection data as a raw downloadable blocklist. Use the API when you need a current result for a specific address and want a score, evidence, and recommendation in the same response. If your application also maintains a local allowlist or denylist, apply those business rules alongside the API result.

Frequently Asked Questions

How do I detect disposable email addresses via API?

Send a server-side POST request to https://www.antitempmail.com/api/v1/email/check with an Authorization: Bearer YOUR_API_KEY header and a JSON body containing the email address. Read the returned risk score, risk level, signals, explanation, and recommendation before applying your signup or lead policy.

What is a temp mail detector?

A temp mail detector checks whether an address is associated with a temporary or disposable inbox. AntiTemp combines multiple detection signals and returns both a risk result and the evidence your application can use to allow, challenge, review, or reject the address.

Is there a free disposable email blocklist API?

AntiTemp provides trial access to its disposable email detection API rather than a raw downloadable blocklist. Create an account, generate an API key, and use the available trial credits to test single-address checks against your integration.

Next steps

Open the developer guide for the disposable email detection API, create an API key, and run the curl request above from a server-side environment. Begin with logging and review, then adjust your policy after you have representative results from your own traffic.