Receive order/article update
Updates
System maintenance
21 October 2025General
On 26 October we will do some system maintenance that will affect our APIs. You might experience some outage between 07:00 and 09:00 Sunday 26 October.
Important Update! New TLS certificates on api.bring.com 27th of October 2025
26 September 2025General
Migration from Buypass to Let’s Encrypt TLS Certificates As of 15 September 2025, Buypass has stopped allowing registration of new ACME Account and will stop generating/renewing TLS certificates from 15th October 2025. To ensure continuity, we are migrating all TLS certificates from Buypass to Let´s Encrypt.
As part of this activity:
- Old Buypass certificates will be removed
- New Let´s Encrypt certificates will be created
Impact to Customers:
- If your application does not pin the certificate, no action is required and there will be zero impact.
- If your application does pin the certificate, you will need to download the new Let´s Encrypt certificate and update your application configuration accordingly.
We recommend reviewing your applications to check whether certificate pinning is in place and preparing for updates if needed.
For more queries, contact integrasjon.norge@bring.com (Norway) or edi@bring.com (outside Norway).
Older updates
Note! Removal of temporary domain api-new.bring.com
11 January 2023General
From 19 January 2023, APIs hosted on api-new.bring.com will stop working. Please start using api.bring.com instead of api-new.bring.com.
For more queries contact to integrasjon.norge@bring.com (Norway) or edi@bring.com (outside Norway).
Upcoming DNS change 1st of April 2022
21 December 2021General
Bring’s applications and infrastructure are going through bigger changes, as part
of modernizing our infrastructure. One of these changes, is update of our
load balancing component, and that will affect services running on api.bring.com.
Be sure to verify your integration before the change to ensure no service disruption.
EDI documentation
8 June 2021General
New versions of the documents Appendix2 Available Services and Appendix 2A Instructions for service Implementation
Warehousing API
21 January 2019
Added new attribute OrderItem/ArticleMonetaryAmounts that contains the article
unit sales price.
Warehousing API
11 March 2018
The Order Management API split out of the Warehousing API. These will now continue as two separate APIs.
Order information/update from Bring. Bring Warehousing can send order information to you or you can pull the data from us. How often you want order lifestyle updates is up to you. Bring Warehousing can also send you Inventory reports (full overview over all articles) and Inventory adjustment reports (update per article after an adjustment is made).
Authentication
In order for us to make API requests to you, you will need to send us an API key from your web service site. Steps for getting a key and description of headers should be similar to ours and can be found on the general API Getting Started page.
Formats
REST XML/JSON over HTTPS. This is common for most REST APIs.
Order Information
In order to obtain information about an order/get the receipt for an order, you have two options:
- You can obtain data from Mybring.
- We can push data to you if you set up a webservice on your side
You should use a REST web service which needs to be secured through https.
After you have set up your web service, you must send the information about the URL and its authentication to us, so that we can set up a link from our side.
The data sent from Bring will be in GS1 3.3 format. General information about GS1 3.3 can be found here: https://www.gs1.org/standards/gs1-xml/3-3
Authentication
Bring supports https with basic username and password authentication.
Message header authorization options:
- Authorization: Basic bWFnZ2llOnN1bW1lcnM = ???? or
- API key: X-API-KEY: abcdef12345
Verification
Your webservice must verify and return a response to us that the message was received ok.
Your response will have to follow the format below. It's important that the following is set in the response:
- Message must be equal to success
- Request ID has to be a unique ID for each message.
Response Example
| XML Sample | JSON Sample |
Response Schema
| XML Schema |