Create a Vigil conversation approval

POST /api/vigil/conversations/{conversationId}/approvals on the Vigilbase One API.

Needs a recent sign-in

POST/api/vigil/conversations/{conversationId}/approvals

One accepts this request only with a recent sign-in; renewing a token doesn't count, and MCP sessions and API keys are always refused. See changes that need a recent sign-in.

Authorizations

AuthorizationstringAccess tokenheaderrequired

Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login. Organisation API keys can't call this endpoint: it needs a recent sign-in by a person.

Permissions checkedapprove:vigil-actionswrite:deploymentswrite:services

Path Parameters

conversationIdstringrequired

Body

application/json

The catalog doesn't describe this body's fields.

Response

Success

# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/vigil/conversations/{conversationId}/approvals' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{}'

Set VIGILBASE_TOKEN to an Identity access token first, or use Try it.

Responses

200Success

401Authentication required

403Not permitted

The catalog doesn't include example response bodies for this endpoint.

Was this page helpful?