List the audiences content uses

GET

/content/delivery/v1/audiences

const url = 'https://api.ebitex.io/content/delivery/v1/audiences';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://api.ebitex.io/content/delivery/v1/audiences \
  --header 'Authorization: Bearer <token>'

The ids of the audiences that published content in the key’s delivery environment names: a variant’s condition or a page’s restriction. Ask Audience about these and no others (audiences on POST /audience/delivery/v1/resolve), which keeps the signed token small. Ids only, never names or rules. The SDKs read this for you.

Key: a delivery key (content.delivery.read).

Authorizations

apiKey

Responses

200

401

missing_api_key or invalid_api_key: no key was sent, or it is unknown, revoked or expired.

403

scope_denied: the key lacks this route’s scope. origin_denied or ip_denied: a browser-safe key was used from an origin or address outside its restrictions. app_not_available: Content is not enabled for the organization.

429

Quota exceeded; Retry-After says how long to wait. too_many_failed_authentications: too many bad keys from this address.