> ## Documentation Index
> Fetch the complete documentation index at: https://developer.dashsocial.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Multi-Brand Support Added to the Community API (brand_ids)

> The Community API now supports requesting multiple brands per request via the new brand_ids parameter; single-brand brand_id support ends May 1, 2025.

## 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):**

```http theme={null}
GET https://community.dashhudson.com/community_interactions?brand_id=1
```

**After (Multi-Brand Support):**

```http theme={null}
GET https://community.dashhudson.com/community_interactions?brand_ids=1,2,3
```

### 2. `/community_interactions/unread_interaction_counts`

**Before (Single Brand — Path Parameter):**

```http theme={null}
GET https://community.dashhudson.com/brands/{brand_id}/community_interactions/unread_counts
```

**After (Multi-Brand Support — Query Parameter):**

```http theme={null}
POST https://community.dashhudson.com/community_interactions/unread_interaction_counts
```

Body:

```json theme={null}
{
  "source_updated_after": "2025-01-15T00:00:00-07:00",
  "source_updated_before": "2025-02-11T23:59:59-07:00",
  "types": "FACEBOOK_COMMENT,FACEBOOK_CONVERSATION,FACEBOOK_ADS_COMMENT,INSTAGRAM_COMMENT,INSTAGRAM_CONVERSATION,INSTAGRAM_ADS_COMMENT,TIKTOK_COMMENT,TIKTOK_COMMENT_MENTION,TWITTER_CONVERSATION,TWITTER_MENTION,TWITTER_QUOTE,TWITTER_RETWEET,YOUTUBE_COMMENT",
  "brand_ids": [1, 2, 3]
}
```

### 3. `/tags`

**Before (Single Brand):**

```http theme={null}
GET https://community.dashhudson.com/tags?brand_id=1
```

**After (Multi-Brand Support):**

```http theme={null}
GET https://community.dashhudson.com/tags?brand_ids=1,2,3
```

### 4. `/overview_stats`

**Before (Single Brand):**

```http theme={null}
GET https://community.dashhudson.com/brands/{brand_id}/overview_stats
```

**After (Multi-Brand Support):**

```http theme={null}
GET https://community.dashhudson.com/overview_stats?brand_ids=1,2,3
```

### 5. `/sentiment_distribution_stats`

**Before (Single Brand):**

```http theme={null}
PUT https://community.dashhudson.com/brands/{brand_id}/sentiment_distribution_stats
```

**After (Multi-Brand Support):**

```http theme={null}
POST https://community.dashhudson.com/sentiment_distribution_stats
```

```json theme={null}
{
  "brand_ids": [1, 2, 3, 4]
}
```

### 6. `/sentiment_time_series`

**Before (Single Brand):**

```http theme={null}
GET https://community.dashhudson.com/brands/{brand_id}/sentiment_time_series
```

**After (Multi-Brand Support):**

```http theme={null}
POST https://community.dashhudson.com/sentiment_time_series
```

```json theme={null}
{
  "brand_ids": [1, 2, 3, 4]
}
```

### 7. `/top_keywords`

**Before (Single Brand):**

```http theme={null}
PUT https://community.dashhudson.com/brands/{brand_id}/top_keywords
```

**After (Multi-Brand Support):**

```http theme={null}
POST https://community.dashhudson.com/top_keywords
```

```json theme={null}
{
  "brand_ids": [1, 2, 3, 4]
}
```

### 8. `/volume_time_series`

**Before (Single Brand):**

```http theme={null}
GET https://community.dashhudson.com/brands/{brand_id}/volume_time_series
```

**After (Multi-Brand Support):**

```http theme={null}
POST https://community.dashhudson.com/volume_time_series
```

```json theme={null}
{
  "brand_ids": [1, 2, 3, 4]
}
```

## 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.