Document Statuses

Custom document statuses (EstadoDocumento / estados del documento).

📄️ Get document status by ID

Returns a single custom document status by its primary key.

📄️ Update document status

Full replacement of an existing custom document status. Send the `If-Match` header for optimistic concurrency (accepted but ignored ÔÇö not versioned).

📄️ Delete document status

Deletes a custom document status. Send the `If-Match` header with the current ETag (accepted but ignored ÔÇö not versioned).

📄️ Merge-patch document status

RFC 7396 merge-patch over `application/merge-patch+json`. Send only the fields you want to change; include a field with value `null` to remove it. Use the `If-Match` header for optimistic concurrency control.

📄️ List document statuses

Returns a paginated list of custom document statuses with envelope `{data, totalCount, skip, limit, hasMore}`. Supports optional RSQL `filter`, `sort` (default `name:asc`), `skip`/`limit` pagination and `modifiedAfter`/`modifiedBefore` bookends.

📄️ Create document status

Creates a new custom document status. Business logic runs in the legacy WAR via the internal commands gateway.

📄️ Prototype document status for a creation form

Returns a non-persisted document status pre-populated with backend defaults (current company, default document family). Optional JSON hints: `companyId`, `documentKind`, `copyFromId`. The response has no `id`, `version` or audit fields; call `POST /api/v2/document-statuses` afterwards to persist.