lists.apply
Apply a numbering definition to a paragraph. When `/word/numbering.xml` is absent it is materialized atomically together with the package content-type override and document relationship. Seeds bullet or ordered single-level definitions when no `reuseNumId` is provided. Available on v2-backed sessions only; v1-backed sessions currently return `CAPABILITY_UNAVAILABLE`.
doc.lists.apply(…)Expected result
Returns a ListsMutateItemResult receipt with txId; partsChanged includes numbering / content-types / rels when first-list materialization fires.
Inputs
targetparagraph | listItemrequiredparagraph
kind"block"requirednodeType"paragraph"requirednodeIdstringrequiredlistItem
kind"block"requirednodeType"listItem"requirednodeIdstringrequiredseed"bullet" | "ordered"required2 additional input fields
reuseNumIdstringilvlintegerResult
Output fields
true
successtruerequireditemListItemAddressrequiredFields
kind"block"requirednodeType"listItem"requirednodeIdstringrequiredstoryStoryLocatorStory scope. Defaults to document body when omitted. Use {kind:'story', storyType:'body'} for body, or other storyType values for headers, footers, footnotes, endnotes.
body
kind"story"requiredstoryType"body"requiredheaderFooterSlot
kind"story"requiredstoryType"headerFooterSlot"requiredsectionSectionAddressrequiredheaderFooterKind"header" | "footer"requiredvariant"default" | "first" | "even"requiredresolution"effective" | "explicit"onWrite"materializeIfInherited" | "editResolvedPart" | "error"headerFooterPart
kind"story"requiredstoryType"headerFooterPart"requiredrefIdstringrequiredfootnote
kind"story"requiredstoryType"footnote"requirednoteIdstringrequiredendnote
kind"story"requiredstoryType"endnote"requirednoteIdstringrequiredtextbox
kind"story"requiredstoryType"textbox"requiredtextboxIdstringrequiredaffectedStoriesStoryLocator[]remappedRefsAffectedRefRemapping[]textRangeShiftsTextRangeShift[]txIdstringchangedbooleantrackedChangeRefsTrackedChangeAddress[]false
successfalserequiredfailureobjectrequiredFields
code"INVALID_TARGET" | "TARGET_NOT_FOUND" | "CAPABILITY_UNAVAILABLE" | "INVALID_CONTEXT" | "INVALID_INPUT"requiredmessagestringrequireddetailsunknownFailures
Pre-apply throws
TARGET_NOT_FOUNDCAPABILITY_UNAVAILABLEINVALID_TARGET
1 more codes
INVALID_INPUT
Non-applied receipt codes
INVALID_TARGETTARGET_NOT_FOUNDCAPABILITY_UNAVAILABLE
2 more codes
INVALID_CONTEXTINVALID_INPUT
Raw schemas
Open the generated JSON artifact for the exact input, output, success, and failure schemas represented by this contract version.
View raw JSON schemas