Register for API credentials in the Bringg dashboard; all REST calls target the base URL documented at developers.bringg.com and require your access_token in the Authorization header.
POST to the Create Order (Task) endpoint with a payload containing customer details, at least one waypoint (pickup and/or drop-off with address and scheduled time), and optional fields like vehicle_type and priority.
Capture the returned task id and external_id mapping; store the mapping to correlate Bringg events back to your OMS records.
Configure outbound webhooks in the Bringg dashboard: choose events (order_created, driver_arrived, order_done, order_canceled), provide your endpoint URL, and select an authentication method (JWT HS256 or OAuth 2.0 client credentials).
Parse incoming webhook payloads — each event contains task_id, status, driver_id, and a timestamp — and update order status in your OMS accordingly.
For high-volume integrations use the asynchronous bulk-order endpoint and poll for acknowledgement rather than sending tasks one by one.
Known gotchas
Bringg has separate API versions for Own Fleet (v1) and Delivery Hub multi-carrier orchestration (v2) — confirm which version matches your account type before building.
Webhook payloads are not signed by default; always enable an authentication method (JWT or OAuth) on webhook endpoints to prevent spoofed deliveries.
Waypoint lat/lng must be provided when the address geocoding confidence is low; Bringg will reject or misplace tasks if the address cannot be resolved to a coordinate.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp