zinn-campaigns
POST /v1/store-connect/forms
The WordPress plugin posts one visitor's sign-up from the site's server (double opt-in).
Authentication
This endpoint is public. It takes no credential and no organisation — it is what our own marketing site and AI answer engines read.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X POST https://api.zinndigital.com/v1/store-connect/forms \
-H "Content-Type: application/json" \
-d '{ "form_id": <string>, "email": <string> }'Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Store token only. The plugin sends it only when the visitor ticked the consent box. The same path as the hosted form (F20, docs/1052 §10f): ONE confirmation e-mail goes out and nobody is a contact until they click it. No oracle: a new, pending, confirmed, throttled, suppressed or over-allowance address all answer ok; closed is a fact about the form (off, Campaigns not open, or the account not in good standing). A form of another org is 404.
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
form_id | string | Yes | — |
email | string | Yes | — |
source_page | string | No | The page the form was on. |
client_ip | string | No | The visitor's IP as the site saw it, kept as consent evidence; ignored when not an IP address. |
user_agent | string | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
result | string<ok, closed> | Yes | — |
Errors this endpoint can return
401 · 404 · 422 · 429