Cancel an in-progress contract request. The endpoint stops the signing process, marks every still-pending participant as canceled, transitions the request to canceled, and best-effort archives the document at the signing provider. It returns the updated contract request.

Authentication & access

• Requires a client API token: Authorization: Bearer <token>.
• The caller must hold the contracts.requests.cancel permission and have the OWNER or OPERATIONS role.
• Contract signing must be enabled for the client. If it is disabled the request returns 403.

Path parameters

Preconditions

The contract request must not already be in a terminal state. A request whose status is completed, canceled, declined, or expired cannot be canceled and returns 400.

What cancellation does

• Each participant still in a non-terminal state (created, pending, sent, or opened) is set to canceled.
• The overall request status is set to canceled and canceled_at is recorded.
• The associated signing submission is archived at the signing provider on a best-effort basis. If that archival call fails it is logged and ignored — the cancellation still succeeds.

Response

200 — Returns the updated ContractRequestResponse with status set to canceled, canceled_at populated, and each affected participant reflecting its canceled status.

Error responses

Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.