List Flow responses
The forms customers submitted to ONE Flow, newest first. The Flow is resolved inside the key’s own WABA first, and that resolution is the only thing that scopes what follows — a Flow of another WABA (including another WABA of the same tenant) answers 404 and no response is ever read.
Responses past their retention window are excluded HERE, not only by the pruning job, so a caller can never read a submission the published window says is gone. contactPhone is null when the phone is no longer ours to publish. externalMessageId is Meta’s wamid and is named as a provider id on purpose — every other id on this surface is local.
notice: "FLOW_RESPONSES_WINDOW_TRUNCATED" appears on the page when the Flow minted more sends than one request will correlate (a 10,000-session ceiling). A short answer that does not say it is short is what makes a caller conclude submissions were lost. Permission flows:read.
Requires a number-scoped key. A tenant-scoped key must name the number with the x-whatsapp-number-id header, or it gets 403 TENANT_SCOPE_NOT_ALLOWED.
Authorizations
Your ps_ API key
Path Parameters
The local id of the Flow — the id field GET /v1/flows returns, never metaFlowId.
Query Parameters
Page number, 1-based.
x >= 1Rows per page. Default 30, maximum 100.
1 <= x <= 100Response
List Flow responses