How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bringg Drivers API

The Drivers API from Bringg — 15 operation(s) for drivers.

Bringg Drivers API is one of 30 APIs that Bringg publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Drivers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, a getting-started guide, an AsyncAPI specification, and 6 JSON Schemas.

This API exposes 15 operations across 15 paths. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 7 base URLs: https://us2-admin-api.bringg.com, https://us3-admin-api.bringg.com, https://us4-admin-api.bringg.com, https://eu2-admin-api.bringg.com, https://eu3-admin-api.bringg.com, https://app.bringg.com, https://partner.example.com.

15 operations 15 paths 0 schemas 1 DELETE3 GET11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://us2-admin-api.bringg.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Bringg Drivers API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2ClientCredentials) using the clientCredentials flow, exposing 13 scopes. By default, every request must be authenticated.

  • OAuth2ClientCredentials — OAuth 2.0 Client Credentials Grant. Exchange your clientid and clientsecret for an access token via POST https://admin-api.bringg.com/oauth/token (or the regio…

Paths & Operations 15

Across 15 paths, the API surfaces 15 operations — 1 DELETE, 3 GET, 11 POST. Each is listed below with its method, path, parameters, and response codes.

Drivers 15
POST
/services/assign_task
Assign Order To Driver
assignTask → 200
POST
/services/assign_run_driver
Assign Driver To Route
assignRunDriver → 200
POST
/services/unassign_run_driver
Unassign Driver From Route
unassignRunDriver → 200
POST
/services/create_blacklisted_customer_user
Create Blacklisted Customer Driver
createBlacklistedCustomerUser → 200
DELETE
/services/delete_blacklisted_customer_user
Delete Blacklisted Customer Driver
deleteBlacklistedCustomerUser → 200
GET
/services/get_blacklisted_customer_users
Get Blacklisted Customer Drivers
getBlacklistedCustomerUsers → 200
POST
/services/logoff_user
Logoff Driver
logoffUser → 200
POST
/services/generate_driver_qr_code
Generate Driver QR Code
generateDriverQrCode → 200
POST
/services/generate_pickup_qr_code
Generate Pickup QR Code
generatePickupQrCode → 200
POST
/services/driver_home_events
Initiate Driver Home Events
driverHomeEvents → 200
GET
/services/get_realtime_availability
Get Driver Availability
getRealtimeAvailability → 200
POST
/services/update_driver_location
Update Driver Location
updateDriverLocation → 200
POST
/partner/driver-is-assigned-to-order
Assign Driver
driverIsAssignedToOrder → 200
POST
/partner/update-driver-location
Update Driver Location
partnerUpdateDriverLocation → 200
GET
/partner/driver-location
Driver Location
getDriverLocation → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bringg-drivers-api-openapi.yml Raw ↑

Other APIs Bringg publishes across the network.

Bringg Administration API
Bringg Analytics API
Bringg Authentication API
Bringg Blackouts API
Bringg Bulk API
Bringg Customers API
Bringg Delivery Blocks API
Bringg Delivery Slots API
Bringg Floating Inventory API
Bringg Inventory API
Bringg Notes API
Bringg Operations API
Where this information came from

This is an independent, third-party profile of Bringg Drivers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.