Create a deliverable with validation
Create a node with the concept rules enforced: valid nesting, the fields that concept requires, station linkage, and department scoping.
Anything outside the grammar is rejected, so a step under an order comes back as 400 rather than leaving a tree the app cannot show. Prefer this over POST /deliverable.
Authorizations
Organization-scoped API key. Create one in the BuildingSwell app under Organization settings, API keys.
Body
Concept to create.
order, route, overhead, template-phase, phase, component, stage, step, qcstep Node name.
Node to nest under. Leave it off for a root.
Root of the tree.
Your own identifier. Generated when you leave it out.
How many of this node the work covers.
Cycle time per unit, in seconds.
Total duration, in seconds.
How many people the node is planned for.
Cost code.
Route or template to build this node from. Setting it applies that structure underneath.
Per-concept fields. Which keys are required depends on type: an order needs projectId, an overhead needs category, a qcstep needs qcTemplateId. A stage node needs stageId unless a department can be resolved, in which case the station is found or created for you.
Response
The created node.
A deliverable as the concepts layer returns it: the node's own fields plus its resolved concept context.
Node id.
Human-readable id.
Node name.
Concept this node represents.
order, route, overhead, template-phase, phase, component, stage, step, qcstep Node directly above this one.
Root of the tree.
How many of this node the work covers.
Cycle time per unit, in seconds.
Total duration, in seconds.
How many people the node is planned for.
Cost code.
Per-concept fields for this type.
Values BuildingSwell derives from the tree on every read. All read-only: anything you send here is ignored.