Skip to main content

Forward Meta pricing + conversation objects on WhatsApp status webhooks

Feature Request

Hi Zernio Team,

From 1 Oct 2026 Meta charges service messages after 1,000 free per number per month, and CTWA free entry point windows last up to 7 days. Please pass Meta's status "pricing" object (type, category, billable) and "conversation" object (id, expiration_timestamp) through on message.sent / delivered / read webhooks, so integrators can see which messages Meta charged and when an FEP window closes.

Today only id, status, timestamp, recipient and error are forwarded (confirmed by support).

Posted by RED EAGLE DIGITAL ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Miquel Palet López

    Team•

    Sep 30

    Shipped and live. WhatsApp message.sent, message.delivered, message.read and message.failed webhooks now carry two extra fields:

    • pricing: { billable, pricingModel, category, type }
    • billingConversation: { id, expiresAt, originType } (named this way so it does not clash with the existing Zernio conversation block)

    Both keys are always present on WhatsApp events and are null when Meta omits them. Your "RED Inbox" webhook is already subscribed to these events, so nothing to change on your side. Docs and the OpenAPI spec (1.167.0+) are updated.