Overview
Endpoints to validate, verify, and discover emails in real time with Clearout APIs.
Clearout provides a set of RESTful APIs for email validation, advanced verification, and discovery at scale. You can verify or discover millions of email addresses in real time, with endpoints covering email verification, email finding, reverse lookup, remaining credits, company-to-domain auto-completion, and additional domain utilities.
How to Get Started
Getting started with Clearout APIs is quick and straightforward:
Create a free Clearout account
Sign up to receive 100 free credits and instant access to the API.
Generate your API token
Find your API token in the Clearout developer dashboard and use it to authenticate all API requests.
Set service-level settings
Configure your preferred settings, then call the service API endpoint to get the response.
Integrate with your application
Call APIs from your backend or automation workflows to verify or discover email addresses.
Go live and scale
Monitor your usage, manage credits, and upgrade your plan as it grows.
API Base URL
Clearout APIs use a base URL to which all endpoint paths are appended. Since the base URL may vary based on your account host region, API users should check it by logging into the Clearout app and navigating to the Developer → Reference tab.
Generating an API Token
After signing up and logging in, select the Developer tab located at the top-right, and then click on the API → Create API Token button. All created tokens are listed under this tab. Use this token as the Bearer value in all API requests. Tokens can be reset at any time by clicking the Reset Token icon.
Log in to your Clearout dashboard.
Navigate to Developer → API.
Click Create API Token.
Use the token as the
Authorization: Bearer <TOKEN>header in all API requests.
Example - Using a CURL Request
API Response Objects and Status Codes
HTTP response codes
These are the HTTP response codes set by Clearout to indicate the success or failure of a request:
HTTP Status Code
Meaning / Description
200
Success
400
Bad Request
401
Unauthorized
402
Payment Required
403
Forbidden
415
Invalid Content Type (must be application/json)
429
Rate Limit Exceeded
500
Internal Server Error
503
Service Unavailable
524
Request Timeout
Clearout error codes
The following Clearout error codes will be included in the error response object:
Error Code
Description
1001
You’ve reached the maximum number of bulk verify requests. Please wait for the existing request to complete or contact [email protected]
1002
You’ve exhausted your credits. Please add additional credits to continue
1004
Unable to determine email addresses in the list. Ensure emails are present or explicitly specified in a header row using Email, Emails, Email address, or Emailaddress
1007
List has expired. Contact [email protected]
1008
You are not authorized to access this resource
1017
You’ve reached the daily verify limit. Try again the next day or contact [email protected]
1027
Email address not found
1028
Available credits (AVAILABLE_CREDITS) are insufficient to verify NUMBER_OF_EMAILS emails
1029
List is not available
1030
API rate limit reached. Retry after [CURRENT TIMESTAMP + 60 seconds] UTC, or upgrade your plan / contact [email protected]
1031
You have exhausted your credits.
1032
You have reached your daily verify limit; please try next day
1074
Invalid origin
Flatten Response Object
By adding response=flat as a query parameter to any API request, the nested object will be converted into a flat object. This is helpful when your system does not support nested JSON objects.
Cross-Origin Resource Sharing (CORS)
Clearout does not support API requests directly from web browsers or client apps. This means Clearout APIs can be used only from your server-side application
Limits and Quotas
API Rate Limit
Clearout APIs apply rate limits to ensure platform reliability and fair usage across all plans. Rate-limit details are included in the response headers for every API request.
Rate Limit Headers
Header
Description
x-ratelimit-limit
Total number of requests allowed within a 60-second window
x-ratelimit-remaining
Number of requests remaining in the current 60-second window
x-ratelimit-reset
Time remaining (in seconds) before the rate-limit window resets
Example Response
How It Works
A maximum of 100 requests can be made per minute
42 requests are still available in the current window
The quota resets in 18 seconds
When the Limit Is Exceeded
If you exceed the allowed request limit:
HTTP Status Code:
429 Too Many RequestsClearout Error Code:
1030
You should wait until the duration specified x-ratelimit-reset elapses before retrying.
To increase your rate limit, upgrade your plan or contact support.
Plan-Specific Limits
Clearout offers flexible pay-as-you-go and subscription plans, each with different API limits. Compared to pay-as-you-go plans, subscription plans offer higher limits, which you can increase by selecting an add-on option.
Please find below the breakup of plans and API Request Per Limits (RPM).
Monthly/Annual Subscription
3,000
25
14
10,000
55
40
50,000
90
55
100,000
135
85
250,000
185
110
500,000
240
140
1,000,000
300
190
More than 5,000,000
400
240
Pay-As-You-Go
5,000
20
10
10,000
45
30
100,000
70
45
250,000
110
70
500,000
150
90
1,000,000
190
110
5,000,000
240
150
More than 10,000,000
320
190
For more details on limits and pricing, please refer to the pricing page here.
Testing
To confirm that your integration works as intended without incurring credits, use the test email addresses listed below for all possible email verification results.
An invalid email address
A valid email address
Accept-all or catch-all email address
An unknown email address
Safe to send email address
Not a safe to send email address
Risky email address
Disposable email address
Role- or group-based email address
Free email provider address
Gibberish email address
Hard bounce email address
Soft bounce email address
An auto-suggested email address
Syntax error email address
Greylisted email address
Spamtrap email address
Found part of blocklist email address
Found part of allowlist email address
Found part of blocklist domain
Found part of allowlist domain
The domain does not exist for the email address
Not a mail server email address
Mailbox not found email address
Mail quota exceeded email address
DNS query timeout email address
Unroutable mail exchange server email address
Dormant email address
Receiving limit exceeded email address
Last updated
Was this helpful?