Integrate your systems with Bring
Developing an e-commerce site? Or dealing with logistics software in the Nordic countries? Find out how to integrate with Bring’s API platform.
Get started →Explore our APIs
Checkout
Look up available services, delivery times, prices and environmental data. Verify addresses and let users pick the closest pickup point. And use our recommended service descriptions in your checkout.
Booking
Create shipments and generate shipment number, tracking link, EDI-prenotification, label and other transport documents. Modify certain shipments that are on their way, and order pickup.
Tracking
Look up tracking events of your shipments, or subscribe to them, and make them proactively available to your customers through webhooks.
Warehousing
E-commerce customers in Norway and Sweden, for whom we handle storage and logistics, can submit and retrieve order and article information in Bring’s warehouses.
Reports and invoices
Generate status, quality and deviation, economy and environment reports to analyse your logistics with Bring. List and retrieve invoices in PDF format.
Order Management
For integrated customers, their suppliers and Bring to exchange order level information across the life cycle of customers' orders.
Checkout resources
Best practice checkout guide
Checkout tool
EDI documentation
Guidelines and specifications for vendors of TA/EDI solutions and customers with first-party EDI solutions, including transport instructions for integrations based on EDIFACT (IFTMIN D04A) standards.
EDI documentation →API updates
: Booking API - Deprecation of SOAP endpoint
The SOAP endpoint is now deprecated. Going forward the API will only support application/json and application/xml
as Content-Type.
If you are currently relying on the SOAP endpoint of Booking API, you have until 1 October 2024 to migrate to the JSON/XML over HTTP based endpoints.
We will start rate limiting requests to the SOAP endpoint from 1 September 2024, with gradually reduced request rate until 1 October. This means that you will risk rejected requests because of rate limiting after 1 September
: Shipping Guide API - Deprecation of SOAP endpoint
The SOAP endpoint is now deprecated. Going forward the API will only support application/json and application/xml
as Content-Type.
If you are currently relying on the SOAP endpoint of Shippingguide API, you have until 1 October 2024 to migrate to the JSON/XML over HTTP based endpoints.
We will start rate limiting requests to the SOAP endpoint from 1 September 2024, with gradually reduced request rate until 1 October. This means that you will risk rejected requests because of rate limiting after 1 September
: Tracking API – Starting from 2nd of May, 2024, we will reject browser calls associated with a customer number to enhance security.
We have discovered some API users exposing username and API key openly in the source code of their website. This means that this information is accessible to anyone with a certain level of technical expertise. This poses a security risk as it allows unauthorized access to information about agreements with Posten Bring, as well as GDPR-sensitive customer data.
To address this, we strongly recommend that you call our Tracking API from the backend instead of via the browser. This way, this information will not be exposed. We advise you to promptly delete the current API key and generate a new one here: https://www.mybring.com/useradmin/account/settings/api
If it is not feasible to call our APIs from the backend and you are entirely dependent on doing so via the browser, we recommend creating a new user account not associated with your customer numbers. You can create such an account here: https://www.mybring.com/useradmin/account/settings/api
Please note that starting from May 2, 2024, we will reject browser calls associated with a customer number to enhance security.