CTA URL button messages map a destination URL to a labeled button. Users never see the raw link — they tap the button and the URL opens in their default browser. Use this when you want to drive traffic from WhatsApp to a web experience (a booking page, a product page, a checkout flow) without exposing a long, opaque URL in the message body.Documentation Index
Fetch the complete documentation index at: https://docs.zavu.dev/llms.txt
Use this file to discover all available pages before exploring further.
Send a CTA URL Message
Specifications
| Property | Requirement |
|---|---|
Body text (text) | Required, max 1024 chars |
ctaDisplayText | Required, max 20 chars |
ctaUrl | Required, valid URL (HTTPS required by WhatsApp in production) |
ctaHeaderType | Optional: text, image, video, document |
ctaHeaderText | Required if ctaHeaderType is text, max 60 chars |
ctaHeaderMediaUrl | Required if ctaHeaderType is image, video or document. HTTPS URL that returns valid media |
footerText | Optional, max 60 chars |
Header Variants
Text header
Image header
Video header
Document header
No Webhook on Tap
Unlike reply Buttons and Lists, tapping a CTA URL button does not generate an inbound webhook. The user is redirected directly to the destination URL inside their browser.To track clicks, append tracking parameters to
ctaUrl (for example ?utm_source=whatsapp&clickID=abc123) and read them on your landing page.24-Hour Window
CTA URL messages are free-form interactive messages. They can only be sent inside an open 24-hour conversation window — typically after the user has messaged you first. To initiate a conversation outside the window, send a template message first, then follow up with a CTA URL message once the user replies.Use Cases
- Drive traffic to a booking or scheduling page
- Link to a checkout or product page from a promotion
- Share long campaign URLs without cluttering the message
- Replace raw URLs in receipts or confirmations with a branded button
- Direct users to a web form, survey, or support portal
