Updates the marketing consent declaration of an existing contact

PATCH/jsonapi/contact-marketing/{id}

Where id is the identifier of the contact

For client-credentials integrations, supply your assigned adviser identifier in the UserId header. See request headers and data access.

Access

Bearer authentication. Confirm your scopes, data access and required adviser context.

Request parameters

id path required

·idinteger

format: int32

Request body

application/vnd.api+json

Example request body

Illustrative request using reviewed sample values. Replace sample values, resource types and IDs with your own. Optional fields are shown for illustration; follow the field descriptions and business rules. Send only the attributes or relationships you want to change, and match data.id to the ID in the URL.

{
  "data": {
    "type": "contact-marketing",
    "id": "1001",
    "attributes": {
      "hasMarketingConsent": false
    }
  }
}

Request documentobjectContactMarketingDocument ↗

dataobjectrequiredContactMarketing ↗

Example request

Use your supplied API base URL and replace path placeholders such as {id}. These examples run in your backend or terminal, where your credentials are kept.

curl --globoff --request PATCH "${API_BASE_URL}/jsonapi/contact-marketing/{id}" \
  --header "Authorization: Bearer $ACCESS_TOKEN" \
  --header "UserId: $ADVISER_CONTACT_ID" \
  --header 'Accept: application/vnd.api+json' \
  --header 'Content-Type: application/vnd.api+json' \
  --data '{
  "data": {
    "type": "contact-marketing",
    "id": "1001",
    "attributes": {
      "hasMarketingConsent": false
    }
  }
}'

Responses

200 response

application/vnd.api+json

200 responseobjectContactMarketingDocument ↗

metaobjectread only

jsonApiobjectread only

linksall ofread only

dataobjectrequiredContactMarketing ↗

includedarray · nullableread only

For guidance beyond this operation's schema, see troubleshooting and JSON:API explained.