HubDB API Filtering with __in Not Working

Develop, Build & Integrate APIs & Integrations
1

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, __in should work for filtering by multiple values.

Thanks!

2

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, @gabriel-nextiny, @jeremymandle - any thoughts?
Shane, Community Manager

3

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.

4

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 )

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.