Vigilbase One APIServices

Start a Cloudflare checkup

Starts a Cloudflare Checkup: creates the run under a short customer fence, then starts its durable Workflow (CHECKUP_WORKFLOW), which scans and stores the result however long the account takes. Nothing runs after the response: a run is either handed to its Workflow or marked failed.

Needs a recent sign-in

POST/api/services/cloudflare/checkups/start

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 checkedwrite:services

Body

application/json

customerIdstringuuid

accountIdstring

min length 1

Response

Success

More about this endpoint in the guide.

# Token from `vigilbase login`. API keys can't call this.
curl --request POST \
  --url 'https://one.vigilbase.com/api/services/cloudflare/checkups/start' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"customerId":"<uuid>","accountId":"<string>"}'

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?