You send website form leads into Stravax Engage by posting to a public leads endpoint with a form key unique to your organization. The lead lands on your CRM pipeline board in the intake stage, tagged with source "web form," and any extra fields your form collects are kept alongside it.
Open the CRM section and go to Connections. The web form key is generated (and can be rotated) there by an admin. Connections shows a copyable request snippet you can adapt into your website's form handler.
Post the form fields to the public leads endpoint, passing your key either as an x-engage-form-key header or a key field in the body:
curl -X POST https://app.stravax.ai/api/public/leads \
-H "x-engage-form-key: YOUR_FORM_KEY" \
-H "content-type: application/json" \
-d '{"name":"Jane Doe","phone":"0501234567","email":"jane@example.com"}'
The endpoint resolves your organization from the key itself, never from anything else in the request body. The response is a neutral {"ok":true} or {"ok":false}, so it does not reveal whether a failure was a bad key or something else; the one distinguishable response is a standard 429 when a sender is submitting too fast. If leads are not arriving, check the key configured in your form against the one shown in Connections.
The lead is created with:
If the phone number matches an existing WhatsApp contact for your organization, the lead is linked to that contact automatically. See Leads, pipelines and timelines for how the lead record and its timeline work from there.
Yes. Submissions are limited per key to protect your form from spam and abuse: a request budget per minute and a larger budget per day. Going over the limit returns a "too many requests" response with a retry delay; legitimate traffic from a normal contact form stays well under it. The limit is enforced before your organization is even resolved, so it also caps abuse against an incorrect or guessed key.
Field values and the number of custom fields you can send are capped to keep a single malformed or abusive submission from bloating a lead record. Keep form fields to reasonable, human-entered lengths (names, short text answers, a phone number) rather than pasting large blocks of text.