API.EDO-MBS.COM Production Control Plane
Service Online

Electronic Delivery Order Infrastructure

Build and operate logistics-grade workflows through one API backbone

E-DO API centralizes identity, shipment execution, async processing, notification signaling, and assistant jobs in a production-oriented runtime designed for high operational clarity.

Start with /v1 Open Frontend App
JWT Secured Versioned Routes Redis + BullMQ Audit Ready

Core Systems

Cyberpunk bento grid for primary runtime modules and responsibilities.

Identity Layer

Authentication + Access Control

JWT guardrails, role boundaries, and verification-aware flows protect both internal and consignee contexts.

JWT + Role Policies

Operations Layer

Shipment Execution Engine

Shipment lifecycle, NOA/DO actions, cost updates, and document states are orchestrated from one API surface.

Lifecycle + Documented State

File Layer

Attachment and Document Services

Upload, retrieval, and verification file flows run with controlled metadata and predictable storage behavior.

File APIs + Validation

Async Layer

BullMQ Queue Processing

Import jobs, notifications, and heavy background tasks run through Redis-backed queues with retry semantics.

Async Jobs + Retry

Signal Layer

Notification and Push Delivery

Event-driven notifications with preference controls and push subscriptions enable reliable user signaling.

Realtime + Web Push

AI Layer

AI Assistant and Job Threads

Threaded AI workflows and queued message processing integrate assistant capability into business operations.

OpenClaw + Job Pipeline

Execution Flow

How a request moves from ingress to audited response delivery.

01

Ingress + Validation

Request enters through versioned REST routes with schema validation and transport hardening.

02

Identity + Authorization

JWT context is resolved, role checks are applied, and request intent is mapped to policy boundaries.

03

Core Processing

Domain modules persist state to PostgreSQL and enqueue async tasks to Redis/BullMQ when required.

04

Delivery + Audit

Response is returned while runtime metadata, audit traces, and outbound notifications are committed.

Integration Surface

Domain map for consumers building against production APIs.

Auth + Identity
/v1/auth/*

Login, refresh, account profile, password reset, and role-aware session context.

Shipment Domain
/v1/shipments/*

Operational shipment actions, documents, costs, statuses, and import workflows.

Files Domain
/v1/files/*

Attachment ingest and retrieval with controlled metadata and storage integration.

Analytics + Reports
/v1/reports/*

Operational summary endpoints and export-oriented reporting interfaces.

Settings + Branding
/v1/settings/*

Public branding asset endpoints and internal runtime setting controls.

Assistant + Automation
/v1/edo-ai/*

AI session orchestration, job tracking, and background assistant execution.

Operational Guarantees

Production expectations encoded at middleware, runtime, and async layers.

Hardened Middleware

Helmet baseline and global request rate-limiting are enforced at bootstrap.

Reliable Persistence

PostgreSQL-backed modules with explicit migration strategy and typed entities.

Realtime + Queue Backbone

Redis powers websocket adapter and BullMQ for async operational workloads.

Traceable Operations

Runtime request logging and audit trails maintain operational accountability.

Operator FAQ

Fast answers for integration teams and internal operators.

Where should consumers start?

Use the base path endpoint and domain modules under /v1 for production integrations.

Is API documentation always public?

No. The docs CTA is rendered only when SWAGGER_ENABLED is active in runtime.

How are heavy tasks executed?

Queue-backed workers process imports, notifications, and AI jobs asynchronously.

Ready to integrate with production workflows?

Start with the versioned base path, then move through domain endpoints for operations, reporting, file services, and automation.

Begin Integration Open Application