# HubDB API Filtering with \_\_in Not Working

**URL:** <https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176>\
**Category:** APIs & Integrations\
**Tags:** timeline-and-extensions-apis\
**Created:** [August 18, 2025, 6:26pm UTC](https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176 "2025-08-18T18:26:32Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![RobertMarinho](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robertmarinho/32/86506_2.png) [@RobertMarinho](https://community.hubspot.com/u/RobertMarinho)\
**Post date:** [August 18, 2025, 6:26pm UTC](https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176/1 "2025-08-18T18:26:32Z")

</div>

Hello HubSpot support,

I’m experiencing an issue with the HubDB API when trying to filter rows using the \_\_in operator on a column of type “_foreign ID_”.

The API should return only the rows where the column matches the value. This was working previously and would correctly filter the rows as expected and suddenly the API is now returning all rows, completely ignoring the \_\_in filter.

I’ve double-checked:

- The model column does exist.
- The value is valid.
- The table is published and publicly accessible.
- The same query structure used to work before.

Tried:

- Testing with multiple values (model\_\_in=69918805253,123456789)
- Using different column types
- Publishing and unpublishing the table
- Confirming documentation still lists \_\_in as supported

According to the official docs: [Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/guides/api/cms/hubdb#filtering-and-sorting-table-rows), \_\_in should work for filtering by multiple values.

Thanks!

---

<div class="post-metadata">

**Author:** ![STierney](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stierney/32/186066_2.png) [@STierney](https://community.hubspot.com/u/STierney)\
**Post date:** [August 18, 2025, 8:49pm UTC](https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176/2 "2025-08-18T20:49:38Z")

</div>

Hey @RobertMarinho - thanks for posting in the Community!  
I’d like to call on some HubDB experts to see if they have any insight for us. [@matt\_scott](https://community.hubspot.com/t5/user/viewprofilepage/user-id/64119), @gabriel-nextiny, @jeremymandle - any thoughts?  
Shane, Community Manager

---

<div class="post-metadata">

**Author:** ![RobertMarinho](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/robertmarinho/32/86506_2.png) [@RobertMarinho](https://community.hubspot.com/u/RobertMarinho)\
**Post date:** [August 25, 2025, 3:36pm UTC](https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176/3 "2025-08-25T15:36:50Z")

</div>

I also opened a support ticket reporting the issue. The support team responded that it ended up being a bug on their end, which has since been fixed. Up to this moment, this filter has been working fine. Thanks.

---

<div class="post-metadata">

**Author:** ![RubenBurdin](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/rubenburdin/32/75212_2.png) [@RubenBurdin](https://community.hubspot.com/u/RubenBurdin)\
**Post date:** [August 26, 2025, 11:56pm UTC](https://community.hubspot.com/t/hubdb-api-filtering-with-in-not-working/138176/4 "2025-08-26T23:56:46Z")

</div>

Hi @RobertMarinho

Looks like you already confirmed the issue was on HubSpot’s side and the \_\_in filter is back to working as expected. For anyone landing here later: the official docs still confirm that \_\_in is supported for multi-value filtering

([Accounts Dashboard | HubSpot](https://developers.hubspot.com/docs/guides/api/cms/hubdb#filtering-and-sorting-table-rows) )

So if you see it returning all rows instead of applying the filter, it’s worth checking HubSpot’s status page or opening a support ticket since that usually signals a backend bug rather than your query.

One extra note: when you’re doing more complex filtering, especially combining \_\_in with foreign ID columns, keep an eye on the published state of your table. HubDB only evaluates filters against the published version, so if your unpublished table has the right values but the published one doesn’t, you’ll get odd results.

And sometimes, if you’re chaining HubDB with external systems or databases, teams use a sync layer like Stacksync so these filters stay consistent across all platforms without custom patches it saves chasing down quirks when HubSpot fixes a bug on their end.

Hope this helps.