Spec

Code snippets

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

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

$ch = curl_init("https://api.oanor.com/contentdisposition-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/contentdisposition-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": "Content-Disposition API",
        "notes": "Per RFC 6266, filename* (extended, Unicode) takes precedence over a plain filename when both are present. Non-ASCII filenames are emitted as both filename (ASCII fallback) and filename*. This builds and parses the header string — it does not serve a file. Nothing is stored.",
        "version": "v1",
        "endpoints": [
            {
                "path": "/v1/parse",
                "params": {
                    "header": "a Content-Disposition header value (required)"
                },
                "returns": "the disposition type, filename, form field name and parameters"
            },
            {
                "path": "/v1/build",
                "params": {
                    "name": "the form field name (for form-data)",
                    "type": "attachment (default), inline or form-data",
                    "filename": "the download filename (any Unicode)",
                    "ascii_only": "true to force a plain ASCII filename"
                },
                "returns": "the Content-Disposition header string"
            },
            {
                "path": "/v1/meta",
                "params": [],
                "returns": "this document"
            }
        ],
        "description": "Parse and build HTTP Content-Disposition headers (RFC 6266 with RFC 5987 filename* encoding). The parse endpoint reads a header into its disposition type (attachment, inline or form-data), its filename — correctly decoding the extended filename*=UTF-8''… form and preferring it over a plain filename, as the spec requires — the form-data field name, and any other parameters. The build endpoint assembles a correct header from simple fields and, when a filename contains non-ASCII characters, automatically emits both an ASCII fallback filename and the percent-encoded filename* so every browser gets the right name. Pure local, no key."
    },
    "meta": {
        "timestamp": "2026-06-03T09:25:02.489Z",
        "request_id": "861eb6b2-1a22-4c52-9d58-1ed13ddcf6a4"
    },
    "status": "ok",
    "message": "Meta",
    "success": true
}