Order Webhook
Status: In development: its code is written and tested on its own, but it does not work end to end on the platform yet. It cannot be installed.
| Kind | Version | Publisher | Licence |
|---|---|---|---|
| Connector | 1.0.0 | ZAITRACK | Apache-2.0 |
What it does
Your TMS, ERP or cargo system posts each transport order in ZAITRACK's order format, signed with the installation's secret. The same order id again amends it; a cancellation cancels it. A batch of up to 100 is taken whole or refused whole, naming the order at fault.
- Regions: AE, SA, OM, QA, KW, BH
- Capabilities:
integration.order.webhook.ingest,integration.order.fact.order
How to use it
Not yet: see its status above.
Configuration
None: it needs no settings.
Credentials
Each is a secret setting of the installation: kept sealed (OpenBao in production), never shown again; Adapter Studio shows it as set.
webhook_secret
Limits
- Memory: 128 MB
- Time per call: 10,000 ms
- Largest message: 65,536 bytes
- Calls at once: 16
- Network: no network access
Troubleshooting
- Credentials refused. The secret settings must be the ones the provider issued for this account and environment (sandbox or live); give them again in Adapter Studio, since they are never shown back.
- Rate limited. The provider's limit applies to the account: calls are retried with a growing pause; spread scheduled work or ask the provider for a higher limit.
- Nothing is sent or synced. The installation must be active, its version approved; it reaches only the hosts listed under Limits.
- Webhooks rejected. The webhook secret must match the one configured at the provider; a request whose signature does not match is refused.
Source
adapters/connectors/order-webhook