Decode a data: URI
API · /dataurl-api
Data URI API
Encode content into a data: URI and decode a data: URI back to its content (RFC 2397). data: URIs inline a file directly into HTML, CSS, JSON or email — perfect for small images, SVG, fonts and icons that you want to embed without a separate HTTP request. The encode endpoint wraps your content (given as UTF-8 text, base64 or hex for binary) with a chosen media type and charset, in either base64 or URL (percent) encoding; the decode endpoint parses any data: URI and returns its media type, charset, whether it was base64, the byte size, and the payload as text and/or base64. Pure local computation — no key, no third-party service, instant; up to 4 MB via POST. Live, nothing stored. 3 endpoints. Distinct from a plain base64/hex encoder and from SVG-specific tooling.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 88 ms
- Server probes · 24h
- Subscribers
- 4,604
- active
- Total calls
- 45
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 580 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 580 calls/month
- 2 req/sec
- Encode + decode
- No credit card
Starter
€0.20 /month
- 4,300 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 4.3k calls/month
- 8 req/sec
- base64 / URL, any media type
- Email support
Pro
€17.20 /month
- 116,000 calls / month
- 20 requests / second
- Hard cap (429 above quota, no overage)
- 116k calls/month
- 20 req/sec
- Embedding / build pipelines
- Priority support
Mega
€53.20 /month
- 600,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 600k calls/month
- 50 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Encoding API
A fast, fully-local encoding toolkit: encode and decode text between base64, base64url, base32 (RFC 4648), hex, URL percent-encoding, HTML entities, binary and ASCII85 — plus JWT inspection (decode header and payload without verifying the signature). Pure server-side compute, no third-party upstream, so responses are instant and always available. Ideal for developer tools, webhooks, data pipelines, debugging and integrations.
api.oanor.com/encoding-api
Morse Code API
Morse code conversion as an API, computed locally and deterministically. The encode endpoint turns text into International Morse code, mapping A–Z, the digits 0–9 and common punctuation to dots and dashes, separating letters with a space and words with a slash, and listing any unsupported characters it skipped. The decode endpoint turns Morse code back into text, accepting word separators written as a slash, a pipe or a wide gap, and marking unrecognised symbols. The timing endpoint computes the PARIS-standard timing from a words-per-minute speed — the dot duration is 1200/WPM milliseconds, a dash is three dots, and the gaps are one, three and seven dot units for intra-character, inter-character and word spacing — and, given a Morse message, the total number of units and the transmission time. The word PARIS is exactly 50 units, which defines the WPM scale. Everything is computed locally and deterministically, so it is instant and private. Ideal for amateur-radio, aviation, education, accessibility, puzzle and game app developers, signalling and CW-training tools, and learning Morse. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Morse code; for Base64 and JWT use an encoding API and for Caesar and substitution ciphers a cipher API.
api.oanor.com/morse-api
Roman Numeral API
Roman numeral conversion as an API, computed locally and deterministically. The encode endpoint turns an integer from 1 to 3999 into its Roman numeral using standard subtractive notation, so 1994 becomes MCMXCIV and 2024 becomes MMXXIV. The decode endpoint turns a Roman numeral back into an integer with strict validation — it rejects malformed forms such as IIII or VV and also returns the canonical way to write the same value, accepting any letter case. The arithmetic endpoint adds, subtracts or multiplies two values given as either integers or Roman numerals and returns the result as a Roman numeral and as an integer, provided the result stays within the classic 1–3999 range. The standard subtractive pairs are IV, IX, XL, XC, CD and CM. Everything is computed locally and deterministically, so it is instant and private. Ideal for typesetting, publishing, education, clock-face, game and document-processing app developers, numbering and chapter tools, and history teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Roman numeral conversion; for binary, octal and hexadecimal number-base conversion use a base-conversion API.
api.oanor.com/roman-api
MessagePack API
Encode and decode MessagePack — the compact binary serialization format ("it's like JSON, but fast and small") used by Redis, Fluentd, many RPC systems and IoT protocols. The encode endpoint turns a JSON value into MessagePack bytes, automatically choosing the smallest representation for each integer, string, array and map; the decode endpoint parses MessagePack back into a JSON value. It implements the full spec — nil, booleans, every fixed and variable integer width, float32 and float64, str and bin, arrays and maps, and the ext family — and rejects trailing or truncated data rather than silently mangling it. Binary (bin) values and any non-UTF-8 string come back losslessly as a {"_bytes_hex":"…"} object, and ext values as {"_ext":{"type":N,"hex":"…"}}, so encode and decode round-trip exactly. Bytes are exchanged as both hex and base64 so they survive any transport. Everything is computed locally and deterministically, so it is instant and private. Ideal for debugging MessagePack payloads, bridging JSON and msgpack systems, RPC and cache tooling, IoT pipelines, and teaching the format. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is MessagePack specifically; for JSON, YAML, TOML or XML use those format APIs, for BitTorrent's Bencode use the Bencode API, and for base64, hex, URL or HTML encoding use a general encoding API.
api.oanor.com/msgpack-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Data URI API?
What's the rate limit for Data URI API?
How much does Data URI API cost?
Can I cancel my subscription anytime?
Is Data URI API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/dataurl-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/dataurl-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/dataurl-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/dataurl-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.