Overview
All endpoints in this collection call a single route with a different JSON body per message type:
POST {base_url}/wba/v1/tsp/messages/The message "type" field (text, image, video, audio, document, contacts, location, interactive, template, reaction) and, for interactive/template messages, the nested "interactive.type" or template button sub_type, determine the required schema. This document groups the 28 sample requests into four families:
| Family | Message types |
|---|---|
| Text & Media Messages | text, image, video, audio, document, contact, location, reaction |
| Interactive Messages | cta_url, list, reply buttons, location request |
| Template Messages | approved templates, incl. catalog, coupon, multi-product, carousel |
| Payments & Order Messages | order_details / order_status interactive messages and the order-details template pattern, covering UPI, Razorpay, PayU, and payment-link flows |
Updated 10 days ago
Did this page help you?