zinn-campaigns

PUT `/v1/email-marketing/senders/{sender_id}/webhook`

Store your e-mail provider's webhook signing secret for this connection.

Authentication

Send an API key as a bearer token. The key must carry the email_marketing.manage permission; a key without it is refused with 403, not 404.

Where your organisation id goes

This endpoint takes org_id as a query parameter. Leave it out and the call covers your whole tenancy subtree; send it to narrow the call to one organisation.

Your organisation id is on the API keys screen in your dashboard, beside the key itself. It is the same id in every call you make.

Try it

Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.

curl -X PUT https://api.zinndigital.com/v1/email-marketing/senders/{sender_id}/webhook \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "signing_secret": <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

Gated on email_marketing.manage. The secret (Svix format, whsec_…, as Resend issues it) is kept in the secret store and never returned. Point the provider's delivered, bounced and complained events at the returned webhook_url.

Parameters

Name	Type	Required	What it is
`org_id (query)`	`Uuid`	No	The organization this call acts on. Optional for a caller with exactly one direct membership; required for anyone with more than one — which is every reseller and every agency…
`sender_id (path)`	`string`	Yes	—

Request body

Name	Type	Required	What it is
`signing_secret`	`string`	Yes	—

Response

Name	Type	Required	What it is
`webhook_url`	`string`	Yes	—

Errors this endpoint can return

400 · 401 · 403 · 404