I went out of town on a vacation and came back to several custom apps I built all broken due to the CRM Search api endpoint no longer working. First, the new error I was receiving was that I had too many filter groups (4) and the maximum is 3.
{
"status": "error",
"message": "Invalid input JSON on line 29, column 5: too many filters per filterGroup (count: 4, max allowed: 3)",
"correlationId": "a82bbeae-9941-40b7-9bdb-04c9472132ab",
"category": "VALIDATION\_ERROR"
}
This is a change as the prior maximum was 5 as I had it commented in my code as a reference since I already handled this error in the past. After testing by setting my maximum to only 3 in a filter group, the new error that I began recieving is this below:
{
"status": "error",
"message": "The scope needed for this API call isn't available for public use. If you have questions, contact support or post in our developer forum.",
"correlationId": "b14c3c9a-8a20-4ff8-9de9-5cd04a3ff4f9",
"links": {
"support": "https://help.hubspot.com/",
"forum": "https://community.hubspot.com/t5/APIs-Integrations/bd-p/integrations"
},
"category": "MISSING\_SCOPES"
}
Again, I did not change any scopes on my side, but to be sure I went ahead and added ALL CRM scopes to my app and the same error is thrown. I have had this in production for over a year with no issues and all of a sudden these errors are occuring. Hubspot is closed on 5/1 for a regional holiday apparently, does anyone have any ideas on solutions for this?
Before telling me to go ahead and update my code to the graphql search instead, I already did that for one of my business critical items. It was not an easy change but I got it done quickly. For my other app it’s a much more complex change as the filter groups were updated dynamically, so I’ll have to write a lot of new code to do the same for graphql. If this is an internal HS error I would prefer not to do that.
Edit**
After really digging deep here I believe I realized what the root issue is… Hubspot rolled out the new “Leads” object… well my custom object is named “Leads” so the API path that uses my custom object name "leads"a is pointing to Hubspot’s new endpoint that’s not yet released. I am unable to change the name of my custom object so I will need to figure out what to do here.
I went out of town on a vacation and came back to several custom apps I built all broken due to the CRM Search api endpoint no longer working. First, the new error I was receiving was that I had too many filter groups (4) and the maximum is 3.
{
"status": "error",
"message": "Invalid input JSON on line 29, column 5: too many filters per filterGroup (count: 4, max allowed: 3)",
"correlationId": "a82bbeae-9941-40b7-9bdb-04c9472132ab",
"category": "VALIDATION\_ERROR"
}
This is a change as the prior maximum was 5 as I had it commented in my code as a reference since I already handled this error in the past. After testing by setting my maximum to only 3 in a filter group, the new error that I began recieving is this below:
{
"status": "error",
"message": "The scope needed for this API call isn't available for public use. If you have questions, contact support or post in our developer forum.",
"correlationId": "b14c3c9a-8a20-4ff8-9de9-5cd04a3ff4f9",
"links": {
"support": "https://help.hubspot.com/",
"forum": "https://community.hubspot.com/t5/APIs-Integrations/bd-p/integrations"
},
"category": "MISSING\_SCOPES"
}
Again, I did not change any scopes on my side, but to be sure I went ahead and added ALL CRM scopes to my app and the same error is thrown. I have had this in production for over a year with no issues and all of a sudden these errors are occuring. Hubspot is closed on 5/1 for a regional holiday apparently, does anyone have any ideas on solutions for this?
Before telling me to go ahead and update my code to the graphql search instead, I already did that for one of my business critical items. It was not an easy change but I got it done quickly. For my other app it’s a much more complex change as the filter groups were updated dynamically, so I’ll have to write a lot of new code to do the same for graphql. If this is an internal HS error I would prefer not to do that.
Edit**
After really digging deep here I believe I realized what the root issue is… Hubspot rolled out the new “Leads” object… well my custom object is named “Leads” so the API path that uses my custom object name "leads"a is pointing to Hubspot’s new endpoint that’s not yet released. I am unable to change the name of my custom object so I will need to figure out what to do here.
You first need to adjust your code to adhere to the new limit of 3 filter groups per request. Review your existing filter logic and modify it accordingly to ensure compliance with this updated restriction. Once you’ve made these adjustments, you should be able to avoid the “too many filters per filterGroup” error.
Regarding the “MISSING_SCOPES” error, even after adding all CRM scopes to your app, it’s essential to verify the authentication and permissions setup. Confirm that your app has the necessary scopes to access the required resources.
Thanks for the reply, I should have closed this out. The issue was not the filter group limit, although I did adjust to 3. The issue was I had a custom object named “Leads” and while I was on vacation, Hubspot rolled out an actual “Leads” object. All of the API Endpoints that allow for both the custom object name OR id were set to use the name which makes my code more readable. All of a sudden all of my API calls were pointing to this new Hubspot Leads object which I do not have in my plan. The solution was simply to update all of my API endpoints to use the object ID instead of object Name since Hubspot tookover the “Leads” name I had in use.