List flow responses
List the responses customers submitted when completing a flow (parsed from the
nfm_reply messages received via webhook), newest first. Scope to a single flow
with flowId, which matches responses whose flow_token carries the <flowId>:
prefix that Zernio stamps on auto-generated tokens at send time. Responses sent
with a custom integrator-supplied flow_token are not attributed to a flow.
Authorization
bearerAuth API key authentication: send your Zernio API key in the Authorization header, prefixed with Bearer.
In: header
Query Parameters
WhatsApp account ID
Scope to responses for this flow
Max responses to return
value <= 20050Response Body
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.whatsappflows.listWhatsAppFlowResponses({ query: { accountId: 'account_abc123', },});console.log(data);{ "responses": [ { "id": "string", "receivedAt": "2019-08-24T14:15:22Z", "from": "string", "senderName": "string", "conversationId": "string", "flowToken": "string", "data": {}, "raw": "string" } ]}Send flow message
Send a published flow as an interactive message with a CTA button. When the recipient taps the button, the flow opens natively in WhatsApp. Flow responses are received via webhooks.
Get Flows encryption key status
Read the RSA business public key registered on the phone number for WhatsApp Flows endpoint encryption. Only one key is active per phone number at a time. Flows that use flow_action: data_exchange (an endpoint-backed flow) stop working at runtime until the endpoint serves the matching private key, and Meta rejects publish with error code 139002 ("Missing Flows Signed Public Key") when no key is registered. `registered` reflects whether a key is present, never `signatureStatus` alone: Meta reports an unregistered key as MISMATCH rather than a null/absent value.