Spec

Code snippets

curl "https://api.oanor.com/escape-api/v1/meta" \
  -H "x-oanor-key: oanor_test_..."

await fetch("https://api.oanor.com/escape-api/v1/meta", {
  headers: { "x-oanor-key": "oanor_test_..." }
});

$ch = curl_init("https://api.oanor.com/escape-api/v1/meta");
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$out = curl_exec($ch);

import requests
requests.get(
    "https://api.oanor.com/escape-api/v1/meta",
    headers={"x-oanor-key": "oanor_test_..."}
)

Example response

A real response from this endpoint, captured by the latest health check.

{
    "data": {
        "name": "Escape API",
        "notes": "The sql context produces a quoted literal but is not a substitute for parameterised queries — use bound parameters for untrusted input. For base64/hex/URL/HTML-entity encoding use an encoding API. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/escape",
                "params": {
                    "text": "the string (required)",
                    "context": "regex|shell|json|csv|sql (required)"
                },
                "returns": "the escaped string"
            },
            {
                "path": "/v1/contexts",
                "params": [],
                "returns": "the supported contexts with examples"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Escape a string so it is safe to embed in a given context — a regular expression (literal match), a shell command (POSIX), a JSON string, a CSV field (RFC 4180) or a SQL string literal. Pure local, no key."
    },
    "meta": {
        "timestamp": "2026-06-03T01:09:42.700Z",
        "request_id": "86bc7224-a1db-4a29-8c71-8384a44793ba"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}