Which operations are available?
encode, decode, hash, jwt_decode, normalize, data_uri_encode, and data_uri_decode. GET /api/v1/encoding-convert returns the full catalog including encodings and hash algorithms.
Encoding Convert API
Base64 / URL
SHA-256
JWT Inspect
Encode, hash, inspect. No signing.
Base64, URL encoding, SHA-256, Unicode normalization, and JWT claim inspection that always returns verified: false.
7 encodings · including base64urlsha256 · plus SHA-3JWT · inspect only1M · char cap
Encode, decode, or hash, instantly.
This calls the live Encoding Convert API. Pick an operation, edit the sample, and preview the result.
Request builder
Operation and input in, converted string out.
POST /encoding-convert
Public API is POST
Production sends JSON. This playground uses a GET demo proxy that forwards a capped POST upstream.
Output preview
Live response from the API, plus the exact request to reproduce it.
Running conversion...
Why Encoding Convert API
Text utilities agents actually need.
Common transport encodings
Base64, Base64url, Base32, Hex, URL, HTML entities, and Punycode in encode or decode.
Hash digests
SHA-256 by default, plus SHA-384, SHA-512, and SHA-3. Output as hex, base64, or base64url.
JWT inspection, not trust
Header, payload, and selected claims with verified: false. Signatures are never treated as valid.
Unicode normalization
NFC, NFD, NFKC, and NFKD so agents can canonicalize strings before compare or store.
Data URIs
Encode or decode data URIs with an explicit MIME type. Useful for small inline payloads.
Bounded and stateless
Inputs cap at 1,000,000 characters. Nothing is persisted. Signing and encryption are not in this API.
/api/v1/encoding-convert
Endpoints, at a glance.
POST an operation and input. GET the catalog for encodings, hash algorithms, and limits.
POST/api/v1/encoding-convert
Run an operation
encode, decode, hash, jwt_decode, normalize, data_uri_encode, or data_uri_decode.
GET/api/v1/encoding-convert
Catalog
Operations, encodings, hash algorithms, hash outputs, and max input length.
| Parameter | Type | Required | Description |
|---|---|---|---|
| operation | string | yes | encode, decode, hash, jwt_decode, normalize, data_uri_encode, or data_uri_decode. |
| input | string | yes | Text, encoded value, JWT, or data URI. Max 1,000,000 characters. |
| encoding | string | yes* | Required for encode/decode: base64, base64url, base32, hex, url, html-entity, punycode. |
| algorithm | string | yes* | Required for hash. Defaults to sha256. |
| output | string | no | Hash output: hex, base64, or base64url. |
| form | string | yes* | Unicode form for normalize: NFC, NFD, NFKC, or NFKD. |
Error reference
Failures you can plan for.
Every response includes a success flag and a correlationId for tracing.
400Validation Error
Invalid operation, encoding, algorithm, form, or input.
401Authentication Error
Missing or invalid gateway API key. Send x-api-key or api_key with every request.
404Not Found
Unknown route under /api/v1/encoding-convert.
413Payload Too Large
Input exceeds 1,000,000 characters.
429Rate Limit Error
More than 120 requests in a 15-minute window.
Example error response
{
"success": false,
"error": { "code": "VALIDATION_ERROR", "message": "Unsupported operation." },
"correlationId": "1784849006651-enc01"
}FAQ
API questions developers ask first.
Does JWT inspection verify signatures?
No. jwt_decode returns header, payload, selected claims, and verified: false. The service never treats decoded claims as trusted.
Can I hash a string with SHA-256?
POST operation=hash with algorithm=sha256 (default) and optional output of hex, base64, or base64url. MD5 and SHA-1 are compatibility-only.
How large can the input be?
Input is capped at 1,000,000 characters. Oversized payloads return 413 before conversion runs.
How do I authenticate requests?
Send your Datpaq API key as an x-api-key header or an api_key query parameter. Keys are created in the Datpaq dashboard and a free tier is included.
Encode, decode, and hash in one request.
Base64, URL encoding, and SHA-256 from a single endpoint with a consistent JSON envelope.