CARGOHOLD

Integrations and API

Logistics API and webhooks for your own systems

A versioned REST API with scoped keys and rate limits, signed webhooks with a delivery log, and an MCP server for your own assistants.

API keys with scopes beside a webhook delivery log

What it does

  • A versioned REST API over the core entities, with API keys that carry scopes and rate limits.
  • An OpenAPI specification generated from the code and a hosted API documentation page.
  • Webhooks with subscriptions, a signing secret, retries and a delivery log you can read.
  • An MCP server so your own assistants can call the system's tools.
  • An EDI center with an X12 viewer and an error queue that retries, for load tenders, status messages, freight invoices and warehouse orders, exchanged with each trading partner once that connection is set up for your operation.
  • An integrations page listing every connector with its sync log, and which are available on request.
  • Sandbox API keys for a sandbox account, separate from your live data.

See the workflows

  1. 01
    First key to first call

    A key is created with its scopes, and the first call is made against the documented endpoint.

  2. 02
    Subscribe and receive

    A webhook subscription is created, the first delivery is signed, and failures are retried.

  3. 03
    Assistant tools

    Your assistant connects to the MCP server with a per-user token, the tool list arrives, and any write it asks for waits for approval.

A key is created with its scopes, and the first call is made against the documented endpoint.

API key creation with scopes and a first documented call

Works with the rest of the system

What you get

  • 3steps

    On one record, from the booking to the bill.

  • 14days

    Most builds are handed over in 14 days; your timeline is confirmed in writing after the onboarding call.

  • 3months

    Free support after handover.

  • $0

    Per truck, per dispatch or per client.

Questions

Is the API rate limited?

Yes, per key, with the limits documented alongside the scoped access each key carries.

How are webhooks secured?

Each delivery is signed with the subscription's secret, retried on failure, and recorded in a delivery log you can read.

What happens to our API keys and webhook subscriptions?

Free migration: we review your data with you, agree what moves where, and move it into your new system at no cost. Migration time is agreed at onboarding and comes on top of the build. If your current vendor makes exporting hard, we work with their support or build a workaround.

Who owns the system?

You do. The code and the data are yours, and the system runs on your own server, which we set up for you. There are no per-truck, per-dispatch or per-client fees.

See it running on your kind of data.

Book a demo and we walk through the screens for your operation. Or request sandbox access and try it yourself.