Add a scan's proposals to the cookie banner (admin)

POST 
/api/integrations/website/sites/:site/consent-scans/:scan/apply-suggestions

Accept some of the finished scan's proposals in ONE banner publish: vendors (catalogue keys) are added to the banner's vendors, cookies (proposal names, from the Open Cookie Database) to its cookie entries with the database's provider, category, lifetime and description. The server recomputes the proposals; a name that is not a current proposal is ignored (422 when none is left). The banner version bumps, so every visitor is asked again. Audit row website.consent_banner_published with source: scan.

Request

Responses

200

Added; the proposals that are left.

403

Authenticated but not allowed.

404

Resource not found (or not visible to the current tenant).

422

The request failed validation.