Bringg API
Bringg is an end-to-end last-mile delivery and fleet orchestration platform that helps enterprise retailers and logistics providers plan, dispatch, and track deliveries across owned and third-party fleets. An unofficial API lets you programmatically pull orders, tasks, drivers, vehicles, teams, and tracking data—and push updates like new orders, dispatch assignments, status changes, and fleet records back into Bringg.
What is Bringg?
Bringg is an end-to-end last-mile delivery platform that enables enterprise retailers and logistics providers to plan, route, dispatch, and track deliveries across any fleet type while balancing cost and customer experience. Customers use Bringg to standardize fulfillment across owned and third-party fleets, automate dispatch and routing, connect to a network of 250+ carriers across 70+ countries, and surface real-time visibility and reporting for last-mile operations.
Core product areas include:
- Platform (planning, routing, dispatch, and driver/fleet management)
- Network (access to 250+ third-party, crowdsourced, and autonomous carriers across 70+ countries)
- Own Fleet and Delivery Hub solutions for self-operated and marketplace delivery models
- Real-time reporting, intelligence, and last-mile visibility
- Support for complex delivery types (big and bulky, white-glove, grocery, same-day, express)
Common data entities:
- Orders, Tasks, Waypoints, Deliveries
- Drivers, Vehicles, Teams, Merchants
- Customers, Recipients, Addresses, Parking Spots
- Routes, Dispatch Assignments, Tracking Updates, Service Plans
- Inventory, Order Items, Webhooks, Application Scopes
The Bringg Integration Challenge
Retailers and logistics providers run mission-critical delivery operations on Bringg every day, but turning multi-fleet, multi-region dispatch into reliable API-driven automation is non-trivial:
- OAuth 2.0 and scoped access: Configuring application scopes and managing token lifecycles across read and write operations adds setup overhead for headless automation
- Regional endpoint sprawl: Separate admin API domains for US2, US3, EU2, and EU3 mean integrations must route to the correct tenant region
- Own Fleet vs Delivery Hub split: v1.0 and v2.0 APIs cover different solutions, each with their own object models and lifecycle states
- Hybrid fleet complexity: Owned, crowdsourced, and third-party carrier data must be normalized into consistent order, task, and tracking objects
- Real-time location and status cadence: Driver location updates and check-in/arrival events stream frequently and require careful polling, webhook, and replay handling
- Rate and request limits: Bringg enforces request limiting, so high-volume order and tracking workloads need throttling and backoff to stay within bounds
How Supergood Creates Bringg APIs
Supergood reverse-engineers authenticated flows and Bringg's REST surfaces to deliver a resilient API layer for your Bringg tenant—across Own Fleet and Delivery Hub, owned and third-party carriers, and every supported region.
- Handles OAuth 2.0 token acquisition, scope selection, and refresh in a managed session
- Routes automatically to the correct regional admin API domain (US2, US3, EU2, EU3)
- Normalizes orders, tasks, drivers, vehicles, and tracking across Own Fleet and Delivery Hub so you integrate once against consistent objects
- Manages high-frequency location and status events with adaptive throttling, retries, and webhook handling
Use Bringg with AI agents: Bringg MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your solution (Own Fleet or Delivery Hub), regions, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Bringg adapter tailored to your tenant, scopes, and fleet model.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Bringg evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Bringg tenant via OAuth 2.0, select application scopes, and obtain an access token for downstream calls.
Orders
/ordersList orders and tasks with filters for team, status, service plan, time window, and external ID.
Orders
/create_orderCreate a new delivery order from your OMS, including recipient, address, items, and scheduled time window.
Dispatch
/assign_driverAssign a driver or vehicle to an order and trigger dispatch into Own Fleet or a Delivery Hub carrier.
Fleet
/vehiclesRetrieve a paginated list of vehicles, or a specific vehicle by ID or external ID, across teams.
Tracking
/trackingPull real-time driver location, check-in/arrival, and order status updates for active deliveries.
Use Cases
Sync delivery orders from OMS to Bringg
- Push new orders, recipients, and items from your order management system into Bringg - Pull order and task status changes back into your warehouse and customer notifications - Reconcile external IDs across owned and third-party fleet deliveries
Automate dispatch and driver assignment
- Assign drivers and vehicles to orders programmatically without portal clicks - Route deliveries to the optimal Own Fleet driver or Delivery Hub carrier - Trigger re-dispatch on exceptions, cancellations, or SLA risk
Stream real-time tracking and visibility
- Pull driver location, check-in, and arrival events into customer-facing tracking pages - Feed status milestones into BI and operations dashboards - Alert on late, failed, or delayed deliveries across regions
Keep fleet and team data in sync
- Create and update vehicles, drivers, and teams from your VMS and HR systems - Pull fleet utilization and performance data for reporting and payroll - Maintain parking spots, locations, and team associations programmatically
Technical Specifications
Authentication
OAuth 2.0 with scoped application access, handled in a managed session with automatic token refresh
Connectivity
Bringg REST APIs (v1.0 Own Fleet and v2.0 Delivery Hub) plus authenticated flows where needed
Response format
Normalized JSON across Orders, Tasks, Drivers, Vehicles, Teams, and Tracking objects
Rate limits
Adaptive throttling tuned to Bringg's request limits to avoid carrier-side rejections
Session management
Automatic OAuth token refresh, scope re-acquisition, and credential rotation
Data freshness
Near real-time pulls for orders, tracking, and status with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for order creation, dispatch, status change, check-in, and delivery completion
Latency
Sub-second reads on cached entities; multi-second writes when creating orders and dispatching
Throughput
Horizontally scaled workers sized to high-volume order and real-time tracking workloads
Reliability
Retry, backoff, and idempotency keys for order creation, assignment, and status updates
Adaptation
Continuous monitoring of Bringg API releases, regional endpoint changes, and tenant configuration drift
Frequently asked questions
Yes. Supergood normalizes data across Bringg's v1.0 Own Fleet and v2.0 Delivery Hub solutions, so orders, tasks, drivers, and tracking are exposed through one consistent surface regardless of which model you run.
Supergood automatically routes to the correct regional admin API domain (US2, US3, EU2, EU3) based on your tenant, so you don't have to manage region-specific base URLs yourself.
No. Supergood handles OAuth 2.0 token acquisition and the application scopes your workflows require, managing refresh and rotation inside a secure session.
Yes. Driver location, check-in, and arrival events are surfaced through the API and via webhooks, with handling for Bringg's frequent update cadence and request limits.
Yes. Deliveries dispatched to third-party, crowdsourced, and autonomous carriers in the Bringg Network are normalized alongside Own Fleet orders so you integrate once across all fleet types.