Spam Detector is a simple tool for detecting spam in a text. It utilize an email address or IP address to validate the given text against the spam database.
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": {
// Spam Detector response payload
}
}
About the Spam Detector API
Spam Detector works by analyzing the text provided and detecting if it is spam. It uses advanced algorithms to analyze the text and return the likelihood of spam.
What people use it for
- Content Moderation
- Use the Spam Detector API to detect spam in content. Use the data to filter out spam, protect users, and maintain quality
- Email Validation
- Detect spam by using the Spam Detector API to validate email addresses. Use the data to verify emails, prevent fraud, and protect against spam
- Text Analysis
- Use the Spam Detector API to analyze text for spam. Use the data to identify spam, filter out unwanted content, and maintain security
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 Spam Detector
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Spam Detector API do?
How do I authenticate Spam Detector API requests?
How much does the Spam Detector API cost?
How fast is the Spam Detector API?
What response formats does the Spam Detector API support?
What HTTP method does the Spam Detector API use?
Request parameters — POST /v1/spamdetector
Sent as JSON in the request body. 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 |
|---|---|---|---|
textRequired | string | Congratulations! You have won a free iPhone. Click here to claim your prize now! | The text to detect spam in length 0-50000 |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
emailOptional | string | [email protected] | The email address to validate against the spam database. This is optional email |
ipOptionalPremium | string | 192.168.1.1 | The IP address to validate against the spam database. This is optional ip |
curl -X POST "https://api.apiverve.com/v1/spamdetector" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Can you please spare some change?! Desperate!!! Send cash","email":"[email protected]","ip":"122.180.184.182"}'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. |
content-typeRequired | POST body | application/json |
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 — POST /v1/spamdetector
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": {
"likelySpam": true,
"isDisposableEmail": false,
"isIPBlacklisted": false,
"ipDetails": {
"country": "IN",
"region": "DL"
},
"parsed": true
}
}
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 |
|---|---|---|---|
likelySpam | boolean | true | Indicates whether the text is likely spam |
isDisposableEmailPremium | boolean | false | Indicates if email address uses disposable email service |
isIPBlacklistedPremium | boolean | false | Indicates if IP address is on malicious blocklist |
ipDetails | object | {...} | |
countryPremium | string | "IN" | Country code where IP address is geographically located |
regionPremium | string | "DL" | Region or state where IP address is located |
parsed | boolean | true | Indicates whether input data was successfully parsed |
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 — 10 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 | Spam Detector calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
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 — POST /v1/spamdetector
No SDK to install — this is a plain HTTPS call to /v1/spamdetector 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/spamdetector" \
-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 — POST /v1/spamdetector
Install the Node.js SDK, then call the Spam Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/spamdetectorconst res = await fetch("https://api.apiverve.com/v1/spamdetector", {
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 — POST /v1/spamdetector
Install the Python SDK, then call the Spam Detector API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-spamdetectorimport requests
res = requests.get(
"https://api.apiverve.com/v1/spamdetector",
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 — POST /v1/spamdetector
Install the C# / .NET SDK, then call the Spam Detector 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.SpamDetectorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/spamdetector");
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 — POST /v1/spamdetector
No SDK to install — this is a plain HTTPS call to /v1/spamdetector 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/spamdetector", 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 — POST /v1/spamdetector
No SDK to install — this is a plain HTTPS call to /v1/spamdetector 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/spamdetector");
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 — POST /v1/spamdetector
No SDK to install — this is a plain HTTPS call to /v1/spamdetector 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/spamdetector")
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 Spam Detector 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 — Spam Detector 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 Spam Detector 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 →
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 
Email Validation Best Practices: Beyond Simple RegexEmail validation beyond regex. Learn how to verify deliverability without rejecting legitimate users.Read