Morse to text
API · /morse-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 health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 82 ms
- Server probes · 24h
- Subscribers
- 3,080
- active
- Total calls
- 32
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 5,500 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 5,500 calls/month
- 2 req/sec
- Encode + decode + timing
- No credit card
Starter
€5.00 /month
- 46,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 46,000 calls/month
- 6 req/sec
- Punctuation, PARIS timing
- Email support
Pro
€12.00 /month
- 235,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 235,000 calls/month
- 15 req/sec
- CW-training & signalling pipelines
- Priority support
Mega
€38.00 /month
- 1,300,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,300,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Cipher API
Encode and decode classical ciphers and alphabets as an API — Morse code, ROT13, the Caesar shift (with any shift 1-25), Atbash, the NATO phonetic alphabet, leetspeak, A1Z26 (letters to numbers) and string reversal. Send text and a cipher and get the transformed string back, or decode it again — most are perfectly reversible. Everything runs locally, so it is fast and always available. Ideal for puzzle and escape-room games, ARGs, treasure hunts, education and coding lessons, retro and hacker-themed UIs, and chat bots. For base64/hex/URL encodings use the Encoding API; for cryptographic hashes use the Hash API.
api.oanor.com/cipher-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
Base45 API
Encode and decode Base45 (RFC 9285) — the compact binary-to-text encoding designed to pack densely into the alphanumeric mode of QR codes, best known as the carrier for the EU Digital COVID Certificate. The encode endpoint turns text (UTF-8) or raw bytes given as hex into a Base45 string; the decode endpoint turns a Base45 string back into bytes, returned as hex and — when the bytes are valid UTF-8 — as text. It uses the official 45-character alphabet (0-9, A-Z and a handful of symbols), packs two bytes into three characters (or one byte into two), and validates length and value ranges strictly so malformed input is rejected rather than silently mangled. Everything is computed locally and deterministically, so it is instant and private. Ideal for QR-code payloads, digital health and travel certificates, alphanumeric-mode encoders, and any binary data that must survive an uppercase-only channel. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is Base45 specifically; for base64, base32, hex, URL or HTML entity encoding use a general encoding API.
api.oanor.com/base45-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Morse Code API?
What's the rate limit for Morse Code API?
How much does Morse Code API cost?
Can I cancel my subscription anytime?
Is Morse Code 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/morse-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/morse-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/morse-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/morse-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.