Update integration
Enable, disable or configure an integration. Every integration accepts
status; the rest of the accepted keys depend on which integration it
is, and anything else is ignored.
SiteScanIntegrationalso acceptsscan_frequency(weeklyormonthly; weekly is not available on free accounts) andauto_add_vendors.GoogleConsentModeIntegrationalso acceptsurl_passthroughandads_data_redaction.
Enabling an integration may add its associated vendors to the account.
Scheduled scanning is a paid feature: on a free plan, setting
SiteScanIntegration to active or turning on auto_add_vendors is
refused with a 422. Turning it off always works, so an account that
downgrades can still disable it.
Authorizations
API token obtained from the login endpoint or the dashboard
Path Parameters
ID of the resource
Query Parameters
Which account to act on, as the account's API id. Only meaningful for a user API key, which may reach several accounts — an account key already identifies exactly one and ignores this.
Accepted by the endpoints that declare it; others act on the account the key resolves to on its own.
Optional for reads, where it narrows the request to that account.
Required for writes that declare it when the key can reach more than one
account: without it the request would act on an account it picked rather
than one you named, so it is refused with a 400.
Body
Integration settings to update
status applies to every integration. The remaining keys are only
accepted by the integration that declares them; anything else is ignored.
Response
Updated integration