Send SMS to South Korea
from $0.0450/msg

smsroute.cc is a crypto-only A2P SMS gateway covering 149 countries, including South Korea. Send SMS to 68 million subscribers across SK Telecom, KT Corporation, LG Uplus, and SK Broadband at $0.0450 per message, 41% cheaper than Twilio. Median delivery latency is 68 ms, 99.3% first-attempt success, and direct operator interconnect. Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. no phone binding, no national ID upload, no company registryuments at signup. Minimum $5 top-up.

Why Korean Hangul SMS Segments Cut Your South Korea Character Budget in Half

South Korea's mobile network supports two character encodings: GSM-7 and UCS-2. When you send an SMS containing only ASCII or Latin characters, the message uses GSM-7 encoding, which packs 160 characters into one segment. However, the moment your message includes even a single Korean character (Hangul), the entire SMS switches to UCS-2 encoding, which compresses the segment size to 70 characters. This means a typical Korean marketing message—for example, "안녕하세요! 새로운 상품을 소개합니다"—will consume two segments instead of one, doubling your per-message cost.

For businesses targeting South Korean consumers with Hangul text, this encoding overhead is non-negotiable. If your campaign sends 10,000 messages in Korean, budget for roughly 20,000 segments at the segment rate. smsroute.cc's $0.0450 per-segment pricing reflects this reality: each SMS to South Korea is metered by segment, not by message. A 140-character Hangul text requires two segments and costs $0.09. Plan accordingly, and consider whether shorter, more frequent messages (70 characters of Hangul per SMS) or English-language campaigns (160 characters per SMS) better fit your budget.

The encoding distinction is critical because South Korea's mobile infrastructure (SK Telecom, KT Corporation, LG Uplus) enforces segment-based billing at the carrier level. Our routing automatically detects the character set and applies the correct segment boundary. Multi-segment messages are charged individually: no bulk discounts, no segment bundling. Transparency on this point saves money and prevents billing surprises.

Mobile Operators in South Korea

SK Telecom holds 37% market share and is South Korea's largest operator. SK Telecom's network spans Seoul, Busan, Daegu, and provincial regions. They maintain strict T-flow enforcement and require sender ID pre-registration (1–2 business days). Our direct interconnect with SK Telecom ensures sub-100 ms latency on most messages.

KT Corporation accounts for 30% market share and operates nationwide, with strong urban coverage. KT requires equivalent sender ID registration and honors opt-out preferences immediately upon receipt. KT's routing is lowest-cost per segment on our platform, but no carrier preference is visible to end users—all messages are routed simultaneously.

LG Uplus controls 25% market share and serves a demographic skewed toward younger subscribers and business users. LG Uplus enforces the same quiet hours and consent framework. Pre-registration takes 1–2 business days and must include a valid business license or enterprise tax ID.

SK Broadband MVNO holds 8% market share and operates as a mobile virtual network operator (MVNO) using SK Telecom's infrastructure. SK Broadband subscribers are routed via SK Telecom's network; sender ID registration is handled through SK Telecom's system.

All four operators are directly integrated into smsroute.cc's routing mesh. Outbound SMS to any South Korean number is sent simultaneously to all carriers; the first to accept the message confirms delivery. This "first-accept" model minimizes latency (68 ms median) and maximizes delivery success (99.3%).

Pricing vs. Competitors

smsroute.cc's price per SMS to South Korea is $0.0450, making it the lowest-cost operator-direct route in the market. Below is a comparison with six leading competitors:

smsroute.cc's pricing reflects direct operator interconnection (no middleman markup), competitive routing, and high-volume efficiency. All prices above are per SMS segment; multi-segment Hangul messages cost proportionally more. smsroute.cc's 99.3% delivery success means fewer retries and lower effective cost. Competitors may offer volume discounts or tiered pricing; smsroute.cc offers a flat per-segment rate with no KYC friction, allowing you to scale without account review or approval delays.

How to Send SMS to South Korea in 3 Steps

Step 1: Create a free smsroute.cc account. Visit https://smsroute.cc and sign up. No phone verification, no ID upload, no corporate documents required. You will receive API credentials (API key and REST endpoint URL, or SMPP connection details) within seconds.

Step 2: Top up your account with cryptocurrency. Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5. Your balance is available immediately and does not expire. No credit card, no SEPA transfer, no bank account link required.

Step 3: Send SMS to E.164-formatted South Korean numbers. Use the smsroute.cc API to send to +82 1X XXXX XXXX (where 1X is the 10, 11, or 16 prefix and XXXX XXXX is the 8-digit subscriber number). Include your pre-registered numeric sender ID (1688–1699 range) or enterprise ID. Confirm that your recipient has given explicit consent for marketing SMS. Delivery reports are returned in 68 ms (median) to 88 ms (95th percentile).

REST API Example (cURL):

Python Example:

Both examples send a transactional SMS to a South Korean mobile number. Transactional messages (account confirmations, password resets, delivery updates) do not require explicit prior consent if the recipient has an existing business relationship with your organization. For marketing SMS, ensure that the recipient's phone number is accompanied by documented consent in your records. smsroute.cc logs delivery status and provides webhooks for opt-out callbacks; it is your responsibility to honor those opt-outs.

curl -X POST https://api.smsroute.cc/send \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to": "+821012345678",
    "from": "1688",
    "text": "Your verification code is 123456",
    "route": "south-korea"
  }'

import requests

api_key = "YOUR_API_KEY"
headers = {
    "Authorization": f"Bearer {api_key}",
    "Content-Type": "application/json"
}

payload = {
    "to": "+821012345678",
    "from": "1688",
    "text": "Your verification code is 123456",
    "route": "south-korea"
}

response = requests.post(
    "https://api.smsroute.cc/send",
    headers=headers,
    json=payload
)

print(response.json())

import fetch from "node-fetch";

const apiKey = process.env.SMSROUTE_API_KEY;

const res = await fetch("https://api.smsroute.cc/messages", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${apiKey}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    to: "+825551234567",
    from: "smsroute",
    text: "Your verification code is 384921",
  }),
});

console.log(await res.json());

<?php
$apiKey = getenv('SMSROUTE_API_KEY');

$payload = json_encode([
    'to'   => '+825551234567',
    'from' => 'smsroute',
    'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);

$ch = curl_init('https://api.smsroute.cc/messages');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: Bearer ' . $apiKey,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => $payload,
]);

echo curl_exec($ch);
curl_close($ch);

package main

import (
    "bytes"
    "encoding/json"
    "fmt"
    "io"
    "net/http"
    "os"
)

func main() {
    payload, _ := json.Marshal(map[string]string{
        "to":   "+825551234567",
        "from": "smsroute",
        "text": "Your verification code is 384921",
    })

    req, _ := http.NewRequest("POST",
        "https://api.smsroute.cc/messages",
        bytes.NewBuffer(payload))
    req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
    req.Header.Set("Content-Type", "application/json")

    resp, err := http.DefaultClient.Do(req)
    if err != nil { panic(err) }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}