Common order events
Send confirmation, packing, shipping and pickup messages when users have consented to the chosen channel.
Integration outline
Your backend receives an order event, checks consent and calls the SendSend API. Use an `Idempotency-Key` based on the order number and event type to guard against duplicates during retries.
Production checklist
- Separate transactional messages from promotional content.
- Store credentials server-side.
- Track HTTP status codes and failures.
- Validate connector availability before launching.
A `202 Accepted` API response is not proof that the recipient received the message.