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 – Home mailbox parcel (3584) & Home mailbox parcel RFID (3570) – Change of default fallback delivery
21 January 2026 Important
From 26.01.2026, the default fallback behaviour for Home mailbox parcel will change.
If the shipment does not fit in the recipient’s mailbox, the parcel will by default be left outside the recipient’s door.
Previously, the default fallback was delivery to pickup point.
What this means for you
VAS 1081 (Delivery outside the door) is no longer required in the request.
Recipients can still change delivery preferences in the Posten app.
Restricting delivery outside the door
If you do not want parcels to be left outside the recipients door, you can still reserve against this by adding VAS 1280 (Signature require) in the request. This ensures that shipments not fitting in the mailbox are redirected to pickup points.
Shipping Guide API – Shipping Guide API - Home mailbox parcel (3584) & Home mailbox parcel RFID (3570) – Change of default fallback delivery
21 January 2026 Important
From 26.01.2026, the default fallback behaviour for Home mailbox parcel will change.
If the shipment does not fit in the recipient’s mailbox, the parcel will by default be left outside the recipient’s door.
Previously, the default fallback was delivery to pickup point.
What this means for you
VAS 1081 (Delivery outside the door) is no longer required in the request.
Recipients can still change delivery preferences in the Posten app.
Reports API – Replacement of Emission Report Type IDs
9 December 2025 Important
From 09.12.2025, new emission reports are available in the Reporting API. These reports follow the principles of the ISO 14083:2023 standard for emission calculations and include data from 2025 and onwards.
The existing emission reports remain available for existing API users for now, but they will no longer receive new data. December 2025 data and all future data will only be available through the new reports.
We expect to decommission the old emission report types in early 2026, and they will only be kept available for a limited transition period.
Report type IDs no longer receiving updates
These reports remain accessible for historical data only:
ENVIRONMENT_REPORT_PER_CONSIGNMENTENVIRONMENT_REPORT_PER_MONTHCARGO-ENVIRONMENT_REPORT_PER_CONSIGNMENTCARGO-ENVIRONMENT_REPORT_PER_MONTHENVIRONMENT_REPORT_INTERNATIONAL_PER_CONSIGNMENTENVIRONMENT_REPORT_INTERNATIONAL_PER_MONTH
New report type IDs (use these going forward)
PARCELS_EMISSIONS_PER_SHIPMENTPARCELS_EMISSIONS_PER_MONTHCARGO_EMISSIONS_PER_SHIPMENTCARGO_EMISSIONS_PER_MONTHPARCELS_INTERNATIONAL_EMISSIONS_PER_SHIPMENTPARCELS_INTERNATIONAL_EMISSIONS_PER_MONTH
What this means for you
To continue receiving updated emissions data, we recommend moving your integrations to the new report type IDs as soon as possible. The old report types will remain callable, but only for historical data and only for a limited time.