[26.03.31] March API update monthly summary

Summary

The RCS Biz Center API opened, message automation and template handling expanded, and delivery and report stability improved.

At a glance

• RCS Biz Center API is now available
• A template variable lookup API for Make / Zapier integration
• Improved Omni-polling report timeouts
• Automatic variable substitution for basic Alimtalk / Brand Message templates
• XMS (unified SMS/LMS/MMS) automatic substitution sending
• Brand Message F type sending support

What changed?

1. RCS Biz Center API is open

A new Biz Center API for running RCS message.

Key features

• Brand management (with agency support)
• Template management
• Chatroom management

This lets you automate RCS channel operations through the API.

2. A template variable lookup API for Make / Zapier integration

A new API returns the list of template variables you need
when integrating with message automation tools such as Make and Zapier.

• Makes variable mapping easier when building automation scenarios
• Strengthens support for no-code and low-code message operations

3. Improved Omni-polling report timeouts

The intermittent timeouts that occurred when fetching reports over polling
have been improved.

• Better stability on large lookups
• Higher success rate for receiving results under network delay

4. Automatic template substitution (Alimtalk / Brand Message)

Automatic substitution now applies to basic templates.

• Template variables are substituted automatically, with no preprocessing on your side

5. XMS (unified SMS/LMS/MMS handling)

XMS automatically sends in the optimal format
for the message type (SMS/LMS/MMS).

• Converts automatically based on message length and content
• Simplifies channel branching logic during development

6. Brand Message F type sending

Brand Message now supports F type sending,
which widens your choice of message types.

Why it matters (one line each)

• The RCS Biz Center API moves channel operations from the UI to the API, which raises automation and scalability considerably.
• The template variable lookup API makes integration with automation tools like Make and Zapier easy, which accelerates message operations automation.
• Better polling timeouts reduce failures on large report lookups, which makes data collection reliable.
• Automatic template substitution lets you compose messages with no substitution logic of your own, which lowers development complexity.
• XMS optimizes the message type automatically, raising both send efficiency and developer convenience.
• Brand Message F type support lets you use a wider range of message types, which extends your marketing expressiveness and reach.

How to use it

• RCS extends the existing message API with the same structure; we recommend managing it at the brand, template, and chatroom level.
• In an automation setup, use the template variable lookup API to map variables in advance and operations get more efficient.
• With XMS you can handle sending in a single code path, with no branching on message type.

Things to note

• What RCS actually looks like on arrival can differ depending on channel and handset support.
• XMS automatic conversion works from message length and content, so a message can go out as a different type than you expected.
• Polling is more stable on large volumes now, but excessive calls can still hit the RateLimit.