Choose ingress
Browser and server submissions have different trust boundaries.
Public browser
Browser ingress
Use the form public key, an allowlisted Origin, a UUID Idempotency-Key, and a valid X-Turnstile-Token. No PeopleTide API key is exposed to the browser.
Server-to-serverServer ingress
Use a leads:create API key and the registered form ID from a trusted backend. PeopleTide supplies an idempotency key when one is omitted.
Browser setup
Provision the form before accepting traffic.
- 01
Register the form
In Settings → Integrations → Web Forms, create the form and select its stable type.
- 02
Allow exact origins
Add each HTTPS website origin without a path. Requests from another origin are rejected.
- 03
Configure bot verification
Complete Turnstile provisioning so the form becomes active.
- 04
Send an idempotent request
Generate one UUID per user submission and reuse it only when retrying that same payload.
- 05
Publish a workflow
A receipt does not create CRM records by itself. Use a web-form-submitted workflow to decide the action.
Response
HTTP 202 means the submission was accepted.
Accepted submission
{
"accepted": true,
"submissionId": "0f4f0c75-916a-4adc-a5a5-ef1ec43ff35e"
}