Chord

Chord Audiences API

Read API for activated audiences. Once the Dynamic Audiences API destination is enabled on an account, a sync mirrors a custom audience into the API and a server-side GET on /audiences returns that user's audience memberships with their attached attributes. Keyed by the CDP Blended User ID passed in the Chord-User-Id header and authenticated with a bearer token issued by Chord. Intended for on-site personalization; Chord's docs state it must always be called server-side.

GitHub

Documentation

📖
Documentation
https://docs.chord.co/audiences-api
📖
Authentication
https://raw.githubusercontent.com/api-evangelist/chord-commerce/refs/heads/main/authentication/chord-commerce-authentication.yml

Other Resources

🔗
ErrorCatalog
https://raw.githubusercontent.com/api-evangelist/chord-commerce/refs/heads/main/errors/chord-commerce-error-codes.yml

API entry from apis.yml

apis.yml Raw ↑ 
name: Chord Audiences API
description: Read API for activated audiences. Once the Dynamic Audiences API destination is enabled on
  an account, a sync mirrors a custom audience into the API and a server-side GET on /audiences returns
  that user's audience memberships with their attached attributes. Keyed by the CDP Blended User ID passed
  in the Chord-User-Id header and authenticated with a bearer token issued by Chord. Intended for on-site
  personalization; Chord's docs state it must always be called server-side.
humanURL: https://docs.chord.co/audiences-api
baseURL: https://analytics.api.chord.co
tags:
- Audiences
- Personalization
- CDP
properties:
- type: Documentation
  url: https://docs.chord.co/audiences-api
- type: Authentication
  url: authentication/chord-commerce-authentication.yml
- type: ErrorCatalog
  url: errors/chord-commerce-error-codes.yml