Getting Data Out
Integrations & API Access
What you can automate today — inbound email, calendar feeds, file exports, and ERP integration — and where a public API fits in.
4 min readLast updated
Goal
Work out whether Trackberry can connect to the system you have in mind, and which integration point to use.
Is there a public API?
Not yet. Trackberry does not currently offer a self-serve REST API, API tokens, or outbound webhooks. There is no endpoint you can point a script at, and no developer portal to generate credentials from.
We document this plainly because the alternative is worse: a page describing endpoints that don’t answer costs you an afternoon before you conclude the docs were wrong.
If a public API would change how you work with Trackberry, tell us what you’d build with it — email support@trackberry.com. Access is prioritised by what people actually need, so a concrete use case carries real weight.
What you can automate today
Plenty of Trackberry is already machine-readable. These are the integration points that exist and are supported.
| You want to… | Use | Direction |
|---|---|---|
| Get shipment documents into Trackberry automatically | Inbound email address | In |
| Keep arrival dates in Outlook, Google, or Apple Calendar | Calendar subscription feed (ICS) | Out |
| Pull a filtered shipment list into a spreadsheet | Excel download | Out |
| Push packing data into your ERP | ERP integration | Out |
| Share live tracking with a customer or partner | Public tracking pages | Out |
Inbound email is a real integration point
Your organization’s address — your-slug@in.trackberry.com — accepts mail from
any system that can send it. Anything that can email a packing list can feed
Trackberry: a supplier’s ERP, a forwarder’s notification system, a scheduled
job in your own stack.
Documents are extracted, matched to the right shipment, and the email body is analysed for status changes. No credentials to manage on your side. See Receiving Documents by Email.
The calendar feed is a live URL
The ICS subscription link described in the Calendar guide is a stable, tokenised URL that returns current shipment arrivals every time it’s fetched. Calendar apps are the intended consumer, but anything that reads ICS can poll it.
Two things to know before you build on it:
- The token grants read access to your organization’s arrival data. Treat it as a secret; Revoke link invalidates it immediately.
- It returns arrivals, not full shipment records. It is not a substitute for an API.
ERP integration is set up with you, not by you
Trackberry pushes data into ERP systems through a connection our team builds and maintains — via your ERP’s own API, a file drop, or UI automation for software that has neither. This is a configured integration rather than something you wire up yourself, and it carries a setup fee and a monthly retainer.
See Exporting Data & ERP Integration for methods, what the export contains, and current pricing.
Known limitations
Being specific about the edges saves you discovering them mid-build:
- No read API. Shipment, pallet, and tracking data can’t be queried programmatically. Export or the calendar feed are the ways out.
- No outbound webhooks. Trackberry can’t POST to your endpoint when a shipment changes. Notifications reach people, not systems — see Notifications.
- No write API. Shipments are created by email, by manual upload, or as a draft container — not by request.
- The calendar feed is read-only and scoped to arrivals.
- Export formats are per-ERP. TradaBase XLSX ships today; other templates are built on request.
Getting help
Email support@trackberry.com with what you’re trying to connect and which system is on the other end. We’ll tell you whether an existing integration point covers it, or what it would take to build one.