Integrations & API Access

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? #

Yes. Any member, admin or owner can create an API token under Organization settings → API & webhooks and read shipments, tracking, free time, alerts, checks, documents and packing lists as JSON. See The Trackberry API for tokens, versions and every endpoint.

Most of it is read-only. A token created as “Read and write” can also do two things:

• Create and revoke the tracking links you give your customers (see Customer links).
• Upload documents for extraction and read the data back, whether or not the shipment is tracked with Trackberry (see Documents to data).

For events, admins can set up webhooks: Trackberry calls your system when a shipment changes status or ETA, its document checks finish, or an alert opens. If another write endpoint would change how you work with Trackberry, tell us what you’d build with it at [email protected]. A concrete use case helps us assess the request.

What you can automate today #

Much of Trackberry’s data is already machine-readable. These are the integration points that exist and are supported.

Inbound email is a real integration point #

Your organization’s address, [email protected], 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 analyzed for status changes. There are 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, tokenized 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. Our team configures it, so it is not something you set 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 #

Knowing these limits in advance means you won’t discover them halfway through a build:

• The API mostly reads. It reads what you see in the app, including document files. Its only writes are customer tracking links and document uploads.
• Webhooks cover seven events. Status changes, ETA changes, finished document checks, new alerts, newly read documents, and shipments becoming Ready for ERP or going back to review can be POSTed to your endpoint (see Webhooks); other changes only reach people, see Notifications.
• Shipments can’t be created or edited through the API. They’re created by email, by manual upload, or as a draft container. The one exception is an uploaded document with no shipment to go on: it gets a new draft shipment that isn’t tracked.
• The calendar feed is read-only and scoped to arrivals.
• Export formats are per-ERP. TradaBase XLSX is available today, switched on for each organization that uses it; other templates are built on request.

Getting help #

Email [email protected] 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.