Integration-owned messaging
Your integration owns pre-arrival messaging for every Public API Reservation. Trutee sets both trutee_confirmation_suppressed and trutee_cancellation_suppressed to true.
Use messaging.course_name, guest_name, allocation time, quantity, and selections to send:
- the initial confirmation;
- reminders and arrival instructions;
- cancellation confirmation;
- replacement details after cancel-and-rebook.
The messaging object is a delivery-ready snapshot, not a delivery receipt. Trutee does not email or text the guest through this flow. Your integration must record delivery status, respect consent and local messaging law, avoid duplicate sends after idempotent replays, and provide its own support contact.
On an ambiguous write, recover the idempotent response before sending. On cancellation, send only after a 200 response. A 409 denial means the Reservation remains active.

