Audience guide

Keep people and audiences distinct.

A Customer Profile holds identity. A List records an explicit membership and its source. A Segment computes membership from an approved definition. None of these grants marketing consent.

Create a Profile

Use an organization-wide key with audience:write. Supply an email or phone and a stable Idempotency-Key. A repeat with the same body returns the original result; changing the body returns 409.

curl https://api.fendsy.com/v1/audience/profiles   -H "Authorization: Bearer $FENDSY_API_KEY"   -H "Content-Type: application/json"   -H "Idempotency-Key: customer-1042"   -d '{"email":"buyer@example.com","firstName":"Riya"}'

The response includes the Profile ID. Keep that ID for orders, Lists and customer history. Creating a Profile does not mean the person signed up for a SaaS account or subscribed to marketing.

Maintain a static List

Create a List at POST /v1/audience/lists, then add one existing Profile with POST /v1/audience/lists/{listId}/members. Read members with a bounded cursor. Adding an existing member preserves the original join source. Archive and restore are explicit operations.

curl https://api.fendsy.com/v1/audience/lists   -H "Authorization: Bearer $FENDSY_API_KEY"   -H "Content-Type: application/json"   -H "Idempotency-Key: list-autumn-2026"   -d '{"name":"Autumn customers"}'

Draft, then activate a Segment

Read GET /v1/audience/segments/catalog for valid conditions and source health. Submit a version 1 definition as a draft. Activation pins a revision and queues evaluation; a 202 response means the evaluation was accepted, not that membership is already fresh.

Use the workspace consent workflow for consent evidence. Server Audience writes cannot opt a person into marketing. Read the API reference for request schemas.