Every stack has its own Hangul romanizer — a Python package, a PHP class, a JavaScript module, a .NET library — which means a separate dependency to vet and maintain in each service. This API does the same Revised Romanization (RR) over plain HTTP, so any language calls the identical implementation with one GET.
Revised Romanization (RR) is South Korea's official system for writing Korean in the Latin alphabet (서울 → Seoul, 김치 → gimchi). It is what you want for English-facing UIs, search slugs, transliterated place and menu names, and travel content. This endpoint maps each Hangul syllable per the 국립국어원 (National Institute of Korean Language) RR table and returns the romanized string.
| GET | /v1/romanize?text=서울 |
Revised Romanization (RR) of any Korean (Hangul) text. Non-Hangul characters pass through unchanged. |
curl "https://korea-calendar-api.kunstudio.workers.dev/v1/romanize?text=%EB%B9%84%EB%B9%94%EB%B0%A5"{
"input": "비빔밥",
"romanized": "bibimbap",
"system": "Revised Romanization (RR). Per-syllable mapping; full inter-syllable assimilation is partial in v1."
}No API key is needed on the origin to try this — it is rate-limited for fair evaluation. See the OpenAPI spec for the full schema.
seoul, 김치 → gimchi, 부산 → busan, 안녕하세요 → annyeonghaseyo.osi) is only partially applied, so this is best for names, places, menu items and slugs rather than full sentence phonetic transcription.text query parameter (Hangul is multi-byte UTF-8). Any non-Hangul characters — spaces, Latin letters, punctuation, digits — pass through unchanged.Building a Korean fortune (사주/saju) app? Pair this with the KunStudio Saju API for a full four-pillars reading over REST.