New Warning in API - Split BL

We’ve added a new warning type to container tracking: splitBL. It helps you detect when containers under the same BL or BK may be split across different vessels, ports, or timelines — a situation that often leads to confusion and downstream issues.

🧠 Why it matters

Sometimes, containers booked under the same BL/BK don’t move together. This can happen for many operational reasons (e.g. vessel omissions, transshipment delays), but the outcome is the same: your shipment appears to “split” unexpectedly. With the new splitBL warning, you can detect this earlier and take action proactively.

⚙️ How it works

We trigger the splitBL warning when containers under the same BL or BK show diverging tracking data:

• One container has more (or fewer) tracking events than the others
• Containers are associated with different vessels or locations

Container Tracking API

• The warning appears in the metadata.warnings array for each container.

Webhooks

• The warning appears in the metadata.warnings array inside each container's data.
• You can subscribe to a new event: shipment.warning.split_bl, which triggers when the warning appears for the first time in the tracking data.