Settings — Webhooks & API key
Permission: Admin only.
The Developer group in Settings covers machine-to-machine access: Webhooks (Zendera calling your systems) and the API key (your systems calling Zendera).
For an overview of all Settings sections, see Settings.
Webhooks
Settings → Developer → Webhooks
Webhooks push events from Zendera into your own system.
Webhooks list
| Column | What it means |
|---|---|
| Name | Your label for the webhook. |
| Type | The event that triggers it. |
| URL | The endpoint Zendera posts to. |
| Status | Active, Degraded (recent deliveries are failing) or Disabled. |
Each row has a Delete button. Click a row to open the webhook.
How to create a webhook
- Click New webhook.
- In the Webhook card, fill in:
- Name (required, unique).
- Webhook URL (required) — the endpoint to POST to.
- Send webhook when — the trigger event (for example Order status changes).
- In the Conditions card, optionally add conditions. The webhook fires only when the event matches all of them. Build them in Visual mode (Select property → Operator → Value, Add Condition for more rows) or write them in Text mode.
- In the Body card, define the JSON that’s sent. In Builder mode, tick the fields you want and check the Generated JSON; in Text mode, write the template yourself.
- Click Save.
After you create a webhook, its Signing secret is shown once. Copy it and store it somewhere safe — it can’t be retrieved later.
Webhook endpoint status
When you open an existing webhook, the Webhook endpoint status card shows its status, URL, Last delivery, Last delivery status, Consecutive failures and the (masked) Signing secret.
- Rotate secret — issues a new signing secret. The current secret stops working immediately, so whatever receives the webhook has to be updated with the new one.
- Re-enable — shown when the webhook is disabled; turns it back on.
You can also switch a webhook off or on with its Active toggle.
Delivery logs
Below the webhooks list, Delivery logs shows the history of webhook deliveries with their Time, Status (Success or Failed), URL, Response and Duration. Use the Status filter to show only successes or failures.
Click a log row to open Delivery details, including the Request body, Response code, Response body and any Error.
API key
Settings → Developer → API key
External systems can read and update your Zendera data on your behalf using an API key. Your organization has one API key.
The API key card shows your Zendera organization ID (integrations need it together with the key), the key’s Status (Active or No API key), and when it was Created and Last seen.
- Generate API key — creates the key when you don’t have one.
- Hold to show the API key — press and hold to reveal the key. Click it to copy, and Hide to hide it again.
- Regenerate API key — replaces the key. Integrations using the current key stop working until they’re updated to the new key.
- Delete API key — removes the key. All integrations based on it stop working immediately.
Keep the key secret. If you think it has leaked, regenerate or delete it immediately and contact Zendera.
What’s next
- API documentation — for developers building against the API.
- Settings — overview.