Spam Detector API
Overview
To use Spam Detector, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/spamdetectorExample
How to call the Spam Detector API in different programming languages.
curl -X POST \
"https://api.apiverve.com/v1/spamdetector" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text": "Can you please spare some change?! Desperate!!! Send cash",
"email": "[email protected]",
"ip": "122.180.184.182"
}'const response = await fetch('https://api.apiverve.com/v1/spamdetector', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"text": "Can you please spare some change?! Desperate!!! Send cash",
"email": "[email protected]",
"ip": "122.180.184.182"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text": "Can you please spare some change?! Desperate!!! Send cash",
"email": "[email protected]",
"ip": "122.180.184.182"
}
response = requests.post('https://api.apiverve.com/v1/spamdetector', headers=headers, json=payload)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"text": "Can you please spare some change?! Desperate!!! Send cash",
"email": "[email protected]",
"ip": "122.180.184.182"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/spamdetector", bytes.NewBuffer(jsonPayload))
req.Header.Set("X-API-Key", "your_api_key_here")
req.Header.Set("Content-Type", "application/json")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}{
"status": "ok",
"error": null,
"data": {
"likelySpam": true,
"isDisposableEmail": false,
"isIPBlacklisted": false,
"ipDetails": {
"country": "IN",
"region": "DL"
},
"parsed": true
}
}Authentication
The Spam Detector API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Spam Detector API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Spam Detector API:
Detect Spam
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text to detect spam in | - | |
email | string | optional | The email address to validate against the spam database. This is optional | - | |
ipPremium | string | optional | The IP address to validate against the spam database. This is optional Format: ip (e.g., 192.168.1.1) | - |
Response
The Spam Detector API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?xml version="1.0" encoding="UTF-8"?>
<response>
<status>ok</status>
<error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<data>
<likelySpam>true</likelySpam>
<isDisposableEmail>false</isDisposableEmail>
<isIPBlacklisted>false</isIPBlacklisted>
<ipDetails>
<country>IN</country>
<region>DL</region>
</ipDetails>
<parsed>true</parsed>
</data>
</response>
status: ok
error: null
data:
likelySpam: true
isDisposableEmail: false
isIPBlacklisted: false
ipDetails:
country: IN
region: DL
parsed: true
| key | value |
|---|---|
| likelySpam | true |
| isDisposableEmail | false |
| isIPBlacklisted | false |
| ipDetails | {country:IN,region:DL} |
| parsed | true |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains the API response data if successful, otherwise null | {...} |
Learn more about response formats →
Response Data Fields
When the request is successful, the data object contains the following fields:
| Field | Type | Sample Value | Description |
|---|---|---|---|
likelySpam | boolean | Indicates whether the text is likely spam | |
isDisposableEmailPremium | boolean | Indicates if email address uses disposable email service | |
isIPBlacklistedPremium | boolean | Indicates if IP address is on malicious blocklist | |
ipDetails | object | - | |
â”” countryPremium | string | Country code where IP address is geographically located | |
â”” regionPremium | string | Region or state where IP address is located | |
parsed | boolean | Indicates whether input data was successfully parsed |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Spam Detector through GraphQL to combine it with other API calls in a single request. Query only the spam detector data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
spamdetector(
input: {
text: "Can you please spare some change?! Desperate!!! Send cash"
email: "[email protected]"
ip: "122.180.184.182"
}
) {
likelySpam
isDisposableEmail
isIPBlacklisted
ipDetails {
country
region
}
parsed
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Spam Detector API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Spam Detector requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Spam Detector API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Spam Detector
Official Spam Detector packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Spam Detector works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Spam Detector?
How many credits does Spam Detector cost?
Each successful Spam Detector API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful spam detector lookups.
Can I use Spam Detector in production?
The free plan is for testing and development only. For production use of Spam Detector, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.
Can I use Spam Detector from a browser?
What happens if I exceed my Spam Detector credit limit?
When you reach your monthly credit limit, Spam Detector API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.








