TMS & visibilityAutomated detention and demurrage recovery for project44
project44 ocean milestones as the independent clock for your D&D audit
- Sync
- Event-driven via webhook, with a reconciliation pull every 6 hours
- Authentication
- OAuth 2.0 client credentials issued from your project44 account
- Data exchanged
- Ocean shipment tracking · Intermodal rail events · Shipment identifiers
How it connects
project44 is a supply chain visibility platform that tracks shipments across ocean, rail, truck, parcel and air, normalizing carrier, terminal and vessel data into a single event stream for shippers and logistics providers.
ATAHSKIA subscribes to the ocean and intermodal container events in your project44 account through its API, and uses them to build a container-level timeline: discharge, availability, holds where reported, outgate, rail moves and empty return. Every D&D invoice is then checked against the 20 elements of 46 CFR § 541.6 and against that timeline, so the stated free time and the specific dates charged can be tested rather than assumed.
Visibility tells you a charge is coming. Recovery needs the invoice, the rule and the evidence in one place, inside the § 541.8 window. Connecting project44 means the events you already pay for become dispute evidence instead of a dashboard someone glances at.
Data flows
Ocean shipment tracking
Reads
Container-level events from origin to destination: discharge, availability, outgate, empty return.
Intermodal rail events
Reads
Rail ramp arrivals and departures for inland point intermodal moves where tracked.
Shipment identifiers
Reads and writes
ATAHSKIA can register containers or B/Ls for tracking when they first appear on an invoice.
Field mapping
| ATAHSKIA | project44 | Note |
|---|---|---|
| Container number | Container identifier on the tracked shipment | |
| Bill of lading number | B/L identifier on the tracked shipment | |
| Carrier | Carrier identifier (SCAC) | |
| Discharge date | Vessel discharge event | |
| Container availability date | Available for pickup event, where reported | |
| Gate-out full date | Gate out full event at the discharge terminal | |
| Empty return date | Empty return event | |
| Event source | Event source attribution | Kept on the evidence timeline. |
Setup
Create API credentials
Your project44 administrator issues API credentials with read access to ocean shipments.
Connect and test
Add the credentials on the Integrations page. We pull a handful of recent containers to confirm events arrive.
Decide on auto-registration
Choose whether containers that appear on D&D invoices but are not yet tracked should be registered for tracking automatically.
Load invoices and history
Upload 12 months of D&D invoices so historic timelines can be matched and the retrospective audit produced.
What it recovers
Challenge billed days after empty return
Per diem runs two days past the empty return event recorded in project44. The packet attaches the event and asks for the excess to be credited.
Test free time start dates
The invoice starts free time on discharge, but the container showed no availability event until later. The discrepancy is flagged for the dispute.
Cover inland intermodal moves
Rail events show when an IPI container reached the inland ramp, so storage billed before arrival can be questioned.
project44 integration FAQ
Do we need a project44 subscription?
Yes. ATAHSKIA uses your existing project44 account. If you do not have one, we can use other tracking sources.
Are project44 events enough on their own?
They are a strong independent clock, but terminal holds and appointment availability usually come from terminal or appointment data. We combine sources and show each one.
Is this a formal project44 partnership?
No partnership is claimed. We connect through the API access your account provides.
Don't let your 30-day dispute window expire.
Send your recent D&D invoices for a free audit. We report what is recoverable within 48 hours.