Design engineering API (design_engineering)

The design_engineering module serves designs with their review lifecycle and files, and engineering change notes (ECNs). All 20 endpoints sit under /api/v1/design_engineering. For business meaning see the Design engineering module page.

Group facts¶

Endpoint summary¶

One row per sub-module folder. The router prefix is added to the base path.

Designs endpoints¶

Design records, submit for review, approve, reject, files, and the ECNs of a design.

Engineering change notes endpoints¶

ECN records, approve, reject, and implement.

Error codes¶

The table lists the error codes that code under src/cluster_erp/modules/design_engineering/ raises, found by a syntax-tree scan for AppError(...), the factories in src/cluster_erp/core/errors.py (not_found, conflict, protected, permission_denied, privilege_escalation, check_version), and HTTPException(...). A status of 400 is the AppError default (src/cluster_erp/core/errors.py:23). Guard errors (401, 403), the entitlement codes, and validation errors (422) apply to every route and are listed on Errors.

Events emitted¶

The table lists the contract classes that code under src/cluster_erp/modules/design_engineering/ passes directly to EventBus.emit, found by a syntax-tree scan. Events built in a variable first are not counted. The contracts are described in Contracts reference.

Related pages¶

• API reference
• Design engineering module
• API conventions
• Errors
• Authentication and headers

Verified against commit 92f8051 on 2026-11-13.