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.

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/chord-audiences-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

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