Create Outline Node

POST

/api/writing/outline/nodes

• DivinityEngine - Local development
• DivinityEngine - Localhost alternative

Create a new outline node.

Parameters

Query Parameters

project_id

required

Project Id

string

>= 1 characters

Request Body ^required

OutlineNodeCreateRequest

Create a new outline node.

object

parentId

Any of:

string

string

null

null

title

required

Title

string

nodeType

Nodetype

string

default: chapter

Allowed values: series book part act chapter scene beat

summary

Summary

string

""

notes

Notes

string

""

sortOrder

Sortorder

integer

0

documentId

Any of:

string

string

null

null

wordCountTarget

Any of:

integer

integer

null

null

status

Status

string

default: draft

Allowed values: draft in_progress revision done

povType

Any of:

string

string

Allowed values: first_person second_person third_limited third_omniscient third_objective multiple_first deep_third stream_of_consciousness unreliable

null

null

povEntityId

Any of:

string

string

null

null

sceneType

Any of:

string

string

Allowed values: scene sequel hybrid flashback vision dream

null

null

sceneOutcome

Any of:

string

string

Allowed values: success failure partial disaster yes_but no_and pyrrhic unexpected

null

null

locationEntityId

Any of:

string

string

null

null

timeMarkerEventId

Any of:

string

string

null

null

timeMarkerText

Any of:

string

string

null

null

knowledgeState

Any of:

SceneKnowledgeState

SceneKnowledgeState

Knowledge state for a scene, keyed by participant lore_entries.id.

Participants absent from the map are treated as having empty known / unknown sets — the map is only required to carry non-empty state.

object

participants

Participants

object

key

additional properties

ParticipantKnowledge

Per-participant fact set — what a character knows (and does not know) at the start of a scene.

M3 stores facts as free-text strings. M4 will upgrade them to {id, text} references when the contradiction engine formalizes a fact registry; the shape evolves forward-compatibly via data migration, not a schema rewrite.

object

knownFacts

Knownfacts

Array<string>

unknownFacts

Unknownfacts

Array<string>

null

null

Responses

201

Successful Response

OutlineNode

Single outline node in the book hierarchy.

object

id

required

Id

string

projectId

required

Projectid

string

parentId

required

Any of:

string

string

null

null

title

required

Title

string

nodeType

required

Nodetype

string

Allowed values: series book part act chapter scene beat

summary

required

Summary

string

notes

required

Notes

string

sortOrder

required

Sortorder

integer

documentId

required

Any of:

string

string

null

null

wordCountTarget

required

Any of:

integer

integer

null

null

status

required

Status

string

Allowed values: draft in_progress revision done

povType

Any of:

string

string

Allowed values: first_person second_person third_limited third_omniscient third_objective multiple_first deep_third stream_of_consciousness unreliable

null

null

povEntityId

Any of:

string

string

null

null

sceneType

Any of:

string

string

Allowed values: scene sequel hybrid flashback vision dream

null

null

sceneOutcome

Any of:

string

string

Allowed values: success failure partial disaster yes_but no_and pyrrhic unexpected

null

null

locationEntityId

Any of:

string

string

null

null

timeMarkerEventId

Any of:

string

string

null

null

timeMarkerText

Any of:

string

string

null

null

knowledgeState

Any of:

SceneKnowledgeState

SceneKnowledgeState

Knowledge state for a scene, keyed by participant lore_entries.id.

Participants absent from the map are treated as having empty known / unknown sets — the map is only required to carry non-empty state.

object

participants

Participants

object

key

additional properties

ParticipantKnowledge

Per-participant fact set — what a character knows (and does not know) at the start of a scene.

M3 stores facts as free-text strings. M4 will upgrade them to {id, text} references when the contradiction engine formalizes a fact registry; the shape evolves forward-compatibly via data migration, not a schema rewrite.

object

knownFacts

Knownfacts

Array<string>

unknownFacts

Unknownfacts

Array<string>

null

null

createdAt

required

Createdat

integer

modifiedAt

required

Modifiedat

integer

422

Validation Error

HTTPValidationError

object

detail

Detail

Array<object>

ValidationError

object

loc

required

Location

Array

msg

required

Message

string

type

required

Error Type

string

input

Input

ctx

Context

object