Skip to main content

​
What’s Changing?

Previously, the Community API only supported a single brand_id per request. You can now request data for multiple brands at once using the new brand_ids parameter with a comma-separated list.
Note: Even if your account is associated with only one brand, we kindly ask that you update your API calls to use brand_ids to ensure continued compatibility.

​
What You Need to Update

Please adjust the query parameters based on your use case.

​
1. /community_interactions

Before (Single Brand):
After (Multi-Brand Support):

​
2. /community_interactions/unread_interaction_counts

Before (Single Brand — Path Parameter):
After (Multi-Brand Support — Query Parameter):
Body:

​
3. /tags

Before (Single Brand):
After (Multi-Brand Support):

​
4. /overview_stats

Before (Single Brand):
After (Multi-Brand Support):

​
5. /sentiment_distribution_stats

Before (Single Brand):
After (Multi-Brand Support):

​
6. /sentiment_time_series

Before (Single Brand):
After (Multi-Brand Support):

​
7. /top_keywords

Before (Single Brand):
After (Multi-Brand Support):

​
8. /volume_time_series

Before (Single Brand):
After (Multi-Brand Support):

​
Next Steps

  • Review and update any existing API calls that use brand_id to use the new brand_ids format.
  • Test your requests to confirm they return expected results for multiple brands.
  • No other parameters or functionality are affected — just a more flexible way to query!

​
Deprecation Timeline

Please note that support for the previous single-brand API format will end on May 1, 2025. We recommend updating your API calls promptly to avoid any disruptions. If you have any questions or need help making the update, feel free to reach out — we’re happy to assist.