Create a deliverable
Create one deliverable, or several at once by sending an array.
These raw endpoints do not enforce the nesting rules. A step under an order, or a stage node with no station, is accepted here and leaves the tree in a state the app cannot show. Use the domain concepts endpoints for validated writes.
Authorizations
Organization-scoped API key. Create one in the BuildingSwell app under Organization settings, API keys.
Body
- object
- object[]
These raw endpoints do not enforce the nesting rules. A step under an order, or a stage node with no station, is accepted here and leaves the tree in a state the app cannot show. Use the domain concepts endpoints for validated writes.
Display name.
Which concept this node represents.
order, route, overhead, template-phase, phase, component, stage, step, qcstep, group Unique id. Generated on create unless you supply one.
Human-readable id, unique within your organization. Generated for you when you leave it out.
Archived records are hidden from list results unless you ask for them. Set this to archive or restore the record.
When the record was archived. Set automatically when isArchived flips to true, and cleared on restore.
How many of this node the work covers.
Node directly above this one.
Root of this node's tree. A root node points at itself.
Route or template this node was built from.
Cycle time per unit, in seconds.
Total duration, in seconds.
How many people the node is planned for.
Per-concept fields. Which keys apply depends on type: a stage node needs stageId, an order needs projectId, and so on. See the domain concepts guide for the full table.
Cost code. Trimmed on write, and an empty string is rejected: send a non-empty string or null.
Stored as a plain string. It is not validated against the cost code list, and renaming an entry in that list does not change this value.
When the record was created.
When the record last changed.
Response
The created deliverable. An array request returns values instead of value.
- Option 1
- Option 2
One generic work-tree node. Its type decides which domain concept it represents, from an order down to a single step.