Reference

Refer to this section to get more details on the Flows API, Flow JSON, and other technical topics for WhatsApp Flows.

Flow JSON Flow JSON is the way you define and express your use case for a WhatsApp Flow. Learn more about the Flow JSON syntax here.	Flows API The Flows API provides a programmatic way to manage your Flows. This API allows you to create new Flows, publish draft Flows, and more.
Error Codes Are you seeing an error response from the Flows API? Learn more about the error and how to fix it here.	Versioning Learn more about the different versions of Flow JSON and the Data API.
Webhooks It's important to keep an eye on the performance of your Flow.	Metrics API Learn all about the Metrics API here.

Looking for Help?

Status Check on the status of WhatsApp and WhatsApp Flows using our external status tool.

Support If you're stuck and need help, create a support case using the link above. You can also visit the Community to ask additional questions.

Learn More

Ready to create your first Flow? Get Started here! Curious about what Flows look like? Explore examples here. Want to kick the tires with a demo Flow? Try it now with the Flows Playground. Looking for a comprehensive list of Flow Components? Check it out here.

Terminology

Flows: Represents a use case or workflow that a business offers to users. For example, “Book an appointment”. A Flow consists of screens, components (such as input fields), assets such as graphics), and (optionally) an endpoint for data-driven interactions.

Flow JSON: Flow JSON is used to programmatically define Flows.

Components: Individual building blocks that make up a screen (text fields, buttons, and so on).

Screens: A collection of Components on a single screen, defined in Flow JSON.

Endpoint: Communication channel created to exchange data between WhatsApp screens and the business server that processes data from each screen. Based on the business logic, the channel is then used to respond back with data to render the next screen in the workflow.