Using a different carrier? See Package Tracking.

Introduction

Zembula reads Bring tracking through Bring's Tracking API, with the API key of your own Mybring user. One connection covers Bring and Posten parcels.

Zembula uses the key only to read tracking. It never books shipments or changes anything in your Mybring account.

This guide covers creating the API key in Mybring and connecting it in the Zembula platform. You enter the key in Zembula yourself.

Who can do this

You need a Mybring user account. If you don't have one, register in Mybring. Bring says some companies keep a separate Mybring user just for API use. The account type is the same either way.

In Zembula, only account Admins can connect Bring. Other users can open the Package Tracking page, but they can't change it.

Before you go live

Bring doesn't publish a fixed call limit for its Tracking API. It refuses calls when too many arrive at once, and it can temporarily block requests after too many invalid ones.

Each time an image with Bring tracking loads, Zembula can ask Bring for the latest scans. So each email open can use a Bring call. When Bring refuses a call, the image can't show tracking for that load.

To avoid invalid requests, send only Bring and Posten tracking numbers with a Bring carrier value.

Create the API key

Sign in to Mybring at mybring.com.
Open the API page in your account settings: mybring.com/useradmin/account/settings/api.
Create an API key.
Copy the API key. You also need the email address you sign in to Mybring with.

Bring treats the API key like a password. Don't send it by email or chat. You enter it yourself in the Zembula platform in the next step.

If you change or delete the key, or delete the Mybring user, tracking stops until you paste a new key in Zembula.

Connect Bring in Zembula

In the Zembula platform, open Data Sync → Integrations and select the Data integrations tab.
Click Set up on the Package Tracking tile. If Package Tracking is already set up, the button reads Open instead.
If Package Tracking is off, click Turn on. The page shows Setting up the builder source… and then Use INTERFACES › Package Tracking in the builder.
Under Carriers, click Add on the Bring row.
The row lists API key and Mybring login email. Click Paste a key next to API key. The Paste your Bring keys dialog opens.
The dialog has two fields. Paste the key into API key, and type the email address you sign in to Mybring with into Mybring login email.
Click Connect.

The button reads Verifying… while Zembula saves your credentials. The Bring row then reads Connected — starts answering within the hour.

Zembula doesn't test the key with Bring when you connect. A wrong key or login email shows up later as missing tracking. Check it with Try it below.

If order data is live for Package Tracking, the Bring row reads Connected — waiting: carriers and order data can't run together until the next release. To switch, click Use Bring instead. This turns order data off and Bring on. Content that sends only an order ID then shows your fallback.

Try it

Add INTERFACES › Package Tracking to a draft image in the builder, turn on Simulate, and preview it with a Bring tracking number. If a number you know is real shows no tracking, check the key and the login email, and replace them if needed.

The Status section at the bottom of the Package Tracking page also lists anything that needs attention.

Using Bring in your content

Send each package's tracking number in tracking_number and the carrier in carrier. Zembula doesn't work out the carrier from the tracking number, so always send the carrier. You can also send a shipment number: Zembula then shows the whole shipment.

A carrier value that contains Bring as a word goes to Bring, in any case. For example: Bring, BRING or Bring Business Parcel. Posten Norge, POSTEN_NORGE, Posten Bring and POSTEN_BRING go to Bring too.

Posten on its own and Norway Post don't go to Bring. Send Bring or Posten Norge instead.

What shoppers see

Status: the latest scan Bring reports when the image loads, such as In Transit, Out for Delivery, Ready for Pickup or Delivered. Each scan shows Bring's English description. A scan Zembula can't classify reads In Transit.
Estimated delivery: a date, when Bring gives one. Zembula shows the date only, with no time window. After delivery it reads Delivered, with the delivery time.
Ready for Pickup: the pickup point's name, a link to it, and the date it holds the package until, when Bring gives them.
Several packages: when you send a shipment number for a shipment with more than one package, it doesn't read Delivered until every package is delivered.
Tracking link: the package's page on tracking.bring.com, or on sporing.posten.no for Posten packages.
No manage delivery link: Bring's tracking doesn't give one.

Zembula leaves out Bring's notices that a message was sent to the recipient. It also hides email addresses and phone numbers in scan descriptions.

Where your credentials are kept

The API key and your Mybring login email are saved as encrypted secrets. They can't be read back: the platform only shows their last four characters. They're listed under Data Sync → Secrets & Configs, and they can only be sent to Bring's API (api.bring.com).

Zembula calls Bring from its own servers, as Bring recommends. The key never appears in your emails or in a shopper's browser.

To change the key, open the Package Tracking page and click Replace key next to API key on the Bring row. To stop using Bring, click Disconnect. Bring still accepts the key until you delete it in Mybring.

More detail: Shared Secrets and Configs.