Create or edit a WhatsApp form
Save a WhatsApp form (a Meta Flow: screens of fields that open inside the chat) as a DRAFT on the connected Business account. Nothing is sent. Pass form_id to replace the definition of an existing draft. Write definition as Flow JSON: {"version":"7.2","screens":[{"id":"DETAILS","title":"...","data":{},"layout":{"type":"SingleColumnLayout","children":[...]}}]}. Screen IDs use letters and underscores; SUCCESS is reserved. Components: TextHeading, TextSubheading, TextBody, TextCaption, TextInput (input-type text, number, email, password, passcode, phone), TextArea, Dropdown, RadioButtonsGroup, CheckboxGroup, ChipsSelector (data-source: [{id,title}]), DatePicker, CalendarPicker, OptIn, EmbeddedLink, Image, PhotoPicker, DocumentPicker, If, Switch. Inputs need a unique name and label. Every screen ends with a Footer whose on-click-action is navigate ({"name":"navigate","next":{"type":"screen","name":"NEXT_ID"},"payload":{}}) or, on the last screen ("terminal": true, "success": true), complete with a payload that collects the answers: "${form.field}" for this screen, "${screen.OTHER_ID.form.field}" for earlier screens. Only the complete payload is returned as answers. Meta returns validation_errors; fix them and save again with form_id. Then share preview_url. Reference: https://developers.facebook.com/docs/whatsapp/flows/reference/flowjson
Request
- Base URL: https://whatsync.app
- URL: https://whatsync.app/api/v1/tools/create_whatsapp_form
- Auth: one of:
- HTTP bearer
- API key in header X-API-Key
Headers
Stable key for a write; body idempotencyKey takes precedence.
Request body
Response
JSON result. Every response includes X-Request-Id.
Changes
No recorded changes to this operation across all 1 revision of this API.