Settings — Webhooks & Integrations
Permission: Admin only.
This section covers Webhooks (pushing events from Zendera to your own system) and Integrations (API keys, ERP integration, GPS providers, SSO).
For an overview of all Settings tabs, see Settings.
Webhooks
Settings → Webhooks
Webhooks push events from Zendera into your own system in real time. The page has two sections.
Webhooks list
A table of every webhook your organization has set up.
| Column | What it means |
|---|---|
| Name | Your label for the webhook. |
| Type | The event that triggers it. |
| URL | The endpoint Zendera posts to. |
| Status | Whether the webhook is active. |
| Actions | Edit or delete the webhook. |
Use the Filter bar above the table to search the list. Click + Create new webhook to add a new one.
The Create Webhook dialog
When you create or edit a webhook, you’ll see these fields:
- Name (required) — your label for the webhook.
- Send webhook when (required) — the trigger event (e.g. Order status changes).
- Expression — optional conditions on top of the trigger.
- Visual / Text toggle — build conditions with the visual builder or write a raw expression.
- Each condition row is Select property → Operator → Value.
- Click + Add Condition for more rows.
- Webhook URL (required) — the HTTPS endpoint to POST to.
- Webhook Body Template — the JSON body that gets sent.
- Builder / Text toggle — pick fields with checkboxes, or paste a raw template.
- In Builder mode, expand any of these groups and tick the fields you want included: Customer, Delivery, Driver, Event, Order, Pickup.
- Generated JSON preview on the right updates as you tick boxes. (The “Template is required” notice means you need to include at least one field.)
Click Save to apply, or Cancel to discard.
Delivery Logs
Below the webhooks list is the Delivery Logs table — the history of every webhook delivery attempt.
| Column | What it means |
|---|---|
| Time | When the delivery was attempted. |
| Status | Success or failure. |
| URL | The endpoint that was called. |
| Response Code | HTTP response code returned by your endpoint. |
| Duration | How long the request took. |
Use the Status dropdown to filter (e.g. only failures). Pagination controls let you change the page size and step through pages.
Failed deliveries are retried automatically — each retry waits longer than the last. Use the Delivery Logs to diagnose endpoints that are returning errors or timing out.
Integrations
Settings → Integrations
Centralized place to configure:
- API keys (see below).
- Cargo carrier credentials (DHL, Posten, etc.).
- GPS / sensor providers.
- ERP integration (Dynamics, Visma — most Zendera customers use one of these).
- Single sign-on (SSO) (if your plan includes it).
How to create an API key
- Settings → Integrations → API keys.
- Click Create API key.
- Give it a label (e.g. “ERP - production”).
- Copy the key shown — this is the only time you’ll see it in full. Store it in your secrets manager.
- Save.
How to rotate an API key
- Find the key in Settings → Integrations → API keys.
- Click Rotate. Zendera issues a new key.
- Update the key in your downstream system.
- The old key continues to work for a short overlap window.
How to revoke an API key
Find the key, click Revoke. Effective immediately.
API keys never expire automatically. Rotate every 90–180 days and revoke any you can’t account for.
What’s next
- API documentation — for developers building against the API.
- Settings — overview.