PATCH /list_attributes/{list_attribute_id}

Overwrite the List Attribute with the provided id. Required arguments are identical to creating a new List Attribute.

Servers

Path parameters

Name Type Required Description
list_attribute_id Integer Yes

The ID of the List Attribute you'd like to update

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
key_field String No

The name of the object which holds targeting ids on your website

name String No

A unique, human-readable name for the List Attribute

archived Boolean No

Whether or not the List Attribute has been archived

description String No

A short description of the List Attribute

list_type String No

The type of data object which holds targeting ids on your website (cookies, query parameters, zip codes, Global JS variables)

Valid values:

  • "zip_codes"
  • "js_variables"
  • "cookies"
  • "query_parameters"
list_content String No

A comma separated string of IDs or ZIP Codes. Items will be matched against the key_field to determine if an active visitor should be targeted by the list. Note that if the list currently contains data, providing this value will overwrite the previous data.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.