# Filtering conversation threads by status not working

**URL:** <https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471>\
**Category:** APIs & Integrations\
**Tags:** cms-content\
**Created:** [January 23, 2024, 6:29pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471 "2024-01-23T18:29:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JUrban78](https://avatars.discourse-cdn.com/v4/letter/j/8e7dd6/32.png) [@JUrban78](https://community.hubspot.com/u/JUrban78)\
**Post date:** [January 23, 2024, 6:29pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/1 "2024-01-23T18:29:39Z")

</div>

Hi, im having trouble filtering my conversation threads by **status** field (in documentation its called **threadStatus** )

Im using endpoint **conversations/v3/conversations/threads?threadStatus=OPEN** but getting results with **status: ‘CLOSED’** aswell.

Also i noticed this API is still in BETA so maybe it has still some bugs.

My sources

> **[Conversations API - HubSpot docs](https://developers.hubspot.com/docs/api-reference/legacy/conversations/guide)**
>
> Use the conversations API to manage inboxes, channels, threads, and messages.

> **[Conversations API - HubSpot docs](https://developers.hubspot.com/docs/api-reference/legacy/conversations/guide)**
>
> Use the conversations API to manage inboxes, channels, threads, and messages.

---

<div class="post-metadata">

**Author:** ![zach\_threadint](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/zach_threadint/32/46318_2.png) [@zach\_threadint](https://community.hubspot.com/u/zach_threadint)\
**Post date:** [January 24, 2024, 12:12am UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/2 "2024-01-24T00:12:24Z")

</div>

Hi @JUrban78 👋

As far as I can tell, the _threadStatus_ query parameter is only applied if the _associatedContactId_ query parameter is also defined.

I hope this proves useful. Please let me know if you have any follow-up questions.

---

<div class="post-metadata">

**Author:** ![JUrban78](https://avatars.discourse-cdn.com/v4/letter/j/8e7dd6/32.png) [@JUrban78](https://community.hubspot.com/u/JUrban78)\
**Post date:** [January 24, 2024, 1:53pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/3 "2024-01-24T13:53:34Z")

</div>

And why is it like that? I think its pretty reasonal and common usecase to have this functionality and return OPEN/CLOSED threads without providing _associatedContactId_

Are there any plans to implement this in near future?

---

<div class="post-metadata">

**Author:** ![AndrewKennedy](https://avatars.discourse-cdn.com/v4/letter/a/7ea924/32.png) [@AndrewKennedy](https://community.hubspot.com/u/AndrewKennedy)\
**Post date:** [January 27, 2024, 7:58pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/4 "2024-01-27T19:58:15Z")

</div>

I agree that the threadStatus parameter is useless as implemented for a large number of possible use cases.

I’ve submitted the following Idea and tagged you on it. Hopefully it can go somewhere. In the meanwhile, I guess we have to implement the filtering in our business logic.

[https://community.hubspot.com/t5/HubSpot-Ideas/Change-functionality-of-threadStatus-in-Conversations-API-to/idi-p/912625#M167128](https://community.hubspot.com/t5/HubSpot-Ideas/Change-functionality-of-threadStatus-in-Conversations-API-to/idi-p/912625#M167128)

---

<div class="post-metadata">

**Author:** ![EricHirsh](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/erichirsh/32/98230_2.png) [@EricHirsh](https://community.hubspot.com/u/EricHirsh)\
**Post date:** [September 25, 2024, 6:50pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/5 "2024-09-25T18:50:34Z")

</div>

We’re considering this! Would love to hear more about your use cases for the \*why\* behind these sorts of filters and sorts here in this Developer Slack thread [Slack](https://hubspotdev.slack.com/archives/C2YHAHB6K/p1727274837457329)

---

<div class="post-metadata">

**Author:** ![JoeP2](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/joep2/32/197801_2.png) [@JoeP2](https://community.hubspot.com/u/JoeP2)\
**Post date:** [July 24, 2024, 10:06pm UTC](https://community.hubspot.com/t/filtering-conversation-threads-by-status-not-working/98471/6 "2024-07-24T22:06:38Z")

</div>

Same. I expect GET [https://api.hubapi.com/conversations/v3/conversations/threads?threadStatus=OPEN](https://api.hubapi.com/conversations/v3/conversations/threads?threadStatus=OPEN) to get list of open threads. However, I’m getting a bunch of threads with a closed status in the response. It seems to be ignoring this filter.

I lost an hour today trying to diagnose why I get closed threads when I filter on threadStatus=OPEN.

Please fix this. It’s both useful and an obvious omission.
