OAuth 2.0 URLs

Access Bringg's API using either service or OAuth 2.0 URLs. Generate unique service URLs in the Bringg platform, or use the OAuth 2.0 format detailed below.

Before you begin, follow the steps in Bringg API Access Management to obtain an authentication token.

---

All Bringg OAuth 2.0 URLs are structured as follows:https://< domain >/services/< service name identifier >.

• < domain > is based on the relevant Bringg distributed server.
• All Bringg API URLs include/services/ after the domain and before the endpoint-specific identifier.
• < service name identifier > is unique to each Bringg endpoint. See the complete list below.

For example, the OAuth 2.0 URL for the Create Order endpoint using the US2 server looks like this:
<https://us2-admin-api.bringg.com/services/create_task>

📘

API Domains and Regional Endpoints

Each Bringg merchant (and its associated data) is hosted and managed on one of Bringg's distributed server regions. Each server region is geographically and physically separated from the others, but for most purposes, public access is via a common, security gateway: app.bringg.com.

For some API purposes however - such as for OAuth 2.0 - it may be required to call your own server region's endpoints directly. In these cases, please substitute the domains as follows:

US2: https://us2-admin-api.bringg.com
US3: https://us3-api.bringg.com
EU2: https://eu2-admin-api.bringg.com
EU3: https://eu3-admin-api.bringg.com