POS
Point-of-sale systems that generate delivery orders at the till.
- Available
Foodics
Live order source integration for foodics-connected restaurant branches.
Developers & integrations
See which integrations are live, how delivery providers connect, and how to build either side of the contract, all in one place.
Ecosystem
FleetBridge is built for many order sources and many delivery providers, not a fixed pair. Foodics and Zid are today's live order source integrations — every category below is a real, supported integration path.
Point-of-sale systems that generate delivery orders at the till.
Foodics
Live order source integration for foodics-connected restaurant branches.
Online storefronts and checkout platforms.
Zid
Live order source integration for zid-connected online stores.
Multi-merchant ordering marketplaces.
Dedicated online-ordering and qR-menu platforms.
Enterprise resource planning and back-office order systems.
Any in-house application or API integrating directly with the order source contract.
Delivery providers integrate through the same Standard Delivery Contract regardless of size — local, regional, enterprise, or future independent providers. No delivery provider is certified for production yet; this catalog will list connected providers by name once one is.
For delivery providers
FleetBridge is an integration and orchestration layer, not a competitor to delivery providers. Providers remain independent companies — FleetBridge standardizes how orders reach them from many upstream order sources.
Delivery providers are independent companies. FleetBridge does not require access to a provider's source code, and commercial onboarding is handled directly between FleetBridge and the provider.
Standard Delivery Contract v1.1.0 · revision 2026-09-19
A single, versioned HTTP contract covers delivery creation, updates, status, tracking, cancellation, return, and a webhook connectivity test — the same contract every connected provider implements.
| Method | Endpoint |
|---|---|
| POST | /deliveries Create a delivery |
| GET | /deliveries/{providerDeliveryId}/status Poll delivery status |
| GET | /deliveries/{providerDeliveryId}/tracking Poll driver location and ETA |
| PATCH | /deliveries/{providerDeliveryId} Update mutable delivery fields |
| POST | /deliveries/{providerDeliveryId}/cancel Cancel a delivery |
| POST | /deliveries/{providerDeliveryId}/return Request a return to origin |
| POST | /webhooks/test Verify a webhook connection |
A shared status vocabulary from sent_to_provider through delivered, cancelled, or failed, plus a return sub-lifecycle.
Nullable driver location and estimated-delivery fields where a provider's capabilities support them — never fabricated when unavailable.
An optional immutable per-delivery webhook URL, a global callback for the connection, and status/tracking polling when neither is configured.
Every webhook is signed with HMAC-SHA256 over the exact request body (X-Platform-Signature) and checked against replay and out-of-order delivery.
Create-delivery requests carry an idempotency key, enforced in durable storage, so retries never create a second delivery.
Up to three attempts for idempotent calls (update, cancel, and return are never auto-retried), with one error envelope across every endpoint.
Build on whichever side of FleetBridge your platform sits: send orders in as an order source, or receive them as a delivery provider.
Your platform → Order source integration → FleetBridge → Delivery providers
Send delivery orders into FleetBridge from a POS, e-commerce platform, marketplace, ERP, or custom system. Contract: FleetBridge order source API, v1, contract revision 1.0.0.
FleetBridge → Standard Delivery Contract → Your delivery network
Receive orchestrated delivery work from every connected order source through one HTTP contract. Contract: FleetBridge standard delivery Provider API, v1.1.0, revision 2026-09-19.
Every event is signed with HMAC-SHA256 in the x-Platform-Signature header and correlated by platformReference — this is the exact payload shape from the published contract.
{
"eventType": "driver.location_updated",
"platformReference": "FB-123",
"providerDeliveryId": "PROV-456",
"providerTrackingId": "TRACK-456",
"status": "on_the_way",
"eventTimeUtc": "2026-09-19T12:30:00Z",
"driverName": "Controlled Driver",
"driverPhone": null,
"driverLat": 32.2211,
"driverLng": 35.2544,
"trackingUrl": null,
"estimatedDeliveryAtUtc": "2026-09-19T12:50:00Z"
}Every contract endpoint returns the same error envelope, with retryable telling the caller whether a retry can help.
{
"code": "validation_failed",
"message": "Request validation failed.",
"retryable": false,
"fieldErrors": {
"currency": ["Must be three uppercase characters."]
}
}The published Standard Delivery Contract and Order Source Integration Kit document every endpoint, field, and error case in full.
Point us to your order source or delivery provider and we'll scope the integration.