Patch Record

PATCH 
/signature/:signature_id/record

Partially update the Record attached to a signature using JSON Merge Patch (RFC 7386).

Fields present in the patch replace the stored value (arrays and objects are replaced wholesale, not merged), fields set to null are cleared, and absent fields are left unchanged. The patch applies against the currently attached Record (or an empty one when none is attached), and the resulting Record must satisfy the same consistency rules as a full replace; a contradictory result is rejected and the stored Record is left unchanged.

Supports optimistic concurrency: pass the current ETag in an If-Match header to make the write conditional; a stale precondition returns 412 Precondition Failed.

Request

Responses

204

The Record was updated

Response Headers

ETag
The signature's current revision as a strong validator, e.g. "5". Pass it back in an If-Match header on a later write to make that write conditional.
Example: "5"
SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

400

The request was rejected. A validation failure lists every offending field in details; other failures carry message only.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

401

An authorization error has occurred.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

403

An authorization error has occurred.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

404

The requested resource was not found.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

409

The signature is revoked; its Record can no longer be modified.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61

412

The If-Match precondition did not match the signature's current revision; the Record was not modified. Re-read the Record and retry with the new ETag.

Response Headers

SASHA-Request-ID
The identifier of this request, set on every response. Quote it when contacting SASHA support: it is what joins your call to the server-side logs. On an error response the same value is repeated in the payload's request_id.
Example: 8f14e45f-ceea-467a-9f0b-2b3a2c5a7d61