API and embedded workflows

Build evidence-pack workflows into your TMS, ERP, or procurement stack

Create workspaces, trigger pack generation, retrieve structured artifacts, record approvals, and test webhook delivery through the LogisticsAI API.

View OpenAPI Spec Request API Access

Legacy report endpoints remain available during migration to the workspace and evidence-pack model.

Built forTMS extensionsshipper procurement integrationsinternal sustainability toolingconsultant delivery workflows

Workspace orchestration

Create and inspect reusable reporting workspaces instead of managing one-off PDFs.

Pack artifacts

Retrieve machine-readable JSON, methodology statements, evidence registers, and audit trail artifacts from one pack version.

Webhook testing

Validate outbound webhook delivery against procurement, TMS, or sustainability endpoints before enabling production automations.

Core workflow endpoints

Grouped around the jobs product teams need to run inside an evidence-pack workflow. View OpenAPI Spec ->

POST/api/v2/workspaces

Create Workspace

Creates a reusable reporting workspace with reporting period and methodology defaults.

Request body

{
  "name": "Q2 Forwarding Workspace",
  "external_reference": "shipper-eu-q2-2026",
  "reporting_period_start": "2026-04-01",
  "reporting_period_end": "2026-06-30"
}

Response

{
  "data": {
    "id": "8a3f0898-6239-4ef3-b97e-06d8578f9d73",
    "name": "Q2 Forwarding Workspace",
    "status": "draft"
  }
}

GET/api/v2/workspaces

List Workspaces

Returns paginated workspaces for the authenticated organisation.

Response

{
  "data": [
    {
      "id": "8a3f0898-6239-4ef3-b97e-06d8578f9d73",
      "name": "Q2 Forwarding Workspace",
      "status": "review_needed"
    }
  ],
  "pagination": { "page": 1, "per_page": 20, "total": 1 }
}

POST/api/v2/workspaces/{id}/packs

Generate Evidence Pack

Builds or refreshes the evidence pack generated from the current workspace state.

Request body

{
  "legacy_report_id": "550e8400-e29b-41d4-a716-446655440000"
}

Response

{
  "data": {
    "id": "e7decc2f-1a69-40f3-b7f0-d77f24bdb4c0",
    "title": "Emissions Evidence Pack",
    "status": "published"
  }
}

GET/api/v2/packs/{id}/artifacts

List Pack Artifacts

Returns every artifact for a pack together with signed download URLs.

Response

{
  "data": [
    {
      "artifact_type": "machine_json",
      "status": "generated",
      "signed_download_url": "https://storage.logisticsai.eu/reports/..."
    }
  ]
}

POST/api/v2/packs/{id}/approvals

Record Approval Action

Moves a pack through request, approval, rejection, or publish actions with auditability.

Request body

{
  "action_type": "approved",
  "comment": "Approved by embedded review workflow"
}

Response

{
  "data": {
    "reportPackId": "e7decc2f-1a69-40f3-b7f0-d77f24bdb4c0",
    "statusBefore": "in_review",
    "statusAfter": "approved"
  }
}

POST/api/v2/webhooks/test

Test Webhook Delivery

Sends a signed test webhook payload to your endpoint and records the outcome.

Request body

{
  "target_url": "https://example.com/webhooks/logisticsai",
  "event_type": "pack.published"
}

Response

{
  "data": {
    "delivered": true,
    "http_status": 200,
    "event_type": "pack.published"
  }
}

How the integration model works

The v2 API mirrors the same workspace and evidence-pack workflow already running in the product.

Create a workspace and register imports from your source system.

Trigger calculation runs, review quality, and generate a versioned evidence pack.

Retrieve artifacts, record approval actions, and test outbound webhooks.

Legacy compatibility

Existing /api/v1/reports endpoints remain live while clients migrate to the workspace and pack model.

GET /api/v1/reports

GET /api/v1/reports/{id}

Use the API when you want LogisticsAI to become a reporting layer inside your own product or workflow.

View OpenAPI Spec Request API Access See sample artifact bundle