CONNECT

Connect your system

Your gate system, warehouse software, truck GPS or control tower can send updates to CargoMo with one web call. It works from any language: PHP and Laravel, Java, .NET, Python or Node. Nothing to install on your side.

NO REWRITE

You keep your system. CargoMo adds the last mile.

Most cargo companies already have software they trust. CargoMo does not ask you to replace it. Your system keeps running the dock, the warehouse or the planning. It sends CargoMo the events it already knows, like gate in, docked or sealed.

CargoMo adds what usually happens outside your system: the truck driver's phone, partners without software, live position, delays with a reason, damage photos, and a tracking link for the customer.

If you later want to move a part of your old system into CargoMo, it can be done one piece at a time while both keep running.

SIX WAYS

From no code to a full connection

1. Partner linksA truck company, terminal or agent with no software gets a link. Big buttons: picked up, delivered, running late, report damage with a photo. No app, no login.
2. Driver linksEach truck driver gets a link on WhatsApp for one shipment: steps, location, photo of the signed paper, signature.
3. Excel / CSV inBring shipments in from a spreadsheet, with a preview before anything is saved. Land, Air and Water.
4. Excel / CSV outTake any list out, or all your data at once. Your data is always yours.
5. The update APIYour system sends events to CargoMo with a key. Air and sea freight today. Details below.
6. Updates outCargoMo sends every update to your system as it happens: trucks, air and sea. Details below.
THE UPDATE API

One web call per event

Each system that sends updates is a data source in CargoMo, with its own key. An admin adds it under Air or Water, then Data sources. A key can be changed at any time, and the old one stops working at once.

AirPOST /api/air/ingest
SeaPOST /api/water/ingest
KeyHeader Authorization: Bearer <source key>
BodyJSON. One update, or { "updates": [ ... ] } with up to 200.
Limit600 updates a minute per key.
shipmentRequired. Our number (AX-2058, WM-3004), the air waybill or the bill of lading. For an air waybill, dashes and spaces do not matter.
eventRequired. One of the events below.
legOptional. Which part of the journey (1, 2, 3...). Left out, CargoMo uses the part in progress.
atOptional. When it happened, ISO time like 2026-11-16T09:42:00Z. Left out, it is now.
lat, lngFor position. Numbers.
delayMinFor delay. Minutes late.
textOptional. A short note people can read, up to 500 characters.
REPLY
// One update
{ "ok": true, "ref": "AX-2058", "leg": 2, "event": "gate_in" }

// A refused update, with the reason in plain words
{ "ok": false, "error": "Part 1 of AX-2058 has not finished yet, so part 2 cannot finish." }

// Many updates: one result for each, in the same order (HTTP 207 if some failed)
{ "results": [ { "ok": true, ... }, { "ok": false, "error": "..." } ] }
EVENTS

What your system can tell us

departedA truck, flight or vessel left. The part starts.
arrivedIt arrived. The part is finished.
received / releasedA warehouse or port took the goods in, or let them go.
gate_in / docked / sealed / gate_outGate and dock steps from a gate system or RFS control tower.
sailed / berthed / anchoredSea only. Vessel steps, for example from an AIS feed.
positionWhere the truck or vessel is now. Needs lat and lng.
delayRunning late. Needs delayMin. The office sees it at once.
problemSomething went wrong. Shown in red to the office.
noteAnything else worth keeping on the shipment.
EXAMPLES

Copy, change the key, send

CURL · AIR · A TRUCK AT THE GATE
curl -X POST https://your-cargomo-address/api/air/ingest \
  -H "Authorization: Bearer YOUR_SOURCE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "shipment": "176-12345675", "event": "gate_in",
        "at": "2026-11-16T09:42:00Z", "text": "Truck NL-82-BX at gate 3" }'
PHP · LARAVEL
use Illuminate\Support\Facades\Http;

// For example in a listener on your own GateEvent model.
$response = Http::withToken(config('services.cargomo.key'))
    ->post(config('services.cargomo.url') . '/api/air/ingest', [
        'shipment' => $awb,               // "176-12345675" or "AX-2058"
        'event'    => 'docked',           // see the list of events
        'at'       => now()->toIso8601String(),
        'text'     => "Docked at door {$door}",
    ]);

if (! $response->json('ok')) {
    Log::warning('CargoMo update not taken', $response->json());
}
NODE · SEA · TWO UPDATES AT ONCE
await fetch(process.env.CARGOMO_URL + "/api/water/ingest", {
  method: "POST",
  headers: { Authorization: "Bearer " + process.env.CARGOMO_KEY, "Content-Type": "application/json" },
  body: JSON.stringify({ updates: [
    { shipment: "WM-3004", event: "position", lat: 25.01, lng: 55.06 },
    { shipment: "WM-3004", event: "delay", delayMin: 240, text: "Waiting for a berth" },
  ] }),
});
UPDATES OUT

CargoMo tells your system as it happens

An admin puts the address of your system under Settings, then Updates out. From then on, every update on every shipment is sent there within a second: a driver picked up, a partner is late, damage was reported, a truck went through the gate, goods were delivered. Trucks, air and sea.

Each call is signed with a secret only you and CargoMo know, so your system can check it really came from us. There is a Send a test button to try it.

WHAT YOUR SYSTEM RECEIVES
POST https://your-system.example.com/cargomo/updates
Content-Type: application/json
X-CargoMo-Signature: sha256=6f1c...e9

{
  "type": "shipment.update",
  "product": "air",
  "shipment": "AX-2058",
  "awb": "176-12345675",
  "event": "problem",
  "leg": 4,
  "at": "2026-11-16T12:35:00.000Z",
  "text": "2 boxes wet at the dock",
  "by": "Rhine Road Feeder update page",
  "photo": true
}
PHP · LARAVEL · CHECK THE SIGNATURE
// Laravel route that receives CargoMo updates
Route::post('/cargomo/updates', function (Request $request) {
    $expected = 'sha256=' . hash_hmac('sha256', $request->getContent(), config('services.cargomo.secret'));
    abort_unless(hash_equals($expected, $request->header('X-CargoMo-Signature', '')), 401);

    $u = $request->json()->all();
    // $u['shipment'], $u['awb'], $u['event'], $u['at'], $u['text'] ...
    GateLog::recordFromCargoMo($u);
    return response()->noContent();
});
RULES AND SAFETY

Wrong updates are refused, with the reason

One key per sourceYou always know which system sent what. Each update on the shipment shows its source.
Keys belong to one companyA key can only touch that company's shipments. Nothing else can be read with it.
Order is checkedA part cannot finish before the part before it. The reply says so in plain words.
No future timesAn update more than 10 minutes in the future is refused.
Rate limit600 updates a minute per key, so a broken loop cannot flood the system.
Same door for everyonePartner links, the office and the API all go through the same checks. No back door.

These are planned and not in CargoMo yet. If your project needs one, it moves to the front.

Read APIYour system asks CargoMo for a shipment's status and expected arrival.
Land update APIThe same update API for truck shipments, for fleets with their own GPS.
Airline messagesRead Cargo-IMP and Cargo-XML status messages (FSU) directly.
START A TEST

Try it on the demo in ten minutes

  1. 01
    Open the demo

    Log in as the owner. No sign-up needed.

  2. 02
    Make a key

    Go to Air, then Data sources, and add a source. Copy its key.

  3. 03
    Send one update

    Use the curl example above with an AWB from the Air shipments list.

  4. 04
    See it land

    Open the shipment. Your update is on the timeline with your source name, and the customer's tracking link has moved.