You can update an existing audience by providing the fields to change.
Security
bearerAuth
Intercom-Versionstring(intercom_version)
Intercom API version.
By default, it's equal to the version set in the app package.
Default:"Preview"
Enum:"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"
Example:Preview
predicatesArray of objects(Predicate)
The predicates that define the audience matching rules.
Example:
[ { "attribute": "company.name", "type": "string", "comparison": "eq", "value": "Intercom" } ]
role_predicatesArray of objects(Predicate)
The role predicates that define audience role-based matching rules.
Example:
[ { "attribute": "role", "type": "role", "comparison": "eq", "value": "user" } ]
- The production API serverhttps://api.intercom.io/audiences/{id}
- The european API serverhttps://api.eu.intercom.io/audiences/{id}
- The australian API serverhttps://api.au.intercom.io/audiences/{id}
curl -i -X PUT \
https://api.intercom.io/audiences/123 \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: Preview' \
-d '{
"name": "VIP Customers (updated)",
"predicates": [
{
"attribute": "company.name",
"type": "string",
"comparison": "eq",
"value": "Intercom"
}
]
}'Audience updated
predicatesArray of objects(Predicate)
The predicates that define the audience matching rules.
Example:
[ { "attribute": "company.name", "type": "string", "comparison": "eq", "value": "Intercom" } ]
role_predicatesArray of objects(Predicate)
The role predicates that define audience role-based matching rules.
Example:
[ { "attribute": "role", "type": "role", "comparison": "eq", "value": "user" } ]
Response
{ "type": "audience", "id": "123", "name": "VIP Customers (updated)", "predicates": [ { … } ], "role_predicates": [ { … } ], "created_at": 1717200000, "updated_at": 1717200100 }