Vigilbase One APIServices

Replace Cloudflare zone security

GET: the zone's security defaults, read live from Cloudflare and graded by the shared Cloudflare Checkup checks, falling back per setting to the latest checkup. The eight pre-2026-10 top-level fields (ssl, waf, ...) stay, with the same values as settings. PUT answers with the same view, read again after the write.

Needs a recent sign-in

PUT/api/services/cloudflare/zones/{zoneId}/security

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.

Path Parameters

zoneIdstringrequired

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 PUT \
  --url 'https://one.vigilbase.com/api/services/cloudflare/zones/{zoneId}/security' \
  --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?