A static WhatsApp Flow is a form that lives entirely on the customer's phone: screens, fields, a submit button, and one message back to you at the end. That covers most lead forms. It stops covering them the moment a screen needs live data: which batches still have seats, which time slots are free, whether this coupon is valid. Then the Flow has to call your server between screens, and that server has rules that most HTTP endpoints don't: every request is encrypted to your key, every response must be encrypted back, Meta pings it to check it's alive, and if it's slow or failing for long enough, Meta can throttle or block the Flow for every customer.
This post builds that endpoint in TypeScript for a real use case, a demo-class booking form for a coaching institute: pick a course, see the batches that still have seats, enter the student's name, book. It covers the encryption, the request actions, the HTTP status codes Meta acts on, and the health monitoring.…