Patch Document
Patch Document
Body
Container for schema-enforced and schemaless data. A document is primarily used to store content (html, text, numbers, dates, JSON, binary data) that is directly or indirectly used for the storefront website experience and may be addressed via the Hypr theming engine language. A document belongs to a documentList and has an underlying documentType. The documentType describes any required and optional schema. Additionally, a binary object may be stored on the document's content subresource and edge cached via the Mozu CDN.
A JSON object of name/value pairs. Name parts are matched against the underlying documentType properties names. Any matching name parts must have a value part that conforms to the matching property schema. Any non-matching name/value pairs are considered dynamic schema and may have a value part of valid JSON. The properties field can be used for sorting/filtering and can be projected in the documents returned within a documentList view.
The current publish status of the document. If publishing is not supported or is currently disabled in the documentList then the value will be "active". If publishing is supported and enabled, then the publish state may be "draft" or "active". A document may have both an "active" and "draft" version. The publishState denotes which version of the document being interacted with. This field is read-only.
Response
OK
Container for schema-enforced and schemaless data. A document is primarily used to store content (html, text, numbers, dates, JSON, binary data) that is directly or indirectly used for the storefront website experience and may be addressed via the Hypr theming engine language. A document belongs to a documentList and has an underlying documentType. The documentType describes any required and optional schema. Additionally, a binary object may be stored on the document's content subresource and edge cached via the Mozu CDN.
A JSON object of name/value pairs. Name parts are matched against the underlying documentType properties names. Any matching name parts must have a value part that conforms to the matching property schema. Any non-matching name/value pairs are considered dynamic schema and may have a value part of valid JSON. The properties field can be used for sorting/filtering and can be projected in the documents returned within a documentList view.
The current publish status of the document. If publishing is not supported or is currently disabled in the documentList then the value will be "active". If publishing is supported and enabled, then the publish state may be "draft" or "active". A document may have both an "active" and "draft" version. The publishState denotes which version of the document being interacted with. This field is read-only.

