SMS/LMS/MMS
Domestic text sending is made up of short messages (SMS), long messages (LMS), and long messages with images (MMS).
The body fields differ by message type, and you can check the fields, requests, and responses for each below.
Send an SMS (short message)
Use this for verification codes and short informational messages. It uses the messageFlow[].sms object, the body holds up to 90 bytes, and there is no title field.
Body Parameters
{}JSONdestinations
RequiredObject ArrayThe array of recipient information. Up to 200 entries per broadcast send request.
messageFlow
RequiredObject ArrayWhen you add more messages, they are automatically handled in order as Failover message.
paymentCode
StringThe department code used for settlement.
groupKey
StringThe key you set to group messages together and review their statistics in Message insight.
idempotencyKey
StringThe idempotency key field that identifies a request as idempotent.
idempotencyTtl
IntegerThe validity period of the idempotency key, in seconds.
ref
StringThe request-level reference field.
Returns
common
ObjectThe common response section.
data
ObjectThe service response section.
Request example
curl -X POST "https://mars.ibapi.kr/api/comm/v1/send/omni" \ -H "Authorization: {ApiKey}" \ -H "Content-Type: application/json" \ -d '{ "destinations": [{ "to": "01000000000" }], "messageFlow": [{ "sms": { "from": "01000000000", "text": "์ธ์ฆ๋ฒํธ๋ 123456 ์
๋๋ค." } }], "ref": "sms-20260330-001" }'Response example
{ "common": { "authCode": "A000", "authResult": "Success", "infobankTrId": "Infobank-Tracking-Id" }, "data": { "code": "A000", "result": "SUCCESS", "data": { "destinations": [{ "to": "01000000000", "msgKey": "20260424104234546POM101182450000", "code": "A000", "result": "Success" }] }, "ref": "sms-20260330-001" }}Send an LMS (long message)
Use this for long informational text messages. It uses the messageFlow[].mms object, and the body holds up to 2,000 bytes.
Body Parameters
{}JSONdestinations
RequiredObject ArrayThe array of recipient information. Up to 200 entries per broadcast send request.
messageFlow
RequiredObject ArrayWhen you add more messages, they are automatically handled in order as Failover message.
paymentCode
StringThe department code used for settlement.
groupKey
StringThe key you set to group messages together and review their statistics in Message insight.
idempotencyKey
StringThe idempotency key field that identifies a request as idempotent.
idempotencyTtl
IntegerThe validity period of the idempotency key, in seconds.
ref
StringThe request-level reference field.
Returns
common
ObjectThe common response section.
data
ObjectThe service response section.
Request example
curl -X POST "https://mars.ibapi.kr/api/comm/v1/send/omni" \ -H "Authorization: {ApiKey}" \ -H "Content-Type: application/json" \ -d '{ "destinations": [{ "to": "01000000000" }], "messageFlow": [{ "mms": { "from": "01000000000", "title": "์ฃผ๋ฌธ ์๋ด", "text": "์ฃผ๋ฌธ์ด ์ ์ ์ ์๋์์ต๋๋ค. ๋ฐฐ์ก์ ๋ด์ผ๋ถํฐ ์์๋ฉ๋๋ค." } }], "ref": "lms-20260330-001" }'Response example
{ "common": { "authCode": "A000", "authResult": "Success", "infobankTrId": "Infobank-Tracking-Id" }, "data": { "code": "A000", "result": "SUCCESS", "data": { "destinations": [{ "to": "01000000000", "msgKey": "20260424104234546POM101182450000", "code": "A000", "result": "Success" }] }, "ref": "lms-20260330-001" }}Send an MMS (image + long message)
Use this for sends that need an image attachment. messageFlow[].mms.fileKey is required, and the body holds up to 2,000 bytes.
Body Parameters
{}JSONdestinations
RequiredObject ArrayThe array of recipient information. Up to 200 entries per broadcast send request.
messageFlow
RequiredObject ArrayWhen you add more messages, they are automatically handled in order as Failover message.
paymentCode
StringThe department code used for settlement.
groupKey
StringThe key you set to group messages together and review their statistics in Message insight.
idempotencyKey
StringThe idempotency key field that identifies a request as idempotent.
idempotencyTtl
IntegerThe validity period of the idempotency key, in seconds.
ref
StringThe request-level reference field.
Returns
common
ObjectThe common response section.
data
ObjectThe service response section.
Request example
curl -X POST "https://mars.ibapi.kr/api/comm/v1/send/omni" \ -H "Authorization: {ApiKey}" \ -H "Content-Type: application/json" \ -d '{ "destinations": [{ "to": "01000000000" }], "messageFlow": [{ "mms": { "from": "01000000000", "title": "ํ๋ก๋ชจ์
์๋ด", "text": "์ฒจ๋ถ ์ด๋ฏธ์ง๋ฅผ ํ์ธํด ์ฃผ์ธ์.", "fileKey": ["FILE_KEY_001"] } }], "ref": "mms-20260330-001" }'Response example
{ "common": { "authCode": "A000", "authResult": "Success", "infobankTrId": "Infobank-Tracking-Id" }, "data": { "code": "A000", "result": "SUCCESS", "data": { "destinations": [{ "to": "01000000000", "msgKey": "20260424104234546POM101182450000", "code": "A000", "result": "Success" }] }, "ref": "mms-20260330-001" }}Reservation send
Registers an SMS/LMS/MMS message to be sent at a time you specify. resvSendTime is required. After you register a reservation, you can look it up, update, cancel, stop, or resume it, and manage its recipients on the Reservation management page.
Body Parameters
{}JSONdestinations
RequiredObject ArrayThe array of recipient information. Up to 200 entries per broadcast send request.
messageFlow
RequiredObject ArrayWhen you add more messages, they are automatically handled in order as Failover message.
resvSendTime
RequiredStringThe reservation send time.
resvName
StringThe reservation name.
paymentCode
StringThe department code used for settlement.
ref
StringThe request-level reference field.
Returns
common
ObjectThe common response section.
data
ObjectThe reservation registration response section.
Request example
curl -X POST "https://mars.ibapi.kr/api/comm/v1/reservation" \ -H "Authorization: {ApiKey}" \ -H "Content-Type: application/json" \ -d '{ "destinations": [{ "to": "01000000000" }], "messageFlow": [ { "sms": { "from": "01000000000", "text": "์์ฝ SMS ๋ฐ์ก ํ
์คํธ์
๋๋ค." } }, { "mms": { "from": "01000000000", "title": "์์ฝ MMS ์๋ด", "text": "์์ฝ MMS ๋ฐ์ก ํ
์คํธ์
๋๋ค.", "fileKey": ["FILE_KEY_001"] } } ], "resvSendTime": "2026-05-01 10:00:00", "resvName": "๋ฌธ์ ์์ฝ ๋ฐ์ก", "ref": "mt-resv-20260501-001" }'Response example
{ "common": { "authCode": "A000", "authResult": "Success", "infobankTrId": "Infobank-Tracking-Id" }, "data": { "code": "A000", "result": "Success", "resvKey": "MO20260501100000abcdef", "data": { "destinations": [{ "to": "01000000000", "msgKey": "20260424104234546POM101182450000", "code": "A000", "result": "Success" }] }, "ref": "mt-resv-20260501-001" }}Upload an image
Upload an image for an MMS send and use the issued fileKey in the message body (messageFlow[].mms.fileKey). You can set up to 3 fileKey values, and the image order is not guaranteed because it depends on the carrier environment.
Body Parameters
FORM-DATAfile
RequiredBinaryThe binary of the image file to upload.
fileKey
StringThe key that identifies the uploaded file. If you omit it, the server generates one.
imageName
StringThe name of the uploaded file. If you omit it, the file name without its extension is used.
Returns
common
ObjectThe common response section.
data
ObjectThe service response section.
Request example
curl -X POST "https://mars.ibapi.kr/api/comm/v1/file/mms" \ -H "Accept: application/json" \ -H "Authorization: {ApiKey}" \ -H "Content-Type: multipart/form-data" \ -F "file=@/path/to/image.jpg"Response example
{ "common": { "authCode":"A000", "authResult":"Success", "infobankTrId":"header-value-X-Infobank-Tracking-Id" }, "data": { "code":"A000", "result":"Success", "data": { "fileKey":"clientId_7ecbac8b4e204acc8c67d4d76e120183", "expired":"2027-04-24T10:45:24+09:00" } }}