[ 25.07.31 ] July API update monthly summary

Summary

The OMNI API Active-Active (IDC–Cloud) migration was completed in stages across June and July, together with RateLimit improvements and key bug fixes.

At a glance

• OMNI API Active-Active (IDC–Cloud) migration complete
• Improved API RateLimit policy
• Fix for the Brand Message variable send error

What changed?

1. Active-Active (IDC–Cloud) migration complete

We moved from a single IDC-based deployment to an Active-Active architecture that uses AWS and IDC at the same time, which considerably strengthens service stability.

2. More granular API RateLimit policy

The call limit policy used to apply one baseline to everyone. You can now configure a RateLimit tailored to each customer's characteristics.

3. Fix for Brand Message variable substitution

Cases where variable values went missing or were substituted incorrectly have been resolved, so messages send more accurately.

Why it matters

• The Active-Active architecture keeps the service running through heavy traffic or a failure in one segment, which raises availability considerably.
• The more granular RateLimit policy minimizes the impact of abnormal or runaway traffic and protects overall API stability.
• Fixing variable substitution raises Brand Message quality, which reduces customer support load and operational risk.

How to use it

• Nothing changes in how you call the API. The Active-Active migration needs no endpoint change and no extra configuration.
• If you hit a RateLimit error (429), applying an exponential backoff retry policy will keep your integration running smoothly.

Things to note

• The default send throughput is 200 TPS. If you need a higher RateLimit, contact us to arrange it.