SMS/LMS/MMS
This guide covers sending text messages — short (SMS), long (LMS), and image (MMS) — to an individual or a group.

SMS/LMS/MMS types
The API needs the type specified
When you send through the API, specify an sms or mms object in messageFlow yourself. Send long messages (LMS) over 90 bytes with the mms object too; attaching an image with fileKey sends it as MMS. Automatic switching based on content length and images applies only to web send in the console.
| Type | Maximum length | Image | Main use |
|---|---|---|---|
| SMS | 90 bytes | Not supported | Verification codes, short notices |
| LMS | 2,000 bytes | Not supported | Long announcements, detailed notices |
| MMS | 2,000 bytes | Supported | Messages that include an image |
One Korean character counts as 2 bytes, and one letter or digit counts as 1 byte.
When do you use each one?
| Situation | Recommended type |
|---|---|
| Verification codes, simple alerts | SMS |
| Order details, long notices | LMS |
| Marketing with images or banners | MMS |
| Failover where Kakao or RCS is not supported | SMS or LMS |
| Sending to overseas recipients | International SMS (see below) |
Check the send structure before you integrate
Once you understand the destinations and messageFlow structure, you can handle it the same way no matter which integration method you use.
Check the destinations, messageFlow, and failover structure on a single page.
How will you integrate?
Now that you understand the structure, choose your integration method below.