API referenceAudiences
Add up to 100 contacts to an audience
POST
Same idempotent-add + automation-enrollment behavior as the single-member endpoint, tallied into a summary. A contact_id not owned by the tenant is a per-item failure, not a batch abort.
bearerAuthheader
AuthorizationBearer <token>API key sent as Authorization: Bearer <key>. Looked up by SHA-256
hash (email_core::sha256_hex) against api_keys.hash; revoked
keys and keys belonging to a suspended tenant are rejected. See the
top-level Authentication section for permission levels.
id*stringapplication/json- body
contact_ids*array<string>Items
1 <= items <= 100Batch processed.
application/json- response
data?array<>summary?curl -X POST "https://example.com/v1/audiences/string/members/bulk" \ -H "Content-Type: application/json" \ -d '{ "contact_ids": [ "string" ] }'{ "data": [ { "contact_id": "string", "added": true, "error": "string" } ], "summary": { "added": 0, "skipped": 0 }}