Lead time
Lead time depends on the recipient’s postal code and address
Two different addresses on the same postal code can have different lead time. We have therefore added an addressLine field, which allows lead time to be calculated based on both postal code and street address. For this to work, it is important that recipients fill out a valid street address.
By using our Address API for Norwegian addresses, the address the recipients fill inn can be pre-validated, which will ensure more accurate lead times. We therefore recommend using the Address API in combination with Shipping Guide API.
<ns:AddressLine>Testsvingen 12</ns:AddressLine>
{
"addressLine": "Testsvingen 12"
}
Pickup agreement also affects lead time
In the absence of a pickup agreement with Bring, you hand in the shipment yourself at one of our manned drop-off points.
Handing in at some places can add an extra day to the delivery time. Hence, to ensure more accurate lead times, we recommend relaying the aforementioned information to us via field postingAtPostoffice in your request.
Estimated arrival time for domestic and cross-border parcel and cargo services
The API offers estimated arrival time information for a range of Norwegian and cross-border parcel and cargo services. This gives your customers a better understanding of when to expect their deliveries.
The API can return lead time in two different ways:
expectedDelivery— the normal delivery estimate for parcel and cargo services.estimatedDeliveryTimes— pickup-point arrival times for services that support them.
Which one you get depends on the request flags you set and whether you provide pickup point IDs.
Which one should I use?
| I want to show… | Response field | Set these request flags |
|---|---|---|
| A delivery date for a shipment | expectedDelivery |
withExpectedDelivery=true |
| A delivery date plus an arrival window | expectedDelivery with timeSlots |
withExpectedDelivery=true |
| Pickup-point arrival windows, if available, otherwise a normal delivery estimate | estimatedDeliveryTimes or expectedDelivery |
withExpectedDelivery=true and withEstimatedDeliveryTime=true |
Supported services
The services below are the ones covered by this page. Use them as the reference set when you choose between expectedDelivery and estimatedDeliveryTimes.
Norwegian domestic services
These services return ETA within Norway:
- Business parcel (5000)
- Business groupage (5100)
- Business pallet (5400)
- Parcel Home plus (5600)
- Pickup Parcel (5800)
- Parcel Locker (5801)
- Mailbox parcel (3584/3570)
Cross-border services
These services return ETA within and across Scandinavian countries:
- Business Parcel (0330)
- Business Parcel Bulk (0332)
- Business Pallet (0336)
- Pickup Parcel (0340)
- Pickup Parcel Bulk (0342)
- Home delivery services
- Express and courier services
What to send in the request
- Set the actual
shippingDateif you have it. Lead time is calculated from the day and time the parcel arrives at a Bring terminal. - If no shipping date is provided, the API uses
now. - Read this guide if you want more background on how shipping date affects the estimate.
Response summary
| Case | Response field | What it means |
|---|---|---|
| Standard lead time | expectedDelivery |
Returns the normal delivery estimate. When the model can predict an arrival window, expectedDeliveryDate.timeSlots is included. |
| Pickup-point lead time | estimatedDeliveryTimes |
Returned when withExpectedDelivery=true and withEstimatedDeliveryTime=true. This applies to 5800 and 5801. |
If you request pickup-point lead time with withEstimatedDeliveryTime=true, but the API cannot calculate an arrival window for the requested pickup point(s), it falls back to expectedDelivery.
expectedDelivery: standard lead time
For supported parcel and cargo services, the API predicts an arrival window: when the shipment is expected to arrive at the recipient address.
The window is returned automatically when withExpectedDelivery is true.
When the model can predict an arrival window, the response includes timeSlots:
{
"expectedDelivery": {
"workingDays": "2",
"formattedExpectedDeliveryDate": "25.06.2026",
"expectedDeliveryDate": {
"year": "2026",
"month": "6",
"day": "25",
"timeSlots": [
{
"startTime": {
"hour": "8",
"minute": "0"
},
"endTime": {
"hour": "17",
"minute": "0"
}
}
]
}
}
}
When it cannot, the response still includes the date, but without timeSlots:
{
"expectedDelivery": {
"workingDays": "2",
"formattedExpectedDeliveryDate": "25.06.2026",
"expectedDeliveryDate": {
"year": "2026",
"month": "6",
"day": "25"
}
}
}
The minutes are always 0, so you only need to use the hours.
Suggested checkout text:
- NO: Forventet levert (dato) mellom kl. X og Y
- EN: Expected delivered (date) between X and Y
Bring cannot guarantee a specific arrival time. The estimate shows when the parcel normally arrives, based on historical scanning data.
estimatedDeliveryTimes: pickup-point arrival window
For pickup-point services (5800 and 5801), the API can return the arrival window for one or more pickup points.
Set both flags:
withExpectedDelivery=truewithEstimatedDeliveryTime=true
You can then do one of two things:
- Provide pickup point IDs in the request to get estimates for specific pickup points.
- Omit
pickupPointsto let the API use the recipient’s default pickup point(s) based on postal code.
Example request fragment:
{
"pickupPoints": [
{
"id": "112306"
},
{
"id": "112073"
}
]
}
The response uses estimatedDeliveryTimes instead of expectedDelivery:
{
"estimatedDeliveryTimes": [
{
"pickupPointId": "112306",
"pickupPointName": "Pakkeboks KIWI Son",
"deliveryStartTime": "12:00",
"deliveryEndTime": "15:00",
"formattedExpectedDeliveryDate": "25.06.2026",
"shippingDate": "24.06.2026",
"workingDays": 1
},
{
"pickupPointId": "112073",
"pickupPointName": "Pakkeboks KIWI Sletta",
"deliveryStartTime": "12:00",
"deliveryEndTime": "15:00",
"formattedExpectedDeliveryDate": "25.06.2026",
"shippingDate": "24.06.2026",
"workingDays": 1
}
]
}
Each item represents one pickup point. If the pickup-point estimate cannot be calculated, the API falls back to expectedDelivery.
Suggested checkout text:
- NO: Pakken ankommer vanligvis mellom kl. X og Y
- EN: The parcel usually arrives between X and Y
Combined with the date:
- NO: Forventet levert XX.XX.20XX. Pakken ankommer vanligvis mellom kl. X og Y
- EN: Expected delivered XX.XX.20XX. The parcel usually arrives between X and Y
Bring cannot guarantee the arrival time for a specific parcel. The estimate shows when the parcel normally becomes available for pickup at the selected pickup point on that date.
Get alternative expected delivery dates
To get the x next possible delivery dates, use the numberOfAlternativeDeliveryDates parameter. Note that this feature is only relevant for a few services (5600, 0336, 3584, 5300 and 9100)
{
"numberOfAlternativeDeliveryDates": 2
}
Note: make sure the numberOfAlternativeDeliveryDates is also set to some positive value. The maximum number of alternative delivery days that can be requested is 9.
There is no guarantee that the requested number of alternative delivery days will be returned as this depends on availability.