API and webhooks

A haulage API with signed webhooks, for your TMS or ERP

Post loads and follow their progress from your own systems, and have events pushed to you as they happen. Load Éireann offers a REST API with scoped API keys, HMAC-signed webhooks with automatic retries and a delivery log, and an OpenAPI specification.

Last updated . Load Éireann is in a closed pilot: registration is limited to approved participants.

Why integrate

Most hauliers and shippers already have software: a transport management system, an ERP, a dispatch spreadsheet or an in-house tool. Re-keying loads into a second system is slow and error-prone. An API lets your system create loads, read their status and tracking, and fetch invoices, so Load Éireann becomes a channel your existing process can use rather than another screen to maintain.

API keys with limited scopes

  • Owners and admins create keys in API Management and give each one only the scopes an integration needs, for example reading loads, writing loads, tracking or invoices.
  • Keys can have an optional expiry and an IP allow-list, and can be rotated or revoked at any time.
  • A key is shown once when it is created. Send it in the X-API-Key header, never in the URL.
  • Some actions, such as bids, cancellations, payments and managing the keys themselves, are deliberately not available to API keys and need a signed-in user.
  • API requests are rate limited per key, and limit headers tell your client how much is left.

Signed webhooks you can trust

Configure an endpoint and choose the events you want. Each delivery is signed with HMAC-SHA256 over a timestamp and the body, so your server can verify it came from us and was not replayed. If your endpoint is down, deliveries are retried automatically, up to 8 attempts over about 22 hours. You can send a test ping, review every delivery in a log and resend one if needed.

  • Load events: created, bid received, assigned, status changed, delivered.
  • Tracking events: location updated, arrived, departed, delayed.
  • Invoice events: created and paid.

Documentation and an OpenAPI spec

The integration guide covers authentication, loads, bids, tracking, invoices, fleet, backloads, webhooks, errors and rate limits, and an OpenAPI specification in JSON is available for generating clients or importing into tools such as Postman.

Getting started in five steps

  • Read the integration guide and open the OpenAPI specification to see the endpoints and scopes.
  • In API Management, create a key with only the scopes your integration needs, and store it somewhere safe because it is shown once.
  • Call the API with the key in the X-API-Key header, starting with a read-only request such as listing loads.
  • Add a webhook endpoint, choose the events you need and send a test ping.
  • Verify the signature and timestamp on every delivery, and return a success response quickly so retries are not triggered.

Accounting is built in

If your goal is getting invoices into your books, you do not need to build anything. Xero, QuickBooks, Sage and FreeAgent connections are built in and set up per company. See the accounting integrations page.

Frequently asked questions

Yes. It is available as JSON alongside the written integration guide.

See it with sample data

The live demo is read-only and needs no sign-in. Try the load board, tracking, warehouse and API screens.