Bringg

Bringg Authentication API

The Authentication API from Bringg — 2 operation(s) for authentication.

Documentation GitHub OpenAPI

Operations 2

POST /partner/get-token Get Token #

GET /partner/merchant-credentials Get Merchant Credentials #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/bringg-authentication-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Bringg Fleet Partners (Self-Integrated Fleets) Authentication API
  version: '1.0'
  description: 'Bringg''s Fleet Partners API is the integration surface for delivery providers

    and self-integrated fleets connecting to the Bringg Delivery Hub. Partners

    implement webhook endpoints Bringg calls (Delivery Created, Get Quote, Order

    Updated, Order Cancelled, Return Delivery Created, Merchant Registered) and

    expose endpoints for accepting orders, updating order status, posting driver

    locations, adding proof of delivery, and managing tokens / merchant credentials.

    Authentication is OAuth 2.0 plus per-partner shared secrets for webhook

    signature verification.

    '
  contact:
    name: Bringg Developer Support
    url: https://developers.bringg.com
  license:
    name: Bringg API Terms of Service
    url: https://developers.bringg.com/reference/terms-of-service
servers:
- url: https://app.bringg.com
  description: Bringg security gateway
- url: https://partner.example.com
  description: Partner-hosted endpoints (replace with your base URL for callbacks)
security:
- OAuth2ClientCredentials: []
tags:
- name: Authentication
paths:
  /partner/get-token:
    post:
      summary: Get Token
      description: Exchange partner credentials for an access token used to call Bringg from the partner side.
      tags:
      - Authentication
      operationId: getToken
      responses:
        '200':
          description: Token returned.
  /partner/merchant-credentials:
    get:
      summary: Get Merchant Credentials
      description: Retrieve merchant-specific credentials issued by Bringg to the fleet partner.
      tags:
      - Authentication
      operationId: getMerchantCredentials
      responses:
        '200':
          description: Credentials returned.
components:
  securitySchemes:
    OAuth2ClientCredentials:
      type: oauth2
      description: OAuth 2.0 Client Credentials Grant. Webhook callbacks are signed with a shared secret.
      flows:
        clientCredentials:
          tokenUrl: https://admin-api.bringg.com/oauth/token
          scopes:
            request_driver: Request driver fulfillment
            cancel_order: Cancel orders
            complete_order: Complete orders
            update_driver_location: Update driver location

Bringg Authentication API

Operations 2

Documentation

Specifications

Schemas & Data

Other Resources