Documentation

API & webhooks

Drop compliance into your TMS, ERP or load board.

Authentication

Create API keys on the API settings page. Send the key as a Bearer token. Live keys (llk_…) run real checks and consume a credit; test keys (llk_test_…) return a sandbox verdict and consume nothing.

Run a check

POST /api/v1/compliance/check
Authorization: Bearer llk_your_key
Content-Type: application/json

{
  "jurisdiction": "US-FED",
  "units": "imperial",
  "trailer_config": { "trailer_axles": 2 },
  "load": { "weight_lb": 42000, "cg_x_in": 505 }
}

Set jurisdiction to US-FED, US-CA…, or CA-MOU/CA-ON/… Add "units":"metric" to send kg/metres and get kg mirrors back. For a tridem, set trailer_config.trailer_axles = 3.

Hosted reference

Interactive docs are in the app: Swagger UI and ReDoc, plus the OpenAPI spec. Every call is logged (method, path, status, duration) on the API requests page.

Webhooks

Register a webhook URL and LoadLegit POSTs a signed check.completed event after every check (3 attempts). Verify the X-LoadLegit-Signature: t=<ts>,v1=HMAC_SHA256 header against your signing secret to confirm authenticity.

Each successful live check consumes one credit, whether from the app or the API. Test keys never do — use them to build your integration for free.
© LoadLegit · Compliance guidance, not legal advice.Docs home · Privacy · Terms