CatalogQueryItemsForTax throws an INTERNAL_SERVER_ERROR exception

Hi Square Team,

I encountered an exception when using the “Search Catalog” API.

If a tax is applied to all Items, when querying the associated Items through TaxId, the Square API will throw an INTERNAL_SERVER_ERROR exception.

Tax ID: JH5KRLOCDHMBSKSGNDLCROTQ
Request Body:

{
    "query": {
        "items_for_tax_query": {
            "tax_ids": ["JH5KRLOCDHMBSKSGNDLCROTQ"]
        }
    },
    "limit": 10
}


Is this restriction newly added recently? This is the first time I have encountered this problem.

Looking forward your reply.
Thanks,
Murphy

:waving_hand: I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Additional Documentation

Catalog API
Call the SearchCatalogObjects Endpoint
Square Developer

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

Are you still experiencing this issue? I just tested this query and it worked as expected. :slight_smile:

Yes, this problem has been happening all the time, and I don’t know when it first appeared.

If you need me to provide more information to help you troubleshoot the problem, please contact me at any time.

What’s your application ID? :slight_smile:

Here, our appId is sq0idp-oWh0xHjr2Y2OEniHaO7hOQ.

Great! The team is looking into this. :slight_smile:

Hi Bryan, Have you found out the cause of the problem? I’m not sure whether this is a BUG or the expected result of Square.

Hi Bryan, Hope you’re doing well! I just wanted to follow up on my previous message regarding [CatalogQueryItemsForTax exception]. Looking forward to hearing from you when you get a chance.

The team is still investigating the issue. I’ll be sure to reach out when I have an update. :slight_smile:

Hi Bryan, Hope you’re doing well! Please keep me post if you have an update.

Are you still getting the error? This should be fixed now. :slight_smile:

Hi Bryan,

I’m not sure whether the issue has actually been resolved, as I’m still able to consistently reproduce the same exception on my side. Could you please double-check if there’s anything else that might be affecting this?

Thanks,
Murphy

Hmm okay, reaching out to the team. :slight_smile:

Thanks Bryan, Hope you’re doing well! Please keep me post if you have an update.

Thanks Bryan, Hope you’re doing well! Please keep me post if you have an update.