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 — this 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.
API key authentication - use your Zernio API key as a Bearer token
In: header
Query Parameters
WhatsApp social account ID
Scope to responses for this flow
Max responses to return
50value <= 200Response 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"
}
]
}{
"error": "Unauthorized"
}Get number status GET
Live snapshot of a connected number straight from Meta: the phone-number node (display number, display name + approval, quality rating, messaging-limit tier, throughput, official-business badge, connection status, health_status) and its owning WhatsApp Business Account (name, business verification, timezone, health_status). Fetched live because Meta updates quality/tier/name/health over time; the call also refreshes the cached values shown on the connection card.
List flow versions GET
List the flow's version history (the clone lineage Zernio tracks, since Meta has no native versioning), newest version first. Each entry is enriched with the version's live name and status from Meta. A flow with no lineage returns just itself as version 1.