Skip to main content
POST
Check a disposable email address
Use this endpoint when your application needs a disposable-email signal during sign-up, account recovery, or abuse-prevention checks. It evaluates one email address and returns whether its domain appears in the configured disposable-email lists.
Live Testing Guide: Before using Try it, create a Development project, then enter its Client ID and Client Secret. Configure the relevant provider for that project before sending the request.

API endpoint

POST

Request fields

Outside the documentation Playground, keep the Project Client Secret on your backend. The request body intentionally uses POST so an email address is not placed in the URL. Only submit addresses that you are permitted to process.

Result fields

is_disposable: false means the configured lists did not contain a matching domain. It is not a guarantee that an address is owned by a real person or safe to trust.

Request example

curl

Response example

Error codes

Keep the JSON request_id or X-APIX-Request-ID response header with your support record. It is the safest way for AvraAPI support to trace a request.
See the REST API guide for shared credential, privacy, and error-handling guidance.

Playground resources

The generated reference below lists this endpoint’s API standard details: request fields, authorizations, and response schema. The complete integration guide, request and response examples, and endpoint-specific error handling are above.

Authorizations

X-API-KEY
string
header
required

Your Development project's Client ID. Enter your own value in the Documentation Playground.

X-API-SECRET
string
header
required

Your Development project's Client Secret. Mintlify does not proxy these requests; the browser sends them directly to AvraAPI. Never enter a Production secret in the Documentation Playground.

Headers

X-ENV
enum<string>
default:development

Selects the Development credential environment. The Documentation Playground exposes Development values only; normal backend integrations may use their documented Production credentials outside this tool.

Available options:
dev,
development
Accept
string

Requests a JSON response where the selected operation supports JSON.

Example:

"application/json"

X-Privacy-Mode
boolean
default:false

Optional privacy override. Turn this on to request that AvraAPI suppress request-payload storage in observability logs for this request.

Example:

true

Body

application/json
email
string<email>
required

An RFC-compatible email address.

Maximum string length: 255
Example:

"documentation@example.invalid"

Response

Disposable-email result.

success
enum<boolean>
required
Available options:
true
request_id
string<uuid>
required

Include this value when contacting AvraAPI support.

data
object
required

Operation-specific result data.

Last modified on October 1, 2026