Request a change
Asks Vigilbase to make a change for the customer. Needs a verified email for customer callers.
Deprecated aliases: POST https://one.vigilbase.com/api/change-requests. They answer with the same bodies, with a Deprecation header and a successor-version link to this URL.
Authorizations
Send one of these:
Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Scope: one:api.
Organisation API key (vb_one_…) from Settings → API keys in Vigilbase One, sent as Authorization: Bearer vb_one_…. Needs a key with write access: read-only keys get 403 with the code read_only_key. See organisation API keys.
Vigilbase Identity access token issued to an MCP client (mcp.vigilbase.com). Scope: one:write.
Headers
A unique key for this write (a UUID is recommended). A retry with the same key and body returns the first answer (draft-ietf-httpapi-idempotency-key-header-08).
Body
application/jsonResponse
application/jsonSuccess
requestedawaiting_customer_approvalreadyexecutingappliedawaiting_propagationverification_failedfaileduncertainrejectedexpiredrolling_backrolled_backrollback_awaiting_propagationrollback_uncertaincompleted_manuallyWhether Vigilbase has prepared the exact change.
2 response headers
The request ID: yours when it was well-formed, otherwise a new one. Quote it to support.
The major API version (informational; the version is in the path).