Transform - Encoding

Free Morse Code Decode API Endpoint

The free Morse code decode API endpoint turns dots and dashes back into text in upper case. It reads the look-alikes people type, such as a middle dot or a long dash, and lists every sequence it cannot read instead of guessing.

  • No API key
  • International Morse
  • GET or POST
  • Lists what it cannot read

Morse to text

GET/morse_decode/{code}

POST/morse_decode

https://aisenseapi.com/services/v1/morse_decode

Call the free Morse code decode API endpoint

Put the code in the path with * for each dot and %20 for a space, since a path cannot hold two dots in a row:

curl https://aisenseapi.com/services/v1/morse_decode/***%20---%20***
{"morse_decoded_data":"SOS","unknown":[]}

Or post it:

curl -X POST https://aisenseapi.com/services/v1/morse_decode \
  -H "Content-Type: application/json" \
  -d '{"data": ".... . .-.. .-.. --- / .-- --- .-. .-.. -.."}'
{"morse_decoded_data":"HELLO WORLD","unknown":[]}

The other way is the Morse encode API endpoint.

Try it

Decode text here. Your browser sends it in a JSON body, as the quick start does. Leave secrets and personal data out.

Rules

  • One space between letters. Between words a slash, a |, a line break or two or more spaces. In a URL a | needs no escape, while a slash is written %2F.
  • Dots and dashes may be typed as . and - or as their look-alikes: the middle dot, the bullet and * for a dot, and the en dash, the em dash, the minus sign and the underscore for a dash.
  • The text comes back in upper case, since Morse has no case. A code that two letters share comes back as Æ, Ø or Å.
  • unknown lists each sequence that is not a character once, at most 32 of them, and the text goes on without it.
  • GET /morse_decode/{code} takes the code as one path segment. The server turns away a path with two dots in a row, so write each dot there as *. POST /morse_decode takes {"data": "..."} with Content-Type: application/json, or the code as the raw body. At most 512 KiB.
curl -X POST https://aisenseapi.com/services/v1/morse_decode \
  -H "Content-Type: application/json" \
  -d '{"data": ".- ........ -..."}'
{"morse_decoded_data":"AB","unknown":["........"]}

Errors

StatuserrorWhen
400No Morse code to decode.No code in the path, no data string and no body
413Morse code over 512 KiB.More than 512 KiB of code in one request
400The data is not UTF-8 text.Bytes that are not UTF-8
400No sequence in the code is Morse for a character.Nothing could be read; unknown lists what was sent

Each refusal also carries fix, a sentence saying what to send instead.

Common uses

Check what was keyed

Read back the dots and dashes a learner or a program wrote, and see at once which letters did not come through.

Read a written message

Turn code copied from a puzzle, a note or a recording transcript into text.

Agents

Through the MCP server the same decoder is encode_data with the format morse and the operation decode.

Privacy and limits

Nothing is stored. The Morse decode answer is worked out while the request is open and the text is gone with it. The access log records the path and the status. A text sent in the path is part of that path, so post it when it should not be logged.

The base URL is https://aisenseapi.com/services/v1. There is no key, no account and no sign-up step. An encode takes at most 64 KiB of text and a decode at most 512 KiB of code, and the service-wide limit is 5000 requests per IP address per day. Every endpoint in the collection is listed on the Free public REST APIs reference, and the encodings side by side on Encoding APIs.