API updates
You can also subscribe to our RSS feed.
System maintenance
21 October 2025General
On 26 October we will do some system maintenance that will affect our APIs. You might experience some outage between 07:00 and 09:00 Sunday 26 October.
Important Update! New TLS certificates on api.bring.com 27th of October 2025
26 September 2025General
Migration from Buypass to Let’s Encrypt TLS Certificates As of 15 September 2025, Buypass has stopped allowing registration of new ACME Account and will stop generating/renewing TLS certificates from 15th October 2025. To ensure continuity, we are migrating all TLS certificates from Buypass to Let´s Encrypt.
As part of this activity:
- Old Buypass certificates will be removed
- New Let´s Encrypt certificates will be created
Impact to Customers:
- If your application does not pin the certificate, no action is required and there will be zero impact.
- If your application does pin the certificate, you will need to download the new Let´s Encrypt certificate and update your application configuration accordingly.
We recommend reviewing your applications to check whether certificate pinning is in place and preparing for updates if needed.
For more queries, contact integrasjon.norge@bring.com (Norway) or edi@bring.com (outside Norway).
Tracking API - Hiding of Flex image
17 September 2025 Important
Starting Monday 22nd of September, the flex image will be hidden in the Tracking API. As the flex image is considered personal information, we are making this change to reduce risk of personal information being available in the Tracking API to be GDPR compliant. If the flex image is needed, the sender can use the Mybring Tracking portal to request the flex image for each shipment. All such requests will be logged in a GDPR-compliant manner.
Event Cast API - Webhook moderation for admin users
16 September 2025
Admin users can now moderate any webhook registered on their customer number. This includes viewing, renewing, and deleting webhooks created by themselves or other users.
To support this, we’ve introduced a new API endpoint that returns all registered webhooks associated with the customer numbers linked to the user making the request.
- Customer admin users will receive a list of all webhooks related to their customer number.
- Non-admin users will only see the webhooks they have created.
The endpoint specifications can be seen under the Event Cast API.
Tracking API - Hiding of Pickup Code
2 April 2025 Important
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.
Older updates
Event Cast API - Subscription on customer numbers
19 June 2024 Important
Starting June 19, 2024, the Event Cast API will support subscriptions on customer numbers. This new feature complements the existing functionality to subscribe on shipment or parcel numbers and does not replace them.
With customer number subscriptions, you’ll automatically receive updates for all shipments registered on that customer number, removing the need to manage individual subscriptions for each new shipment or parcel. These subscriptions will have a validity of one year.
To start using the new customer number subscription, please see to the updated Event Cast API documentation.
Tracking API - Deprecation of Unauthenticated requests
13 May 2024 Important
Starting from May 13th, unauthenticated requests will no longer have access to the Tracking API. Previously, we implemented rate limiting measures. Read here on how to make authenticated requests.
If you see following error message that means you are not sending authenticated requests.
401 - Unathorized. The Tracking API no longer supports unauthenticated requests. Make sure your requests are authenticated. Read more about this on our Bring developer site. https://developer.bring.com/api/tracking/
Tracking API – Starting from 2nd of May, 2024, we will reject browser calls associated with a customer number to enhance security.
25 March 2024 Important
We have discovered some API users exposing username and API key openly in the source code of their website. This means that this information is accessible to anyone with a certain level of technical expertise. This poses a security risk as it allows unauthorized access to information about agreements with Posten Bring, as well as GDPR-sensitive customer data.
To address this, we strongly recommend that you call our Tracking API from the backend instead of via the browser. This way, this information will not be exposed. We advise you to promptly delete the current API key and generate a new one here: https://www.mybring.com/useradmin/account/settings/api
If it is not feasible to call our APIs from the backend and you are entirely dependent on doing so via the browser, we recommend creating a new user account not associated with your customer numbers. You can create such an account here: https://www.mybring.com/useradmin/account/settings/api
Please note that starting from May 2, 2024, we will reject browser calls associated with a customer number to enhance security.
Deprecation of Unauthenticated Open Tracking API
31 May 2023
Our customers are increasingly demanding new functionality and solutions that are easy to use. To meet these expectations, we must know which customers and partners are using our APIs and how they are using them. To further develop the value proposition of our Tracking API, the solution will require authentication. Read here on how to make authenticated requests.
From 15 August 2023, we will start rate liming the requests.
If you see following error message that means you are being rate limited, and you should start using authenticated requests.
429 - Too many requests. We are now rate limiting our unauthenticated users, to prevent this make sure your requests are authenticated. Read more about this on our Bring developer site. https://developer.bring.com/api/tracking/
Note! Removal of temporary domain api-new.bring.com
11 January 2023General
From 19 January 2023, APIs hosted on api-new.bring.com will stop working. Please start using api.bring.com instead of api-new.bring.com.
For more queries contact to integrasjon.norge@bring.com (Norway) or edi@bring.com (outside Norway).
Tracking API
23 June 2022
The event statuses ARRIVED_COLLECTION and ARRIVED_DELIVERY are not valid anymore, and therefore have been removed from the Tracking API.
Tracking API
22 June 2022
Starting 1 August 2022, Tracking API version v1 will be deprecated and the requests will be automatically forwarded to the latest version, v2. It is not a breaking change. In the new version you will have access to many more fields.
Tracking API
4 February 2022
As an increased security measure, we have hidden the pickup code from the open Tracking API. The logged in Tracking API will still contain the pickup code.
Upcoming DNS change 1st of April 2022
21 December 2021General
Bring’s applications and infrastructure are going through bigger changes, as part
of modernizing our infrastructure. One of these changes, is update of our
load balancing component, and that will affect services running on api.bring.com.
Be sure to verify your integration before the change to ensure no service disruption.
Tracking API
8 December 2021
The Tracking API now includes the details of the expected pickup point, where an item is expected to arrive. It contains expected pickup-point-unit id, name and URL(a link to detailed information of pickup point like location, opening hours, etc).
EDI documentation
8 June 2021General
New versions of the documents Appendix2 Available Services and Appendix 2A Instructions for service Implementation
Tracking API
19 April 2021
The Tracking API now includes estimated arrival time window of delivery for supported shipments.
Event Cast API
6 October 2020
Updated maximum length limit for header, also added the maximum length information for id, authenticator, content type and URL.
Event Cast API
7 July 2020
Added support for new request parameter limit. This can be used to limit the
number of latest webhooks returned.
Event Cast API
2 September 2019
Released Event Cast API, an API for getting event updates pushed instead of polling tracking.