Vigilbase One APIServices

Analyze a Cloudflare checkup

AI remediation suggestions for a saved Cloudflare Checkup. The client names the run; the result is read server-side within the caller's tenant scope, never taken from the request body.

POST/api/services/cloudflare/checkups/analyze

Authorizations

Send one of these:

AuthorizationstringAccess tokenheaderrequired

Bearer access token from Vigilbase Identity (auth.vigilbase.com), sent as Authorization: Bearer <token>. The CLI gets one with vigilbase login.

AuthorizationstringAPI keyheaderrequired

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.

Body

application/json

toolRunIdstringuuidrequired

customerIdstringuuid

Response

Success

# Token from `vigilbase login`, or a write API key (vb_one_…)
curl --request POST \
  --url 'https://one.vigilbase.com/api/services/cloudflare/checkups/analyze' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"toolRunId":"<uuid>","customerId":"<uuid>"}'

Set VIGILBASE_TOKEN to an Identity access token or an organisation API key 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?