API keys & authentication

Use your enc_ API key in the Authorization header for developer API requests.

Authorization: Bearer YOUR_API_KEY

Create an API key

Create and manage keys with POST /api/account/keys. The endpoint reference covers the authentication requirements, request body, and response shape.

Key behavior

Behavior	Detail
Format	An `enc_` API key
Scope	Tied to your user account
Revocation	Instant revoked keys are rejected immediately
Usage tracking	Every request is logged with credits consumed and response time

Validate an email

Use Email Validity to verify the authentication setup and validate your first address. It is the same request used in the Quickstart.

curl -X POST https://developer.encrata.com/api/email/validity \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "satya@microsoft.com"}'

Handle common errors

Email API errors use this shape:

{
  "error": "Invalid email address",
  "code": "bad_request"
}

Status	`code` or error	When it happens	What to do
`400`	`bad_request`	The JSON body is invalid or `email` is not a valid address.	Send valid JSON with an `email` field.
`401`	`unauthorized`	The Bearer token is missing, malformed, invalid, or revoked.	Send an active `enc_` key in the `Authorization` header.
`402`	`insufficient_credits`	Your account does not have enough credits for the lookup.	Add credits, then retry.
`402`	`api key credit limit exceeded`	The key has reached its configured credit limit.	Raise the key limit or use another permitted key.
`405`	`method_not_allowed`	The endpoint was called with a method other than `POST`.	Send a `POST` request.
`413`	`payload_too_large`	The request body is larger than the endpoint accepts.	Send only the required request body.
`429`	`rate_limited`	You sent requests faster than the endpoint allows.	Wait before retrying; use exponential backoff.
`502`, `503`, `504`	`upstream_unavailable`	A required upstream provider is temporarily unavailable.	Retry with exponential backoff.
`500`	`internal`	An unexpected server error occurred.	Retry later; include the response request ID when contacting support.

Do not retry 400 or 401 responses unchanged. Correct the request or credential first. Retries are appropriate for 429 and 5xx responses.

Keep your API key secret. Do not commit it to version control or expose it in client-side code.

Get set up

Run your integration

Examples

Integrations

AI Tools

Agent-Ready Docs

API keys & authentication

Create an API key

Key behavior

Validate an email

Handle common errors

​Create an API key

​Key behavior

​Validate an email

​Handle common errors

Create an API key

Key behavior

Validate an email

Handle common errors