Skip to main content
PUT
Update a component setting

Authorizations

Authorization
string
header
required

Path Parameters

component_id
string
required
setting_name
string
required

Body

application/json

Body of a PUT /v2/campaigns/{campaign_id}{version:(/version/.+)?}/components/{component_id}/variables/{setting_name} request.

display_name
string | null
name
string
priority
string
Example:

"10"

tags
string[]
type
enum<string>

Type of the setting. When omitted, the setting keeps its stored type. A different type changes the setting to that type. When the new type has no field that the stored type lacks, every field carries over, for example between ENUM and ENUM_LIST, or SOCKET and MULTI_SOCKET. Otherwise the name, display name, description, tags, priority, values and source carry over, and the request sends the other fields of the new type. A variable and a socket cannot change into each other: unexpected_setting_type. A MULTI_SOCKET changes to SOCKET only while one component is installed into it: multiple_components_installed_into_single_socket. A change to a type with a field that the stored type lacks cannot also change the source from INHERITED to LOCAL: setting_validation_exception.

Available options:
CLIENT_KEY_FLOW
authorization_url
string
client_secret_key_id
string
description

Choose between static or dynamic description. Buildtime expressions use VariableDescriptionBuildtimeContext.

redirect_url
string
source
enum<string>

Where this setting takes its value from. LOCAL uses the values stored on this component. INHERITED uses the same-named setting of the nearest ancestor component that is not itself INHERITED. PARAMETER uses the same-named parameter of the socket this component is installed into. Omit to leave it unchanged; it is applied independently of values. To reconnect a setting to its ancestor, send INHERITED without values: the values stored on this component are kept but no longer used. Changing an INHERITED setting to LOCAL without values copies the inherited values onto this component. Changing it to LOCAL with values stores only the values sent, so send every locale the setting should keep. Either way, assets of the ancestor component that the stored values reference are copied onto this component.

Available options:
INHERITED,
LOCAL,
PARAMETER
values
object

Values to store on this component, keyed by locale or default. Omit to leave them unchanged. The map sent replaces every stored value, so a locale not sent is removed. Sending values does not change source: an INHERITED setting keeps using its ancestor's value until source is set to LOCAL.

Response

Successful response

description
required

The description as configured: a literal value, or an expression (type:string) when defined dynamically. Buildtime expressions use CampaignBuildtimeContext.

display_name
string
required
name
string
required
priority
string
required
Example:

"10"

tags
string[]
required
type
enum<string>
required
Available options:
ADMIN_ICON
source
enum<string>

Where this setting takes its value from. LOCAL uses the values stored on this component. INHERITED uses the same-named setting of the nearest ancestor component that is not itself INHERITED. PARAMETER uses the same-named parameter of the socket this component is installed into. For an INHERITED setting, values shows what is stored on this component, not the value in effect; the built setting reports that.

Available options:
INHERITED,
LOCAL,
PARAMETER
values
object

Open map of setting values keyed by value key. There is no fixed or maximum number of keys. Any string key may be present; each value uses the same shape for this setting's type. The properties listed here are common examples only and are not required.