26.05.31 May API update monthly summary

Summary

Reservation management expanded considerably, and recipient number consistency checks now make delivery more reliable.

At a glance

• Reservation management fully expanded (lookup / change / control)
• Reservation recipient management
• Automatic recipient number consistency checks before sending

What changed?

1. Expanded reservation management

Lookup, change, and recipient management now come together so you can control reservations precisely.

Reservation lookup

• List reservations
• View a reservation in detail

Reservation control

• Edit a reservation
• Cancel a reservation
• Pause a reservation
• Resume a reservation

Reservation recipient management

• Add reservation recipients
• List reservation recipients
• Delete reservation recipients

2. Automatic recipient number consistency checks

At send time, the recipient numbers that were accepted are compared against the numbers actually being sent to.

• A mismatch fails the send
• Blocks mis-sends caused by data errors before they happen

Why it matters

• Expanded reservation management lets you control bulk and recurring messages flexibly, raising both operational efficiency and stability.
• Reservation recipient management lets you manage the audience dynamically, which improves campaign operations and targeting accuracy.
• Recipient number consistency checks block mis-sends caused by bad data before they happen, reducing wasted cost and incident risk.

How to use it

• A reservation can still be edited, paused, and resumed after creation, so we recommend controlling it flexibly as the situation changes.
• Managing the recipient list through the API makes changing a bulk send audience efficient.
• If a consistency check fails, review the logic that produces your recipient number data before sending.

Things to note

• While a reservation is paused, no messages go out; they resume normally afterward.
• When a recipient number consistency check fails, the message is not sent and an error is returned.
• When recipient data changes, take care that the data does not diverge between reservation time and send time.
• Managing large recipient lists increases API call volume, which can bring you under the RateLimit.