[ 25.10.31 ] October API update monthly summary

Summary

The Sandbox (virtual network) opened and delivery history, status, and statistics improved considerably, raising development and operations quality.

At a glance

• The Sandbox (virtual network) environment is officially open
• Stage-by-stage delivery history lookup
• Daily send and report statistics
• Sender number substitution
• appUserId/userKey transmission for Kakao Biz Message
• Korean-language reportText when using report webhook/polling

What changed?

1. The Sandbox (virtual network) environment is open

A separate development and QA environment that you can test against with the same API specification as production.

2. Stage-by-stage delivery history lookup

The message transmission process is split into 3 stages (received → sent to channel → final result), which makes failure analysis considerably more accurate.

3. Korean-language reports and quality improvements

Every report reason is now in Korean, which speeds up customer support and operations.

4. Extended delivery history table

Fields based on Bizgo requirements, such as paymentCode and productType, were added, which strengthens data analysis and settlement quality.

Why it matters

• The Sandbox lets you verify under production-equivalent conditions during development and QA, which reduces functional errors and deployment risk.
• Stage-by-stage delivery history shows exactly where a message failed, which speeds up failure analysis and customer support considerably.
• Korean-language reports make things clearer for the operations and support teams, improving both accuracy and handling time.
• Duplicate report prevention avoids needless reprocessing and incorrect statistics, which raises operational stability.
• The extended delivery history table lets you apply message product classification and settlement logic accurately, improving data-driven operations.

How to use it

• The Sandbox uses the same API specification as production, so you can use it directly for test automation and QA verification.
• Trace the message flow with the msgKey or requestId value and root-causing a failure becomes much easier.

Things to note

• Data generated in the Sandbox environment may differ from real production data.