Connectors 3PL and carrier APIs (DHL, UPS, FedEx, XPO)

3PL and carrier APIs (DHL, UPS, FedEx, XPO) data integration with Lima.

Carriers and third-party logistics providers publish shipment status through APIs and EDI messages. Lima reads tracking events, proof of delivery and exceptions from DHL, UPS, FedEx, XPO and others through their APIs (polling and push) and through EDI 214 and 856 messages, so on-time-in-full can be measured from the carrier's own record.

SOURCE3PL and carrier APIs (DHL, UPS, F…Carrier APIs · EDI 214 / 856LIMA BACKBONEExtractfull · incremental · streamingCheckevery row valid, or an exception with an…Transform and load150+ operators · Python · loads on the c…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · files
How 3PL and carrier APIs (DHL, UPS, FedEx, XPO) fits the six Backbone steps. It is a source: Lima extracts from it, checks and transforms the rows, and loads them where they are needed.
48K
carrier records a day
showcase estate
2
ways to read it
this connector
3
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads 3PL and carrier APIs (DHL, UPS, FedEx, XPO)

Method by method.

Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.

MethodWhat it doesWhen it is used
Carrier APIsPolls and receives tracking events.Near real time.
EDI 214 / 856 (X12) and IFTSTA / DESADV (EDIFACT)Reads status and dispatch messages.Partners on EDI.
What it covers

Objects and patterns.

The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.

ObjectPlain meaning
Shipments and tracking eventsstatus by shipment
Proof of deliverydelivered on time, in full
PatternSupported
Full loadYes
Incrementalevents since the last poll
Change capture—
Streamingpush where the carrier offers it
Write-back—
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs 3PL and carrier APIs (DHL, UPS, FedEx, XPO) grants. The four steps are the same for every connector.

  • Carrier API accounts
  • EDI trading-partner set-up where used
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →

Status and evidence

Stated plainly, with dates.

Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Questions

Asked about this connector.

Does Lima install anything in 3PL and carrier APIs (DHL, UPS, FedEx, XPO)?

Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.

How is load on 3PL and carrier APIs (DHL, UPS, FedEx, XPO) kept in check?

Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.

What do we see when a run finishes?

A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try 3PL and carrier APIs (DHL, UPS, FedEx, XPO) on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.