ResponsesResponse Headers

Response Headers

Every header the transmute API sets — request correlation, rate limit, quota, warnings, paging, and idempotency indicators.

Correlation

HeaderOnMeaning
X-Request-IdEvery responseCorrelation id (req_<ulid>), echoed from your inbound X-Request-Id if you send one. Also present as requestId in error bodies. Quote this to support — it's how we find a request in our body-free logs.

Rate limit (per-second token bucket)

Set on every authenticated response — see Rate Limits & Quotas:

HeaderMeaning
RateLimit-LimitRequests allowed in the current window
RateLimit-RemainingRequests remaining
RateLimit-ResetSeconds until the window resets
Retry-AfterOn 429 only — seconds to wait

Monthly quota

Set on the four metered routes (POST /v1/convert, /v1/normalize, /v1/validate, /v1/enrich):

HeaderMeaning
X-Quota-LimitThe pool this key draws from: your plan's monthly included conversions (live keys) or the one-time 250-request test allowance (test keys)
X-Quota-RemainingRemaining in that pool before this request, clamped at 0

Conversion metadata

HeaderOnMeaning
X-Transmute-WarningsBare-document responsesCount of warnings that couldn't ride in the body
X-Transmute-Warnings-LinkBare-document responsesLink to the warning registry
X-Transmute-PagesPaged text/plain MT outputNumber of MT pages concatenated in the response

Idempotency

HeaderMeaning
Idempotency-Replayed: trueThis response came from the 24-hour replay cache — it was not re-executed and not billed. See Idempotency.

Request headers you can send

HeaderMeaning
Authorization: Bearer ...Your API key or OAuth token
Idempotency-KeyOpt-in safe retries (1–255 chars)
X-Request-IdYour own correlation id, echoed back
X-Transmute-From / X-Transmute-To / X-Transmute-To-VersionFormat selection for raw bodies (lowest precedence — envelope and query parameters win)
Acceptapplication/json (envelope, default), application/xml / text/plain (bare document)