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.
E-commerce solutions
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
: Reports API - Delaying date of removal of REST endpoint
The removal of the following API endpoints:
- /reports/api/invoices/{customerOrGroupId}
- /reports/api/invoices/{customerOrGroupId}.json
- /reports/api/invoices/{customerOrGroupId}.xml
will be delayed to 1. September 2023.
the replacement API is documented here
: Reports API - Removal of REST endpoint
The following API endpoints will be removed from the Reports application after June 2023:
- /reports/api/invoices/{customerOrGroupId}
- /reports/api/invoices/{customerOrGroupId}.json
- /reports/api/invoices/{customerOrGroupId}.xml
the replacement API is documented here
: 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 March 2024 to migrate to the JSON/XML over HTTP based endpoints.
We will start rate limiting requests to the SOAP endpoint from 1 February 2024, with gradually reduced request rate until 1 March. This means that you will risk rejected requests because of rate limiting after 1 February