Translate plain text to Morse code and decode Morse code back to text.
Morse Code converts plain text to Morse code dots and dashes and translates Morse back into text. It provides character counts, dit and dah totals, and validation status, while paid plans add downloadable audio tones.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"text": "This Is A Message",
"morse": "- .... .. ... / .. ... / .- / -- . ... ... .- --. . ",
"stats": {
"characters": 17,
"dits": 25,
"dahs": 7
},
"valid": true,
"audio": {
"audioFile": "a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav",
"format": ".wav",
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/morsecode/a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1765925804&Signature=TiktgUsHV0ipCaRwNNiEihtD5e1SacBHBwWLGvsrnLJTkH%2BH5fRsII5hxk7nEqTypya05Dg4BHTxu672tRU%2Bhb3F8g%2BQYL7u3PMaCHzcnrrpcjSh0hH7%2BWVfEyHxPf5cCuKliISePCOlpbVsU8xtFL8p1DfgTV2FeD8Rmwo3SVpCG4LHpYXJWoZVET2IbS4dZS%2Brn9kvnoBvApgDJgc5EEufOZHYLba6278g0HTgQaOIhdSNhpeSpCwPuSw6q3eK%2FGqzhD5PtzTBMPN1hMvXIZPX11EYRG%2FLbqvltu6gVgbYL5khcG5zQbDse2vXphAys8fMq7PiZSGe1ODf63Gakw%3D%3D",
"duration": "13.20s",
"frequency": "600Hz",
"sampleRate": "8000Hz",
"expires": 1765925804517
}
}
}
About the Morse Code API
Send text to receive dot-and-dash sequences separated by spaces and slashes, along with total counts of dits, dahs, and characters. Decoding parses Morse strings back into text and isolates any unrecognized symbols. Paid plans can generate downloadable audio tone files with duration, frequency, and sample rate metadata.
What people use it for
- Ham Radio Training
- Amateur radio training apps convert practice call signs and sentences into Morse strings to help students verify their manual keying.
- Escape Room Puzzles
- Game designers translate clue strings into dot-and-dash puzzles and count character lengths to calibrate challenge difficulty for players.
- Assistive Communication Tools
- Decode user input from single-switch sip-and-puff hardware into text while flagging invalid or unrecognized signal sequences immediately.
- STEM Classroom Demonstrations
- When teaching telecommunications history, physics teachers translate student messages into Morse code sequences to display exact dit and dah counts.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Morse Code
Same data, same APIVerve account, same credit balance — one key works on all of them.
How many Morse code translations does the Free plan cover?
Can I generate Morse code audio files on the Free plan?
Does the API support two-way translation between text and Morse code?
What format does the generated Morse code string use?
How can I tell if submitted Morse code is valid?
Request parameters — POST /v1/morsecode
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
textRequired | string | hello world | The text to encode or decode in Morse code |
Optional
| Parameter | Type | Example | Description |
|---|---|---|---|
audioOptionalPremium | boolean | Set to true to include an audio file of the Morse code default false |
curl -X POST "https://api.apiverve.com/v1/morsecode" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"This Is A Message","audio":true}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/morsecode
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"text": "This Is A Message",
"morse": "- .... .. ... / .. ... / .- / -- . ... ... .- --. . ",
"stats": {
"characters": 17,
"dits": 25,
"dahs": 7
},
"valid": true,
"audio": {
"audioFile": "a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav",
"format": ".wav",
"downloadURL": "https://storage.googleapis.com/apiverve/APIData/morsecode/a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav?GoogleAccessId=635500398038-compute%40developer.gserviceaccount.com&Expires=1765925804&Signature=TiktgUsHV0ipCaRwNNiEihtD5e1SacBHBwWLGvsrnLJTkH%2BH5fRsII5hxk7nEqTypya05Dg4BHTxu672tRU%2Bhb3F8g%2BQYL7u3PMaCHzcnrrpcjSh0hH7%2BWVfEyHxPf5cCuKliISePCOlpbVsU8xtFL8p1DfgTV2FeD8Rmwo3SVpCG4LHpYXJWoZVET2IbS4dZS%2Brn9kvnoBvApgDJgc5EEufOZHYLba6278g0HTgQaOIhdSNhpeSpCwPuSw6q3eK%2FGqzhD5PtzTBMPN1hMvXIZPX11EYRG%2FLbqvltu6gVgbYL5khcG5zQbDse2vXphAys8fMq7PiZSGe1ODf63Gakw%3D%3D",
"duration": "13.20s",
"frequency": "600Hz",
"sampleRate": "8000Hz",
"expires": 1765925804517
}
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
text | string | "This Is A Message" | Original input text converted to Morse code |
morse | string | "- .... .. ... / .. ... / .- / -- . ... ... .- --. . " | Encoded Morse code representation with spaces and slashes |
stats | object | {...} | Statistics about the Morse code encoding |
characters | number | 17 | Total number of characters in original text |
dits | number | 25 | Total count of dits (dots) in Morse code |
dahs | number | 7 | Total count of dahs (dashes) in Morse code |
valid | boolean | true | Whether the Morse code is valid and properly formatted |
audioPremium | object | {...} | Audio file information including URL and metadata |
audioFilePremium | string | "a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav" | Unique identifier for the generated audio file |
formatPremium | string | ".wav" | Audio file format (e.g., .wav, .mp3) |
downloadURLPremium | string | "https://storage.googleapis.com/apiverve/APIData/morsecode/a11f9d7f-1fd2-4b10-86de-82defaf18c57.wav?GoogleAccessId=635500398038-compute%40de… | Signed URL to download the generated audio file |
durationPremium | string | "13.20s" | Duration of the audio file in seconds |
frequencyPremium | string | "600Hz" | Frequency of the Morse code tone in Hz |
sampleRatePremium | string | "8000Hz" | Sample rate of the audio file in Hz |
expiresPremium | number | 1765925804517 | Unix timestamp when the audio download URL expires |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Morse Code calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/morsecode
No SDK to install — this is a plain HTTPS call to /v1/morsecode with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/morsecode" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/morsecode
Install the Node.js SDK, then call the Morse Code API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/morsecodeconst res = await fetch("https://api.apiverve.com/v1/morsecode", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/morsecode
No SDK to install — this is a plain HTTPS call to /v1/morsecode with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/morsecode",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/morsecode
Install the C# / .NET SDK, then call the Morse Code API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.MorseCodeusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/morsecode");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/morsecode
No SDK to install — this is a plain HTTPS call to /v1/morsecode with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/morsecode", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/morsecode
No SDK to install — this is a plain HTTPS call to /v1/morsecode with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/morsecode");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/morsecode
No SDK to install — this is a plain HTTPS call to /v1/morsecode with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/morsecode")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Morse Code form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Morse Code API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Morse Code API.
Data Processing
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read