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 Orders API

The Orders API from Bringg — 22 operation(s) for orders.

Bringg Orders 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 Order. 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 22 operations across 22 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.

22 operations 22 paths 0 schemas 4 GET18 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 Orders 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 22

Across 22 paths, the API surfaces 22 operations — 4 GET, 18 POST. Each is listed below with its method, path, parameters, and response codes.

Orders 22
POST
/services/create_task
Create Order
createTask → 200
POST
/services/update_task
Update Order
updateTask → 200
GET
/services/get_task
Get Order
getTask → 200
GET
/services/get_open_tasks
Get Open Orders
getOpenTasks → 200
GET
/services/get_post_optimization_tasks
Get Post-Optimization Orders
getPostOptimizationTasks → 200
GET
/services/get_open_orders_by_customer
Get Open Orders by Customer
getOpenOrdersByCustomer → 200
POST
/services/start_task
Start Order
startTask → 200
POST
/services/end_task
End Order
endTask → 200
POST
/services/cancel_task
Cancel Order
cancelTask → 200
POST
/services/update_task_external_id
Update Order External ID
updateTaskExternalId → 200
POST
/services/create_task_refund
Create Order Refund
createTaskRefund → 200
POST
/services/create_task_payment_history
Create Order Payment History
createTaskPaymentHistory → 200
POST
/services/checkin
Check-in (Arrived to Destination)
checkIn → 200
POST
/services/checkout
Check-out (Left Destination)
checkOut → 200
POST
/services/mass_checkout
Multi-Order Checkout
massCheckout → 200
POST
/services/release_tasks
Release Orders
releaseTasks → 200
POST
/services/assign_task
Assign Order To Driver
assignTask → 200
POST
/partner/request-driver
Request Driver
requestDriver → 200
POST
/partner/cancel-order
Cancel Order
cancelOrder → 200
POST
/partner/complete-order
Complete Order
completeOrder → 200
POST
/partner/update-order
Update Order
updateOrder → 200
POST
/partner/start-order
Start Order
startOrder → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bringg-orders-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 Drivers API
Bringg Floating Inventory API
Bringg Inventory API
Bringg Notes API
Where this information came from

This is an independent, third-party profile of Bringg Orders 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.