Get Flow endpoint config
The data_exchange wiring of ONE Flow: where we forward the decrypted exchange (url), whether a signing secret exists (hasSecret), OUR proxy URL for this Flow (endpointUri), what Meta has registered (metaEndpointUri), whether the two DIVERGE (drift), and whether the number holds an encryption keypair at all (numberHasKey).
⭐ numberHasKey: false is the field this route exists for. Without a keypair on the number Meta has nothing to encrypt with, so the call never reaches the proxy, so the destination is never used — and nothing else on either side reports it. warnings carries the same facts as stable codes: FLOW_ENDPOINT_NO_DESTINATION, FLOW_ENDPOINT_NUMBER_HAS_NO_KEY, FLOW_ENDPOINT_KEY_NOT_AT_META, FLOW_ENDPOINT_META_URI_UNKNOWN, FLOW_ENDPOINT_META_DRIFT.
The HMAC secret itself is NEVER returned here — only hasSecret. Permission flows:manage and deliberately not flows:read: endpointUri and metaEndpointUri embed the number’s endpoint path token, and that token is the credential of the proxy.
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.