Welcome to the WhatsApp Flows API from Meta. This collection contains the [Graph API](https://developers.facebook.com/docs/graph-api/) requests to create, manage, and send WhatsApp Flows. For the full Flows documentation, refer to [https://developers.facebook.com/docs/whatsapp/flows<br>](https://developers.facebook.com/docs/whatsapp/flows) **Note:** Flow messages won't be delivered to unsupported WhatsApp versions. # Installation Import this collection into postman to start using the API. You can generate the code for the API calls in your language by following the steps here [https://learning.postman.com/docs/sending-requests/generate-code-snippets/#generating-code-snippets-in-postman](https://learning.postman.com/docs/sending-requests/generate-code-snippets/#generating-code-snippets-in-postmanEnvironmentChangelogUpdates) # Environment This collection uses environment variables. To edit the variables in the collection 1. Click on the environment name in the left sidebar 2. Go to the "Variables" tab 3. Update the "Current Value" for the variables Here's the list of the variables used in the collection | Name | Description | | --- | --- | | `base-url` | Base URL for Facebook Graph API. Example: [https://graph.facebook.com/v18.0](https://graph.facebook.com/v18.0) | | `access-token` | This can be retrieved by copying the **Temporary access token** from your app which expires in 24 hours. <br> <br>Alternatively, you can generate a [System User Access Token](https://developers.facebook.com/docs/whatsapp/business-management-api/get-started#system-user-access-tokens). | | `waba-id` | Your WhatsApp Business Account (WABA) ID. | | `flow-id` | Id of the flow to update or send. You can set this variable after creating a flow. | | `business-phone-number-id` | ID for the sender phone number connected to the WhatsApp Business API. You can get this from the request "Get WABA Phone Numbers". | | `customer-phone-number` | Phone number that you want to send a flow to. | # General Notes - You can add \`fields\` param to any request to specify which exact fields will be returned in the response - POST requests accept the data in query or form or JSON body. However, the asset upload API only accepts the file attachment in form data # Changelog Updates to the Flows API will be tracked here
Versori has established itself as the third generation of Integration Platform as a Service (iPaaS). Versori builds custom integrations for its customers using an intuitive visual user interface.
Versori’s connector engine means there is no dependency on an existing library of apps, all you need to start is the documentation of the app or system you want to integrate to.
Drag and drop the Open API Spec into Versori's connector engine to create a new connector in minutes.
Build out visual integration workflows with powerful data tools on an intuitive canvas UI.
Deploy your automated workflow instantly and maintain your integrations with ease.
Is there something wrong with this spec? Let us know and Versori's engineering team will improve the quality of the spec based on your feedback.
Automatically match and transform data fields between systems with precision, reducing manual effort and errors.
Design integrations visually, test workflows instantly, and deploy seamlessly—accelerating your time to value.
Drag and drop API specifications to build custom integrations, unlocking endless connectivity with minimal setup.