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.

Shipping Guide API Pickup Point API Address API Postal Code API

Booking

Create shipments and generate shipment numbers, tracking links, EDI-prenotifications, labels and other transport documents.

Booking API Pickup API Shipment API Bulksplit API Customs API Customer Info API

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.

Tracking API Event Cast API Modify Delivery API

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.

Send updates Receive updates Pull order/article

Analytics

Generate status, quality and deviation, economy and environment reports to analyse your logistics with Bring. List and retrieve invoices in PDF format.

Reports API Invoice API Documents API

Order Management

For integrated customers, their suppliers and Bring to exchange order level information across the life cycle of customers' orders.

Order Management API

Checkout resources

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

Pickup Point API – Deprecation of path suffix based content negotiation

19 June 2026 Important

Support for content negotiation using URL path suffixes .json or .xml (for example /api/pickuppoint/NO/postalCode/0174.json and /api/pickuppoint/NO/postalCode/0174.xml) is deprecated and will be removed in a future release.

Recommended Alternative

Clients should instead specify the desired response format using the HTTP Accept header:

JSON:

GET /api/pickuppoint/NO/postalCode/0174
Accept: application/json

XML:

GET /api/pickuppoint/NO/postalCode/0174
Accept: application/xml

Why This Change?

Path suffix-based content negotiation is no longer recommended and is not supported by default in newer versions of the underlying framework. Continuing to support this behavior requires custom compatibility code that will be removed in a future release.

Using standard HTTP content negotiation via the Accept header improves interoperability, aligns with current web standards, and ensures compatibility with future platform upgrades.

Removal Timeline

Support for .json and .xml URL suffixes is not yet scheduled for removal in a future release, but we recommend updating all integrations as soon as possible to avoid service disruption.

Shipping Guide API – Deprecation of path suffix based content negotiation