Unable to parse search query for hubapi File manager

Hey folks,

Out of the blue today, we’re getting server errors on one of our integrations and we’re getting the following message when attempting to login.

Client error: `GET https://api.hubapi.com/filemanager/api/v2/folders?&parent_folder_id=119886235194` resulted in a `400 Bad Request` response: {“status”:“error”,“message”:“Unable to parse search query”,“correlationId”:“7842185f-7912-46e3-8391-f0d4a7c13d44”}

We haven’t adjusted any of these scripts recently, so we’re unsure why we’d be getting a 400 error here. In another thread, I noticed that it looks like there were differences between & and ? being used. Is part of our URL wrong?

Hi @Molinero9249

Typically the & (ampersand) is used to add additional query parameters after the ? (quention mark).

e.g. domain.com**?query_1=one&**query_2=two

While your query should still work… I’d remove the ampersand:

https://api.hubapi.com/filemanager/api/v2/folders?parent_folder_id=119886235194

It’s possible a code tweak at HubSpot’s end may have rejected the query based on the URL structure (probably looking for a query it couldn’t find).

Have fun

Mike

p.s. I’m a HubSpot Partner, not a HubSpot employee

We also started hitting this issue yesterday. Much like you, these API calls have been running fine for a very long time with no issues. I logged a support ticket with HubSpot however no feedback as of yet. Our URL does not have any extra ampersands. I suspect this is a newly introduced HubSpot API bug.

Did you find any workaround?

No, not yet. We’ve commented out the part of our code where it makes it a parent folder, since it’s thankfully not a super high profile aspect of our integration, and we’re still working through how to re-code this.

We’re running into the same issue.

https://api.hubapi.com/filemanager/api/v2/folders?offset=0&limit=100

Hey all!
This is a known issue and we are working on a fix! Apologies for any disruption this may have caused!

Dennis,

Okay, sounds good. When will we know to start working on it again? Will you post in here, have it in a developer update, etc.? Just want to let my team know that if it’s on Hubspot’s end at the moment don’t lose hairs over trying to fix it.

@Molinero9249 ,

Try now! Was just informed that a rollback was pushed and should be resolving any errors :crossed_fingers:

For one of our customers a similar error appears with using Hubspot’s CTA:

Hi @mwx_kk and Happy Friday!
Thanks for asking the HubSpot Community and thanks for sharing the screenshot!
This happened while using which method and which endpoint, please?
What are you trying to achieve?
The more info, screenshots (without sensitive/confidential information), and details you can provide, the better the Community can assist.

I’d love to put you in touch with some of our Top Experts: Hi @sylvain_tirreau, @Anton and @Bortami do you have suggestions to help @mwx_kk, please?
Have a great weekend and thanks so much in advance for your valuable contributions!
Bérangère

Hi @mwx_kk, I hope that you are well!
Do you still need help?
If yes, can you please share additional information with the Community?
Thanks and enjoy the weekend!
Bérangère