Developers › API reference › Access reviews

POST `/api/v1/access-reviews/{id}/sign-off`

Sign off, applying the chosen recommendations (a person).

Scope access_reviews:write
Idempotency-Key
A person
operationId adminSignReview

The token needs the scope access_reviews:write, 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).

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

Request

POST /api/v1/access-reviews/{id}/sign-off

Path parameters

Name	Description	Example
`id`	The id of the access review.	`1`

Headers

Header	Required	Value
`Authorization`	yes	`Bearer <token>`: an OAuth access token (`vat_…`) or a personal access token (`vpt_…`). Get a token
`Idempotency-Key`	yes	A unique string up to 255 characters (a UUID). Idempotency
`Content-Type`	yes	`application/json`

Body: `ReviewSignOff`

Field	Type	Required	Description
`apply`	list of integer	no	Indexes of the recommendations to apply.
`note`	string	no	Your note.

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/access-reviews/1/sign-off" \
  -H "Authorization: Bearer $VESTORIS_TOKEN" \
  -H 'Idempotency-Key: 7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11' \
  -H "Content-Type: application/json" \
  -d '{"apply":[0,2],"note":"Quarterly review done"}'

Python (requests)

import os, requests

r = requests.post(
    "https://vestoris.com/api/v1/access-reviews/1/sign-off",
    headers={
        "Authorization": f"Bearer {os.environ['VESTORIS_TOKEN']}",
        "Idempotency-Key": "7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11",
    },
    json={
        "apply": [
            0,
            2
        ],
        "note": "Quarterly review done"
    },
    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/access-reviews/1/sign-off", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.VESTORIS_TOKEN}`,
    "Idempotency-Key": "7f9c2b1e-4d0a-4a7e-9a51-3c2f0b8d6e11",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
      "apply": [
          0,
          2
      ],
      "note": "Quarterly review done"
  }),
});
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: AccessReview. Rate-limit headers: RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset.

Response fields

Field	Type	Description
`id`	id (string)	The record's id (a string of digits).
`period`	string	The period reviewed.
`status`	string	draft or signed.
`drafted_by_ai`	boolean	True when the AI drafted it (a person still checks and signs).
`draft`	string	The drafted text.
`recommendations`	list	What the review recommends (grant, revoke, adjust), each with a reason.
`created_at`	date-time or null	When it was created.
`signed_by`	id (string) or null	Who signed off.
`signed_at`	date-time or null	When it was signed off.
`sign_note`	string or null	The note written at sign-off.

Example response

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

{
    "id": "1042",
    "period": "2026-Q3",
    "status": "draft",
    "drafted_by_ai": false,
    "draft": "",
    "recommendations": [],
    "created_at": "2026-10-27T14:30:00Z",
    "signed_by": null,
    "signed_at": null,
    "sign_note": null
}

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.

Status	When	Problem codes
200	Success
200 / 201	The same Idempotency-Key again: the first answer is replayed (24 hours)
400	The request is malformed	`invalid_request` `invalid_json`
401	No token, or it is invalid or expired	`invalid_token`
403	The token lacks the scope, or the person or service account behind it lacks the privilege or account permission	`insufficient_scope` `forbidden` `ip_not_allowed` `user_token_required`
404	Not found, or not visible to you (the API never confirms what you may not see)	`not_found`
409	Not possible in the current state	`invalid_transition` `conflict` `idempotency_in_progress`
422	Validation failed (the detail says which field), or blocked	`validation_failed` `idempotency_key_reused`
428	A required header is missing	`idempotency_key_required`
429	Rate limited: wait for Retry-After seconds	`rate_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/access-reviews/1/sign-off"
}

On the screens

The same thing in the app is explained in:

Access reviews

POST /api/v1/access-reviews/{id}/sign-off