26.04.30 April API update monthly summary

Summary

SMO integration was added, and message delivery, settlement, and template management were strengthened.

At a glance

• SMO integration is now available (supports the MO receive flow)
• paymentCode added to Brand Message broadcast (F) sending
• A change history lookup API for Alimtalk / Brand Message templates

What changed?

1. SMO integration (MO receive support)

SMO integration, which forwards MO (inbound messages) to your system, has been added.

The message flow is GW → Omni API → your MO webhook server, so you receive user replies in real time. That takes you beyond one-way sending into two-way communication.

2. paymentCode on Brand Message broadcast (F) sending

A paymentCode field was added to Brand Message broadcast (F) sending, which makes per-send billing and settlement management possible.

Being able to classify and trace message cost raises settlement and report accuracy.

3. A recent template change history API

A new API returns the recent change history for Alimtalk and Brand Message templates.

Being able to see template edit history makes change tracking and management easier during operations.

Why it matters

• SMO integration lets you receive user replies in real time, which takes you beyond one-way messaging into two-way communication.
• paymentCode lets you classify and settle message cost accurately, which raises operational and accounting efficiency.
• The template change history API lets you trace template edits, which strengthens operational stability and management transparency.

How to use it

• To handle MO messages, set up a webhook server and implement receive logic that matches the SMO integration flow.
• Use paymentCode to separate cost by message type, and settlement and report analysis become easier.
• We recommend using the template change history API to build a management practice that records and traces changes during operations.

Things to note

• SMO integration requires a webhook server with good availability and response times.
• MO messages may not arrive, depending on channel policy and whether the user replies.
• Manage paymentCode values with a consistent policy of your own so settlement stays accurate.
• Some template change history data may be limited after a certain period.