[26.01.31] January API update monthly summary

At a glance

• New clientSubId field for international message
• Support for managing multiple Sender IDs / message signatures
• Extended signature support for overseas carrier policies
• Fixed the RateLimit control bug for customers using ApiKey authentication

What changed?

1. Extended signature support for international message

A new clientSubId field lets you manage several Sender IDs and message signatures
for international message.

New field

What is a Sender ID?

A Sender ID is the sender information shown in the
"from" area on the recipient's handset.

• Some countries and carriers allow a text Sender ID (Korea, MyService) as well as digits (15882460).
• Some countries require a company or service to register its own Sender ID in advance, to prevent spam and impersonation.
• Common examples: Indonesia, India, the Philippines, Thailand
• Sender ID registration usually takes 2~4 weeks.

What is a message signature?

Some countries require a string identifying the sender (company or service name) to be inserted in the message body
when sending overseas.

• This is called a message signature, and it must be registered in advance.
• Common example: China
• Example form:
  TEXT

  Copy

  【INFO中国】메시지 내용
  

With clientSubId you can manage several Sender ID + message signature combinations,
which makes handling international sending per country and per service far more flexible.

2. Fixed the RateLimit control bug for ApiKey authentication

A bug where some customers arriving over ApiKey authentication only ever got the default RateLimit has been fixed.

• The RateLimit policy configured per customer now applies correctly
• Call control stays consistent even for high-traffic customers

Why it matters (one line each)

• Extended international message signatures let you handle policies that differ by country and carrier flexibly, which raises the reliability of global messaging.
• Introducing clientSubId lets one API key manage several Sender IDs and signatures, which reduces the complexity of running an international service.
• Fixing the ApiKey RateLimit bug applies each customer's call policy accurately, which makes API operations predictable even under heavy traffic.

How to use it

• For international message, we recommend setting clientSubId separately per Sender ID / message signature.
• For countries that need a Sender ID or a message signature, plan your schedule around the **advance registration period (2~4 weeks)**.
• Customers on ApiKey authentication get the correct RateLimit policy automatically, with no configuration change.

Things to note

• Sender ID and message signature policies differ by country and carrier, and sending without prior registration can fail.
• Omitting the message signature or using the wrong Sender ID can get the message blocked as spam or impersonation.
• For details on international message policy, check with your sales representative.
• The RateLimit policy may be adjusted after advance notice, depending on system load and operational policy.