APIs & Integrations

Tim_Munro
Participant | Elite Partner
Participant | Elite Partner

COS "Upload New File" Outage/Change?

SOLVE

With reference to this endpoint:

https://legacydocs.hubspot.com/docs/methods/files/post_files

 

We use the HubSpot API to send files to HubSpot file manager & then associate with engagements, e.g. notes.

 

Our integration logic has not changed recently, however in the last hr or so HubSpot has started consistantly responding with HTTP 400 codes & the error below:

{"status":"error","message":"Invalid file access option","correlationId":"0d557595-77a0-4a9a-af76-82498069762d"}

 

An example of the URL we call to add these files is:

https://api.hubapi.com/filemanager/api/v2/files?overwrite=true&hidden=true

 

This is reproducable on multiple HubSpot portals, are other API users hitting this?

 

1 Accepted solution
Tim_Munro
Solution
Participant | Elite Partner
Participant | Elite Partner

COS "Upload New File" Outage/Change?

SOLVE

Seems to be resolved now.

View solution in original post

5 Replies 5
Tim_Munro
Participant | Elite Partner
Participant | Elite Partner

COS "Upload New File" Outage/Change?

SOLVE

Issue looks to be when the hidden=true

cabotdeveloper
Participant

COS "Upload New File" Outage/Change?

SOLVE

We're facing the same issue, so that we removed hidden params. But is it a bug of system or Hubspot has changed the logic? 

I've looked up on the File API documentation and the hidden is still there, and didn't see any changelogs for this one.

I know that remove hidden is just workaround for avoiding this case.

0 Upvotes
Tim_Munro
Participant | Elite Partner
Participant | Elite Partner

COS "Upload New File" Outage/Change?

SOLVE

Thanks for sharing this; I have a ticket in with HubSpot support and they are investigating

0 Upvotes
Tim_Munro
Solution
Participant | Elite Partner
Participant | Elite Partner

COS "Upload New File" Outage/Change?

SOLVE

Seems to be resolved now.

cabotdeveloper
Participant

COS "Upload New File" Outage/Change?

SOLVE

Thank Tim!

Let me check again!

0 Upvotes