A confirmation message refers to an existing waiver. Sending it does not collect a new signature or create a new arrival. Keep the action tied to the signed record the guest actually needs.
Start with the record
Retrieve or otherwise identify the intended waiver before calling send confirmation. Use the endpoint's supported request fields and the messages:send scope. Do not construct a generic marketing campaign around this transactional endpoint.
Confirm the record belongs to the organization represented by the API key. If a guest reports a missing message, distinguish an incorrect record selection from a message delivery problem before initiating another send.
Make repeat sends deliberate
A staff member may need to send another copy, but repeated clicks or a background retry loop can create unwanted contact. Disable a pending action in the interface and show its result before offering another attempt.
The route has a tighter sending limit. A 429 should follow retry-after. A lost network response is different: the send may already have occurred. Reconcile that uncertainty rather than assuming a retry is harmless.
Keep sensitive content out of diagnostics
Record the operation, status and request ID. Do not log a full participant message, phone number or email address unless your system has a specific need and an appropriate handling policy. Never include the API key in the support request.
A successful API action is not a guarantee that a human read the message. Describe the state your system actually knows. Avoid UI labels such as “guest notified” if your integration only knows that a send request was accepted.
Coordinate with invitations
An event invitation asks someone to complete a task. A waiver confirmation follows a signed record. Use the event invitation workflow when you are contacting a roster before signing.
Before launching, test one confirmation for a representative record and inspect the guest-facing content through your normal authorized test process. Keep broader communication preferences and marketing messages separate from this operational action.