Skip to content
RSFlowHub
Developer docs API v1 Stable OpenAPI SDKs Playground
PII Redaction API Specification & Integration Reference

POST PII Redaction API

/api/v1/ai/pii-redaction

Automatically detect and mask Personally Identifiable Information (PII) such as names, emails, phone numbers and card numbers before text reaches your logs, tickets or analytics tools.

Base Billing 1 Credit
Typical Response 1-3 s
Client Timeout 15-30 s (recommended)
Provider Fallback Automatic
JSON Contract Envelope v1

Architecture Role & AI Definition

PII Redaction 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.

Freemium API
This API is part of the utility tier. Every plan includes a shared monthly quota of free utility requests (1,000/month on the Free plan). Credits are only used after the quota is reached.

Request Body Parameters

Field Type Required Description
text string Required The raw text to be sanitized (Max: 10,000 characters).
redact_types array of strings Optional Specific types to redact. Allowed: `names`, `emails`, `phone_numbers`, `credit_cards`, `ssn`, `addresses`, `passwords`, `ip_addresses`. If empty, redacts all high-risk PII.
redaction_style string Optional How to mask the data. `placeholder` (e.g., [EMAIL]), `asterisk` (e.g., j***@gmail.com), or `scramble`. Default is `placeholder`.
return_entities boolean Optional Optional. If true, returns an analytics array summarizing the types of PII detected and redacted.

Example Request (Selective Redaction)

In this example, we ask the API to specifically target and asterisk-out credit cards and emails, while safely ignoring names or other data.

JSON Request
{
  "text": "Hey, it's Jane Smith. Please update my billing. My new card is 4111-2222-3333-4444 and my receipt email is jane.smith99@example.com. Thanks!",
  "redact_types": ["credit_cards", "emails"],
  "redaction_style": "asterisk",
  "return_entities": true
}
curl-trigger.sh cURL
curl -X POST https://rsflowhub.com/api/v1/ai/pii-redaction \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "text": "Hey, it'\''s Jane Smith. Please update my billing. My new card is 4111-2222-3333-4444 and my receipt email is jane.smith99@example.com. Thanks!",
    "redact_types": ["credit_cards", "emails"],
    "redaction_style": "asterisk",
    "return_entities": true
  }'

Example Response

The API safely sanitizes the requested fields. Notice how "Jane Smith" was intentionally ignored because `names` was not included in the `redact_types` array. The `entities_redacted` array securely provides analytics without exposing the raw strings.

response.json JSON Response
200 OK
{
  "success": true,
  "request_id": "req_7f3a9c2d1e4b8a6f",
  "data": {
    "result": {
      "redacted_text": "Hey, it's Jane Smith. Please update my billing. My new card is ****-****-****-4444 and my receipt email is j***@example.com. Thanks!",
      "entities_redacted": [
        {
          "type": "CREDIT_CARD",
          "count": 1
        },
        {
          "type": "EMAIL",
          "count": 1
        }
      ]
    }
  },
  "meta": {
    "version": "v1",
    "timestamp": "2026-09-27T12:34:56+00:00"
  }
}

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/pii-redaction' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{
    "text": "My number is 555-1234",
    "redaction_style": "placeholder"
}'

Want to try it without code? Test this request in the live Playground.


Common Failure Modes & Troubleshooting Matrix

HTTP Code Error Code Root Cause Recommended Remediation
401 API_KEY_MISSING / INVALID_API_KEY No key sent, or the key was mistyped or regenerated. Copy the current key from Dashboard → API Keys and send it as Authorization: Bearer (or X-API-Key).
402 INSUFFICIENT_CREDITS Your balance cannot cover the estimate for this call (base 1 credits plus input/output size). Buy a plan in Dashboard → Billing. Nothing was charged.
422 VALIDATION_ERROR A field is missing, too long or the wrong type, or the body is not valid JSON. Read error.details for the field messages and fix the request. Do not retry the same body.
429 RATE_LIMIT_EXCEEDED Your plan-wide or per-endpoint per-minute limit was reached. Wait the seconds in the Retry-After header, then retry with jitter. Rate limits
502 AI_PROVIDER_ERROR The AI model and its backup both failed. Retry with backoff and check the status page. Nothing was charged.

Technical Q&A (FAQ)

Each PII Redaction API call costs 1 base credit, plus about 1 credit per 1,000 input characters and 1 credit per 500 output characters. It is a utility endpoint, so it also counts toward the free monthly quota included in every plan (1,000 requests/month on the Free plan) before any credits are used. Failed calls are not charged.

The text field accepts up to 10,000 characters per request. Larger inputs return a 422 validation error, so split long content into chunks.

PII Redaction API runs on Google Gemini (gemini-2.5-flash), with automatic fallback to OpenAI (gpt-4.1-mini) if the primary provider fails or rate-limits. Models are tuned per task, so your integration does not change when we upgrade them.

Yes. Identical requests within 24 hours are answered from cache, which is faster and free or discounted in credits.

Most requests complete in 1 to 3 seconds; set a client timeout of 60 seconds so a call that switches to a backup model can finish. On HTTP 429, wait for the Retry-After delay. Retry network errors once or twice with exponential backoff and jitter.

Ready to build?

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

RSFlowHub

Sign in to continue

You'll come straight back to this page.

Forgot password?

New to RSFlowHub? Create a free account