Skip to main content
An endpoint lets a WhatsApp Flow talk to a server while the customer fills it in: to check an answer, load options, or decide which screen comes next. Every request between WhatsApp and the endpoint is encrypted with a key pair that belongs to your phone number, and WhatsApp checks the endpoint regularly to make sure it’s working. Flows without an endpoint send their answers only when the customer finishes.
In Flowella. Supported. For Flows built from HubSpot forms, Flowella hosts the endpoint, creates and uploads the encryption key on your number, answers WhatsApp’s health checks and checks that each request really comes from WhatsApp. You don’t run a server. Flows from the Flow designer and the Flowella API don’t use an endpoint.

What an endpoint does

In Flowella. When the customer submits a HubSpot-form Flow, the endpoint checks the answers against the live HubSpot form and submits them to HubSpot. If something is wrong, the customer sees an error on the screen and can try again. See Errors the customer sees.

Encryption

  • A key pair per phone number. The business creates a public and private key. The public key is uploaded to the WhatsApp phone number and signed by Meta. The private key stays on the endpoint.
  • Every request is encrypted. WhatsApp encrypts each request with a one-time key, which only the endpoint can unlock with its private key. The response is encrypted the same way.
  • Requests are signed. Each request carries a signature made with the Meta app’s secret, so the endpoint can reject anything that didn’t come from WhatsApp.
  • The number must be registered first. The key can only be uploaded once the phone number is registered for the Cloud API.
In Flowella. Flowella uploads the key to your number for you. If the number isn’t registered yet, the sync shows Registration required. Finish registration, then sync again. See Phone numbers.

Data API versions

Flowella’s HubSpot-form Flows use Data API 3.0. See Flow JSON versions.

Keeping the endpoint healthy

  • Answer quickly. Meta suggests responding in under 1 second.
  • Stay reachable from the internet at all times, and answer every health check.
  • Return errors Meta recognises, so the Flow can show the customer something useful.
If health slips, WhatsApp throttles the Flow, then blocks it. See Flow health.

Protecting what customers share

  • Mark sensitive fields. Flow JSON can mark a field as sensitive, so WhatsApp doesn’t show its value in the summary the customer sees after submitting.
  • Don’t ask for sensitive identifiers. WhatsApp’s policies forbid asking for full card numbers, bank account numbers or national ID numbers. See Policy and enforcement.
  • Know where answers go. In Flowella, HubSpot-form answers go to HubSpot, uploaded photos are saved as public HubSpot files, and designer Flow answers go to Flowella’s submission store and any webhook you choose. See Data security.

Flow health

Throttling, blocking and recovery.

WhatsApp Flows overview

Static and endpoint Flows.

Flows in Flowella

How HubSpot-form Flows submit.

Flows error codes

Endpoint and publishing errors.
Checked against Meta’s documentation on 18 November 2026: Implementing endpoints for Flows, Flows encryption, Flow health and monitoring and the WhatsApp Flows changelog.
Last modified on November 18, 2026