Developers › API reference › Workflow

POST /api/v1/workflow/rules/{id}/sign-off

Sign off as Admin or Compliance (a person; X-Vestoris-Confirm).

  • Scope workflow:rules:approve
  • Idempotency-Key
  • Confirmation
  • A person
  • Four eyes
  • operationId workflowSignOff

The token needs the scope workflow:rules:approve, and the person or service account behind it needs the matching privileges and account permissions, exactly as on the screens. See Scopes.

Idempotency-Key. Send a unique Idempotency-Key (up to 255 characters, e.g. a UUID) with every POST. Retrying with the same key and body replays the first answer for 24 hours, so a timeout never creates a second order; the same key with a different body is refused (idempotency_key_reused).

Confirmation. Needs X-Vestoris-Confirm with the confirm_token of the preview you are confirming (see Confirmations). The token is bound to that exact preview; if anything changed, ask for a new preview.

A person. Only a person may do this: use a personal access token or an authorization-code token, never client credentials (user_token_required).

Four eyes. An approval: never by the person who entered or authored the item. A service account needs its client's "may approve" setting (approvals_not_granted).

Request

POST /api/v1/workflow/rules/{id}/sign-off

Path parameters

NameDescriptionExample
idThe id of the rule.41

Headers

HeaderRequiredValue
AuthorizationyesBearer <token>: an OAuth access token (vat_…) or a personal access token (vpt_…). Get a token
Idempotency-KeyyesA unique string up to 255 characters (a UUID). Idempotency
X-Vestoris-ConfirmyesThe confirm_token of the preview you confirm. Confirmations
Content-Typeyesapplication/json

Body: WorkflowSignOff

FieldTypeRequiredDescription
asstringyes"admin" or "compliance".
notestringnoA note in plain words.
effectivestringnoWhen it takes effect: "now" or a date (YYYY-MM-DD).

Decimals (money, prices, quantities, percentages) are sent as strings, ids as strings, times as ISO 8601 UTC.

Examples

Keep the token in an environment variable (VESTORIS_TOKEN), never in the script.

curl

curl -X POST "https://vestoris.com/api/v1/workflow/rules/41/sign-off" \
  -H "Authorization: Bearer $VESTORIS_TOKEN" \
  -H 'Idempotency-Key: 7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11' \
  -H 'X-Vestoris-Confirm: vcf_77be…' \
  -H "Content-Type: application/json" \
  -d '{"as":"admin","note":"Replay reviewed","effective":"now"}'

Python (requests)

import os, requests

r = requests.post(
    "https://vestoris.com/api/v1/workflow/rules/41/sign-off",
    headers={
        "Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
        "Idempotency-Key": "7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11",
        "X-Vestoris-Confirm": "vcf_77be…",
    },
    json={
        "as": "admin",
        "note": "Replay reviewed",
        "effective": "now"
    },
    timeout=30,
)
r.raise_for_status()  # errors are application/problem+json with a stable "code"
print(r.json())

JavaScript (fetch)

const res = await fetch("https://vestoris.com/api/v1/workflow/rules/41/sign-off", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.VESTORIS_TOKEN}`,
    "Idempotency-Key": "7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11",
    "X-Vestoris-Confirm": "vcf_77be…",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
      "as": "admin",
      "note": "Replay reviewed",
      "effective": "now"
  }),
});
const data = await res.json();
if (!res.ok) throw new Error(`${data.code}: ${data.detail}`); // problem+json
console.log(data);

Response

200 OK, application/json: WorkflowRule. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.

Response fields
FieldTypeDescription
idid (string)The record's id (a string of digits).
lineage_idid (string)The id shared by every version of the rule.
versionintegerVersion number.
namestringThe rule's name.
item_typestringThe kind of item: order, override, rule, violation, batch, feed_run, access_review, exception.
priorityinteger1 (urgent) to 4 (low); for rules, lower numbers are evaluated first.
statusstringdraft, pending, active, superseded, retired or rejected.
statestringHow the rule stands now (in force, scheduled, waiting for sign-off…).
is_defaultbooleanTrue for the default rules that reproduce the firm thresholds.
conditionsanyWhen the rule applies: "all" conditions must hold and at least one "any" condition.
actionslistWhat the rule does when its conditions hold (approvals, queue, assignment, priority, SLA, notifications).
restatementstringWhat the engine will enforce, written by code from the structured definition.
source_textstringThe words the rule was written from.
drafted_by_aibooleanTrue when the AI drafted it (a person still checks and signs).
pending_actionstring or nullWhat is waiting for sign-off: "activate", "change" or "retire".
weakensbooleanTrue when the change weakens an approval (then Compliance must also sign).
weakens_whystringWhy it counts as weakening.
signoffsobjectWho has signed off so far.
signoffs.adminid (string) or nullThe Admin who signed off (id), or null.
signoffs.complianceid (string) or nullThe results of the compliance checks (rule, outcome, measured value, limit).
test_benchobject or nullThe latest test-bench result: what the rule would have blocked, warned on or logged.
effective_fromdate-time or nullWhen this version took (or takes) effect.
effective_todate-time or nullWhen this version stopped being in force (null: still in force).
created_byid (string) or nullThe user who created it.
created_atdate-time or nullWhen it was created.
donebooleanWhether every required sign-off is in.
still_neededlist of stringSign-offs still needed.

Example response

HTTP/1.1 200 OK
Content-Type: application/json

{
    "id": "1042",
    "lineage_id": "41",
    "version": 1,
    "name": "Large Growth orders",
    "item_type": "order",
    "priority": 2,
    "status": "active",
    "state": "in force",
    "is_default": false,
    "conditions": {
        "all": [
            {
                "field": "notional",
                "op": ">",
                "value": 1000000
            }
        ],
        "any": []
    },
    "actions": [
        {
            "type": "require_approval",
            "roles": [
                "portfolio_manager",
                "compliance_officer"
            ],
            "count": 2
        }
    ],
    "restatement": "Block any order that would make one issuer more than 5.00% of a Growth account (ETFs excepted).",
    "source_text": "",
    "drafted_by_ai": false,
    "pending_action": "",
    "weakens": false,
    "weakens_why": "",
    "signoffs": {
        "admin": null,
        "compliance": []
    },
    "test_bench": null,
    "effective_from": null,
    "effective_to": null,
    "created_by": "7",
    "created_at": "2026-10-27T14:30:00Z",
    "done": false,
    "still_needed": [
        "compliance"
    ]
}

Example values. Your values depend on your firm's data; prices, orders and fills are simulated.

Status codes and errors

Errors are application/problem+json (RFC 9457) with a stable code to program against; the detail says what to fix. See Errors.

StatusWhenProblem codes
200Success
200 / 201The same Idempotency-Key again: the first answer is replayed (24 hours)
400The request is malformedinvalid_request invalid_json
401No token, or it is invalid or expiredinvalid_token
403The token lacks the scope, or the person or service account behind it lacks the privilege or account permissioninsufficient_scope forbidden ip_not_allowed user_token_required approvals_not_granted
404Not found, or not visible to you (the API never confirms what you may not see)not_found
409Not possible in the current stateinvalid_transition conflict idempotency_in_progress
422Validation failed (the detail says which field), or blockedvalidation_failed idempotency_key_reused
428A required header is missingidempotency_key_required confirmation_required
429Rate limited: wait for Retry-After secondsrate_limited
{
    "type": "https://vestoris.com/developers/errors#validation_failed",
    "title": "Validation failed",
    "status": 422,
    "detail": "Quantity must be greater than zero.",
    "code": "validation_failed",
    "instance": "/api/v1/workflow/rules/41/sign-off"
}

On the screens

The same thing in the app is explained in: