// Add a reaction to an activity
let reaction = try await feed.addReaction(
activityId: "activity_123",
request: .init(
custom: ["emoji": "❤️"],
type: "like"
)
)
// Remove a reaction
_ = try await feed.deleteReaction(activityId: "activity_123", type: "like")Reactions
Overview
You can react to both activities and comments. It's possible to configure any reaction types that best fit your app.
When adding reactions and the enforce_unique flag is set to true, the existing reaction of a user will be overridden with the new reaction. Use this flag if you want to ensure users have a single reaction per each comment/activity. The default value is false, in which case users can have multiple reactions.
// Add a reaction to an activity
val reaction: Result<FeedsReactionData> = feed.addActivityReaction(
activityId = "activity_123",
request = AddReactionRequest(
custom = mapOf("emoji" to "❤️"),
type = "like",
// Optionally override existing reaction
enforceUnique = true
)
)
// Remove a reaction
val deleteResult: Result<FeedsReactionData> = feed.deleteActivityReaction(
activityId = "activity_123",
type = "like"
)Overview of the reaction model
FeedsReactionResponse
| Name | Type | Description | Constraints |
|---|---|---|---|
activity_id | string | ID of the activity that was reacted to | Required |
comment_id | string | ID of the comment that was reacted to | - |
created_at | number | When the reaction was created | Required |
custom | object | Custom data for the reaction | - |
type | string | Type of reaction | Required |
updated_at | number | When the reaction was last updated | Required |
user | UserResponse | User who created the reaction | Required |
By default creating a reaction doesn't create an activity. Pass create_notification_activity: true to add a notification to the reacted-to user's notification feed — see Reaction notification creation timing (added June 23, 2026). The response includes notification_accepted and notification_task_id; notification_created is deprecated and mirrors notification_accepted.
When you read a feed the reactions are included. Here's an example:
feed.getOrCreate()
feed.state.activities.collect { activities ->
// Last 15 reactions on the first activity
println(activities.first().latestReactions)
// Count of reactions by type
println(activities.first().reactionGroups)
}Querying Reactions
You can query reactions to both activities and comments. Here are some examples:
// Query reactions to a specific activity
val activityReactionList = client.activityReactionList(
ActivityReactionsQuery(
activityId = "activity-123",
filter = ActivityReactionsFilterField.reactionType.equal("like"),
)
)
activityReactionList.get()
activityReactionList.state.reactions.collect { reactions ->
// Handle activity reactions
}
// Query reactions to a specific comment
val commentReactionList = client.commentReactionList(
CommentReactionsQuery(
commentId = "comment-456",
filter = CommentReactionsFilterField.reactionType.equal("like"),
)
)
commentReactionList.get()
commentReactionList.state.reactions.collect { reactions ->
// Handle comment reactions
}Batch query activity reactions
batchQueryActivityReactions fetches a single user's reactions across a whole page of activities in one call, so you can merge own_reactions back onto a cached page without calling query reactions once per activity. Pass up to 100 activity IDs per request. The response contains reaction rows only (no activity payloads) and supports the same filter, sort, and pagination options as the single-activity query.
On a client-side connection the returned reactions are always the connected user's. Server-side, pass user_id to choose whose reactions to fetch.
// Fetch the connected user's reactions across a page of activities in one request.
const response = await client.batchQueryActivityReactions({
activity_ids: activities.map((activity) => activity.id),
// Optional: filter by reaction type, sort, or paginate with next/prev
filter: { reaction_type: "like" },
});
// Merge response.reactions back onto the activities as own_reactions
console.log(response.reactions);Reaction queryable built-in fields
Both batchQueryActivityReactions and batchQueryCommentReactions accept these filter fields.
| name | type | description | supported operations | example |
|---|---|---|---|---|
reaction_type | string or list of strings | The type of reaction | $in, $eq | { reaction_type: { $in: [ 'like', 'heart', 'thumbs_up' ] } } |
user_id | string or list of strings | The ID of the user who created the reaction | $in, $eq | { user_id: { $eq: 'user_123' } } |
created_at | string, must be formatted as an RFC3339 timestamp | The time the reaction was created | $eq, $gt, $gte, $lt, $lte | { created_at: { $gte: '2023-12-04T09:30:20.45Z' } } |
Batch query comment reactions
batchQueryCommentReactions is the comment counterpart of batch query activity reactions. It fetches a single user's reactions across up to 100 comments in one call, returning reaction rows only (no comment payloads). Use it to hydrate own_reactions for a whole comment thread without a request per comment. It accepts the same filter fields, sort, and pagination options.
As with activities, a client-side connection returns the connected user's reactions; server-side, pass user_id.
const response = await client.batchQueryCommentReactions({
comment_ids: comments.map((comment) => comment.id),
filter: { reaction_type: "like" },
});
console.log(response.reactions);