Hoping there is someone who can shed some light on what I feel is a strange issue with the files API.
The situation is that I have a stream of incoming emails, picked up by a HubSpot inbox and truned into conversation objects. When I process teh conversation objects, I can discover any whether the email has any attached files. If it does, I can find the fileID and the associated signed URL.
Having the URL I can read thr file and parse its internal contents, etc. But the fileID value I obtain seems to be useless to discover file details via the
files/v3/files/{fileId}
or
/files/v3/files/{fileId}/signed-url
requests. Both variants always return a 404 code.
Does anyone have any ideas on a solution/work-around here?
Steve