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 numbers, tracking links, EDI-prenotifications, labels and other transport documents.
Tracking
Track your shipments’ events or subscribe to them, and proactively share updates with your customers through webhooks. Modify or stop shipments that are already in transit.
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.
Analytics
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
E-commerce platform plugins
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 - Return mailbox parcel (9650) decommissioning
On September, 1, Bring is decommissioning the service Return mailbox parcel (9650).
We strongly recommend transitioning to start using alternative return services in Norway (9350, 9300) as soon as possible, as booking of 9650 will not be possible shortly after this date.
This is the case for both of the following scenarios:
- return bookings of 9650
- combined outbound + return bookings of 3584 and 9650 together, using the
returnProduct
element
Postal Code API - removal of po_box_only query param
On 15 August, the po_box_only query parameter will be removed from the Postal Code API.
It is replaced by a new, more flexible parameter: postal_code_type. This new parameter allows filtering by postal code type using the following values: PO_BOX, STREET_ADDRESSES, COMBINED, SPECIAL_SERVICE. The API response format remains unchanged.
If you currently use po_box_only, please update your integration to use postal_code_type by 15 August to ensure uninterrupted service. You can read more about the Postal Code API here
Tracking API - Hiding of Pickup Code
Starting Thursday, 24 April, the pickup code will be hidden in the Tracking API for senders. As the pickup code is considered personal information for the receiver, we are making this change to comply with GDPR regulations. If the pickup code is needed, the sender can use the Mybring Tracking portal to request the pickup code for each shipment. All such requests will be logged in a GDPR-compliant manner.