Western Union phonetic alphabet
Spells SOS as Sugar Ocean Sugar using the classic Western Union telegraph table, from Adams for A to Zero for Z, and turns a string of code words back into letters and digits. Unknown words are named, not guessed. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- SOS
- Result
- Sugar Ocean Sugar
- Calculation mode
- Encode
- Quantity
- 3
- Alphabet
- western_union
The Western Union phonetic alphabet is the classic North American telegraph and telephone spelling table that maps every Latin letter to a distinctive place or personal name so wire operators, switchboard staff, and later radio users could read serial numbers, names, and short messages without letter-for-letter confusion. Adams stands for A, Boston for B, Chicago for C, and the rest of the list—Denver, Easy, Frank, George, Henry, Ida, John, King, Lincoln, Mary, New York, Ocean, Peter, Queen, Roger, Sugar, Thomas, Union, Victor, William, X-ray, Young, Zero—was drilled into commercial and military voice circuits long before the NATO Alpha Bravo Charlie standard took over aviation. This capability spells plain text into those Western Union code words or decodes a paste of code words back into letters and digits, with a simple encode or decode mode and a hard error that reports any unknown word by name.
Spell text with Western Union code words (encode mode)
Each Latin letter A through Z maps to its classic Western Union code word—Adams for A, Boston for B, Chicago for C, Denver for D, Easy for E, Frank for F, George for G, Henry for H, Ida for I, John for J, King for K, Lincoln for L, Mary for M, New-York for N, Ocean for O, Peter for P, Queen for Q, Roger for R, Sugar for S, Thomas for T, Union for U, Victor for V, William for W, X-ray for X, Young for Y, and Zero for Z—using the historical telegraph spellings with hyphens kept on multi-part words so tokenization stays stable.
Digits zero through nine map to Naught, One, Two, Three, Four, Five, Six, Seven, Eight, and Nine; digit zero uses Naught rather than Zero so it never collides with letter Z on a round-trip. Whitespace in the input separates word groups: letters inside a group are joined with single spaces, and groups are joined with a slash surrounded by spaces so Hi there becomes Henry Ida slash Thomas Henry Easy Roger Easy. Empty text with no letters or digits also fails validation.
Identical inputs always produce identical outputs because the path is pure table lookup with no network, no random salt, and no wall clock. Use encode whenever you need a paste-ready Western Union spelling for a historical reenactment, genealogy telegram, museum label, training sheet, or short identifier that must be read aloud in the pre-NATO style.
Decode code words and report unknown words
Set mode to decode and put a sequence of Western Union telegraph code words in text, separated by spaces. Optional slash markers between groups are ignored so you can round-trip the encode output without stripping separators by hand. Matching is case-insensitive and treats hyphens, underscores, and internal spaces as equivalent, so New-York, new york, and NewYork all decode to N, and X-ray, xray, and X Ray all decode to X.
Canonical letter words and digit words resolve to uppercase letters and digit characters; common Western Union-era alternates such as Edward for Easy, Robert for Roger, Nought or Oh for Naught, and Zero for Z are accepted so real-world pastes from old manuals still work. Empty decode input fails the same way. Prefer this capability when search intent is Western Union phonetic alphabet, Adams Boston Chicago converter, telegraph spelling alphabet, or historical US voice spelling; modern aviation Alpha Bravo Charlie work belongs to the separate NATO phonetic tools.
Where the telegraph spelling still helps
Call the free in-browser Western Union phonetic alphabet tool for museum demos, genealogy projects that reconstruct old wire messages, amateur radio nostalgia nights, classroom history of telecommunications, and one-off spell-checks of short identifiers without installing a spreadsheet of code words. A typical workflow encodes a short booking reference in Western Union style for an agent to read over the phone, pastes the spoken words into a ticket, then decodes on the receiving system and asserts that result matches the original letters.
Another workflow decodes student answers in a telegraph-history quiz and fails loud on unknown code words so instructors see the exact typo. Authors shipping SDKs can map the tokens array into a table of character and code columns for UI copy buttons, while mode and alphabet labels make OpenAPI examples self-explanatory for readers comparing Western Union and NATO radio spelling styles.
What you can do with it
Historical telegraph and museum demos
Educators and museum kiosks spell visitor names as Adams Boston Chicago so guests hear the classic Western Union table, then decode the code words to verify the original letters.
Help desk with pre-NATO spelling style
Agents who prefer the older US telephone table spell serial numbers over the phone and decode customer read-backs, failing loud on unknown code words before closing the ticket.
FAQ
How do I spell text with the Western Union phonetic alphabet?
The result field returns Sugar Ocean Sugar with a tokens list for each character.
How do I decode Adams Boston Chicago back to letters?
Set mode to decode and put space-separated Western Union code words in text. The result field returns the recovered uppercase letters and digits.
How is this different from the NATO phonetic alphabet?
Western Union uses Adams, Boston, Chicago and other historical US telegraph words. NATO/ICAO uses Alpha, Bravo, Charlie. They are different tables and different search intents; use the matching capability for each.
Why is the digit 0 spelled Naught instead of Zero?
Because Zero is already the code word for the letter Z. Digits use Naught, One, Two and so on up to Nine, so a spelled serial number decodes back without mixing up the digit 0 and the letter Z.
What happens with spaces and punctuation?
Each space starts a new word group: letters inside a group are joined by spaces and groups are separated by a slash, so “Hi there” becomes Henry Ida / Thomas Henry Easy Roger Easy. Punctuation is refused, and the tool names the character and its position.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/enc/western-union-phonetic \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"SOS"}'const res = await fetch("https://api.kit.forhosting.com/enc/western-union-phonetic", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "SOS"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/enc/western-union-phonetic",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "SOS"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/enc/western-union-phonetic", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"SOS"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"SOS"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/enc/western-union-phonetic", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "SOS"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "enc.western_union_phonetic",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The algorithm is a fixed deterministic table: no model, no network, and no clock, so the same input always yields the same JSON for tests and SDKs.
Spell text with Western Union code words (encode mode)
Send a JSON body with the required string field text set to the letters and digits you want to spell, and leave mode at its default encode or set mode to encode explicitly. Characters outside letters, digits, and whitespace raise invalid_input with the offending character and index, so punctuation does not silently drop out of a ticket or call-sign check. Aliases input, value, and s are accepted for the text field; direction, op, and action may stand in for mode. The response includes result as the spelled phrase, tokens as an array of char and code pairs, count as the number of mapped characters, mode equal to encode, and alphabet equal to western_union.
Decode code words and report unknown words
Any token that is not a known code word raises invalid_input with an explicit unknown code word message that names the bad token—exactly the contract training tools and radio-check pipelines need when a typo would otherwise invent a wrong letter. That is how this capability reports unknown words: they surface in the error payload instead of being skipped. On success the response returns result as the recovered string, tokens pairing each resolved character with its canonical code word, count, mode decode, and alphabet western_union. Validation failures are not charged on the prepaid API, so operators can probe bad pastes safely.
API usage, pricing, workflows, and practical limits
Use the prepaid KIT API when a support backend, education quiz, logistics label printer, or SDK needs the same encode or decode step under balance at $0.002 per successful item; failed validation never consumes balance after the engine rejects the request. Pair this endpoint with uppercase or transliteration tools when identifiers arrive in mixed scripts, but keep the steps separate so each landing page matches a single search intent.
Integration use cases
CI fixtures for identifier pipelines
Services that generate spoken identifiers in Western Union style pin encode and decode goldens—including an unknown-word error—so table drift is caught in continuous integration.
Technical questions
What happens on an unknown code word?
Decode raises invalid_input naming the unknown code word so the bad token is reported explicitly. Validation failures are not charged on the prepaid API.
Is the Western Union phonetic alphabet tool free?
The browser widget runs free on your device. API calls use prepaid KIT balance at $0.002 per successful item.