Spam Detection API Specification & Integration Reference
Public API Page

POST Content Moderation & Spam API

/api/v1/ai/spam-detection

Analyze text to detect spam, promotional abuse, toxicity, and PII, keeping your platform safe from malicious actors.

Base Billing 1 Credit
Target Latency < 150ms (p50)
Client Timeout 5.0s (recommended)
SLA Guarantee 99.9% Uptime
JSON Contract Deterministic v1

Architecture Role & AI Definition

Content Moderation & Spam API provides low-latency, deterministic REST execution for production engineering workflows. It processes structured payloads with strict schema validation, returns uniform JSON envelopes, and is secured via SHA-256 API key authentication with atomic credit pre-authorization locks.

Production Reliability Guidelines

1. Strict Timeout Windows

Configure a hard client timeout of 5 to 8 seconds. If network latency spikes, cancel connection to avoid holding open sockets in worker pools.

2. Exponential Backoff with Jitter

Upon receiving 429 Rate Limit or transient 5xx, pause with exponential backoff:
wait = min(max_backoff, base * 2^attempt + jitter).

3. Atomic Pre-Auth Locks

RSFlowHub acquires an atomic lock verifying base credits before model invocation. If validation fails, zero credits are deducted.

Request Body Parameters

Field Type Required Description
text string Required The raw text content to analyze (Max: 5,000 characters).
content_type string Optional Context of where the text came from (e.g., "blog_comment", "email", "product_review"). Helps the AI understand the expected format.
strictness string Optional Filter strictness: "low", "medium", or "high". Default is "medium".
detect_toxicity boolean Optional Optional. Set to true to analyze the text for hate speech, harassment, and severe profanity.
detect_pii boolean Optional Optional. Set to true to detect Personal Identifiable Information (emails, phone numbers, SSNs).
return_sanitized boolean Optional Optional. Set to true to receive a redacted version of the text where malicious links, profanity, and PII are replaced with "[REMOVED]".
model string Optional Optional AI model to use.

Example Request (Full Moderation)

In this example, we test a highly abusive comment and request all advanced moderation features, including sanitization.

JSON Request
{
  "text": "You guys are idiots! Call me at 555-019-2831 or visit my crypto scam site http://bit.ly/scam-link to win free money.",
  "content_type": "blog_comment",
  "strictness": "high",
  "detect_toxicity": true,
  "detect_pii": true,
  "return_sanitized": true
}
curl-trigger.sh cURL
curl -X POST https://rsflowhub.com/api/v1/ai/spam-detection \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "You guys are idiots! Call me at 555-019-2831 or visit my crypto scam site http://bit.ly/scam-link to win free money.",
    "content_type": "blog_comment",
    "strictness": "high",
    "detect_toxicity": true,
    "detect_pii": true,
    "return_sanitized": true
  }'

Example Response

The API processes the text and returns a comprehensive moderation report, including the safely redacted text.

response.json JSON Response
200 OK 118ms
{
  "success": true,
  "data": {
    "result": {
      "is_spam": true,
      "spam_score": 0.98,
      "spam_category": "promotional",
      "reason": "Contains a suspicious shortlink and unsolicited promotional language.",
      "is_toxic": true,
      "toxicity_score": 0.85,
      "contains_pii": true,
      "pii_types": ["phone_number"],
      "sanitized_text": "You guys are [REMOVED]! Call me at [REMOVED] or visit my crypto scam site [REMOVED] to win free money."
    }
  },
  "meta": {
    "credits_used": 2,
    "credits_remaining": 991
  }
}

API Request Example

Use the cURL snippet below to test the endpoint.

curl-trigger.sh cURL
curl -X POST 'https://rsflowhub.com/api/v1/ai/spam-detection' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "text": "You guys are idiots! Call me at 555-019-2831 or visit http://bit.ly/scam-link",
    "content_type": "blog_comment",
    "detect_toxicity": true,
    "detect_pii": true,
    "return_sanitized": true
}'

Common Failure Modes & Troubleshooting Matrix

HTTP Code Error Code Root Cause Recommended Remediation
400 bad_request Malformed JSON syntax or missing required top-level parameters. Validate JSON payload with Content-Type: application/json and ensure all required fields are present.
401 unauthorized Missing, revoked, or incorrectly formatted x-api-key header. Verify API key exists in Dashboard → API Keys and pass in x-api-key or Authorization: Bearer.
402 insufficient_credits Account credit balance is lower than the base required credits (2 credits). Top up credits in billing settings or enable auto-recharge to prevent pipeline interruption.
422 validation_error Input failed parameter constraints (e.g., character length exceeded or invalid array types). Review parameters table above and adjust payload length, types, or structure accordingly.
429 rate_limit_exceeded Concurrency limit (60 requests/minute default) reached for this endpoint key. Back off and retry using the timestamp in Retry-After response header, or batch requests.

Technical Q&A (FAQ)

We recommend setting a client timeout of 5 to 8 seconds. While average latency is under 150ms, large input payloads or complex reasoning models may require additional processing time.

RSFlowHub uses an atomic pre-flight check. Before processing, the gateway validates that your wallet has at least 2 base credits. If the request fails validation (422) or is malformed (400), no credits are charged.

When a 429 is received, your application should respect the 'Retry-After' header and use an exponential backoff retry policy with randomized jitter to prevent thundering herd problems.

Every successful response returns { "success": true, "data": { ... }, "meta": { "credits_used": int, "credits_remaining": int } }.

Ready to build?

Create your free account and make your first API call in minutes.