Carousel Overview
Carousel templates are Meta-approved message templates with 2–10 swipeable cards, each with a header image and up to two buttons. They are used for marketing campaigns — not for native catalog cart browsing.
Carousel vs catalog commerce
| Aspect | Carousel template | Catalog / native cart |
|---|---|---|
| Message type | Approved template with carousel component | Interactive product_list or product |
| Customer browse | Swipe cards in a template message | Browse catalog and cart inside WhatsApp commerce UI |
| Order creation | Buy quick_reply tap → order_source: carousel_campaign | Native cart checkout → order_source: catalog_cart |
| Checkout | May use portal Flow or manual follow-up | WhatsApp Checkout Flow after cart order |
| Registration | Portal UI — submit to Meta for approval | POST /catalogs + product APIs |
Button types are fixed at registration: Carousel template button structure (types, count, and order) is defined when the template is submitted to Meta. ChatYug's registration validator requires all cards to share the same button layout. The portal blocks editing of
APPROVED templates (Cannot edit APPROVED templates). The External API provides list, get, and send only — no template modification endpoint. To change button types on a carousel, register a new template and wait for Meta review (typically 24–48 hours).
Workflow
- Register a carousel template in the ChatYug portal (submit to Meta for approval)
- List approved templates via GET /templates/carousel
- Send to customers via POST /messages/carousel
- Receive
eventType: statuswebhooks for delivery per card send - If cards have Buy buttons, orders are created with
order_source: carousel_campaignorcarousel_inquiry
API sections
- Templates — list and retrieve approved carousel templates
- Sending Carousel Messages — send with per-card parameters