Skip to content

Update Campaign Generation Settings

PUT
/org/settings/campaign-generation

Set the campaign generation toggles.

BOTH default to true, so an empty body turns both ON. A partial body is not a partial update here.

Authorizations

Parameters

Header Parameters

X-Target-Org-Id
Any of:
string

Request Body required

Mirrors UpdateCampaignGenerationSettingsRequest.

Both default to TRUE, so an empty body turns both toggles ON. That is the app’s shape and it is a real trap: a partial body is not a partial update.

object
auto_generate_ad_images

Generate ad images alongside a new campaign.

boolean
default: true
auto_generate_landing_page

Generate a landing page alongside a new campaign.

boolean
default: true

Responses

200

Successful Response

object
data
required

An open envelope for one settings block, document or brand artefact.

OPEN on purpose. These surfaces are configuration and generated content, and both grow: a new toggle on a settings block or a new field on a generated document must reach a caller on the day it ships, not on the day somebody remembers to widen a mirror. A closed response model here would silently DROP the new key, which reads to the caller as “the product does not have that setting”.

The request side is the opposite and is mirrored exactly - see the module docstring for why the asymmetry is deliberate.

object
key
additional properties
any
pagination
Any of:
object
has_next
required

Whether there are more pages

boolean
limit
required

Items per page

integer
next_cursor
Any of:
string
page
required

Current page number (1-indexed)

integer
total
required

Total number of items

integer

422

Validation Error

object
detail
Array<object>
object
loc
required
Array
msg
required
string
type
required
string