How to Structure Filters for Rollup Properties in Notion API

Other Questions Notion
1

I’m struggling with the correct syntax for filtering rollup properties using the Notion API. I’m trying to filter a rollup that displays the original values from a select property type.

Here’s what I attempted, but it’s not working:

{
    "filter": {
        "property": "ProjectState",
        "rollup": {
            "any": {
                "select": {
                    "equals": "Running"
                }
            }
        }
    }
}

This rollup should show original values from a select field, and I want to filter records based on whether the select contains a particular value. Can anyone help me find the right way to structure this filter? I’ve tried several methods but can’t seem to correct the nested structure.

2

This sounds like a rollup config issue, not just filter syntax. I had the same problem and it turned out my rollup was showing a formula result instead of original values, even though it looked right in the interface. Check your rollup property settings - make sure it’s set to “Show original” and not “Show unique values” or any calculation. Also heads up - some rollup properties need the “number” filter type instead of what you’d expect, depending on how Notion processes them internally. If you’re still stuck, try querying the database without filters first and check the actual rollup data structure in the response. You’ll see if the nested values are coming through as select objects or in some other format.

3

I hit this exact problem a few months ago with rollup filters. Your structure looks right, but there’s usually a mismatch between what Notion’s interface shows and what the API actually wants. First, double-check that your rollup property shows original values - not a formula or count. The API handles these differently even when they look the same in the UI. Also verify your property name casing. “ProjectState” has to match exactly what’s in your database schema. I’ve burned hours debugging filters just to find a capitalization error. What worked for me: run a simple query without filters first to see how your rollup data actually looks in the response. This shows whether the nested values come back as select objects or in some other format. The API docs are pretty misleading about rollup structures since they depend on how the source property is configured.

4

Had the same problem last week - switch any to every based on your rollup setup. Double-check that your source database’s select property name matches exactly what you’re filtering on. Notion’s API can be finicky about rollup aggregation types.