Disposable Phone Number Checker is an API that checks whether a given phone number is a known disposable or temporary number. Useful for fraud prevention, user verification, and security.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Disposable Phone Number Checker response payload
}
}
About the Disposable Phone Number Checker API
Disposable Phone Number Checker uses an up-to-date database of known disposable phone numbers from SMS receiving services. This helps identify temporary numbers often used for spam, fraud, or bypassing verification systems.
What people use it for
- User Registration
- Detect and block disposable phone numbers during user registration to prevent fake accounts and improve user quality
- Fraud Prevention
- Identify temporary phone numbers used in fraudulent activities and protect your platform from abuse
- SMS Verification
- Ensure SMS verification codes are sent to real phone numbers, not temporary ones that can be easily abandoned
- Lead Quality
- Filter out leads with disposable phone numbers to focus on genuine prospects and improve conversion rates
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Disposable Phone Number Checker
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Disposable Phone Number Checker API do?
How do I authenticate Disposable Phone Number Checker API requests?
How much does the Disposable Phone Number Checker API cost?
How fast is the Disposable Phone Number Checker API?
What response formats does the Disposable Phone Number Checker API support?
What HTTP method does the Disposable Phone Number Checker API use?
Request parameters — GET /v1/disposablephone
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
phoneRequired | string | +12085813945 | The phone number to check in E.164 format (e.g., +12085813945) phone |
curl "https://api.apiverve.com/v1/disposablephone?phone=%2B12085813945" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/disposablephone
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"phone": "+12085813945",
"isDisposable": true,
"firstSeen": "2024-01-30"
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
phone | string | "+12085813945" | The phone number that was checked |
isDisposable | boolean | true | Whether the phone number is a known disposable/temporary number |
firstSeen | string | "2024-01-30" | Date the number was first seen on a disposable list, null if not listed |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 6 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Disposable Phone Number Checker calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 33 | Free |
| Starter | $29.99 | 200,000 | 33,333 | $0.90 |
| Pro | $99.99 | 1,000,000 | 166,666 | $0.60 |
| Mega | $299.99 | 4,000,000 | 666,666 | $0.45 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/disposablephone
No SDK to install — this is a plain HTTPS call to /v1/disposablephone with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/disposablephone" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/disposablephone
Install the Node.js SDK, then call the Disposable Phone Number Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/disposablephoneconst res = await fetch("https://api.apiverve.com/v1/disposablephone", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/disposablephone
No SDK to install — this is a plain HTTPS call to /v1/disposablephone with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/disposablephone",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/disposablephone
Install the C# / .NET SDK, then call the Disposable Phone Number Checker API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.DisposablePhoneNumberCheckerusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/disposablephone");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/disposablephone
No SDK to install — this is a plain HTTPS call to /v1/disposablephone with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/disposablephone", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/disposablephone
No SDK to install — this is a plain HTTPS call to /v1/disposablephone with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/disposablephone");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/disposablephone
No SDK to install — this is a plain HTTPS call to /v1/disposablephone with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/disposablephone")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Disposable Phone Number Checker form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Disposable Phone Number Checker API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Disposable Phone Number Checker API.
Data Validation
- Card Validator
- Disposable Email Checker
- Disposable Phone Number Checker
- Email Validator
- Password Strength
- Phone Number Validator
- SEO Quick Validator
- Spam Detector
- Username Profanity
Related articles
All articles →
The Phone Number Validation Rabbit HoleValidating phone numbers seems simple until you try it. Here's what makes it surprisingly complex.Read
Add Secure Password Generation to Your AppGenerate cryptographically secure passwords via API. Tutorial with code examples for signup flows, admin panels, and password managers.Read
Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read