Hi @Jeffrey_Chimene,
Great to see you got it working! Thanks for sharing the details.
Your feedback about accepted and unsupported formats is noted, and I’ll be sure to bring it up internally.
I found the list of supported file types:
Is this list available via the API?
@Jeffrey_chimene The allowed file types per category are the following:
Images:
gif, jpg, jpeg, png, tif, tiff, jif, jiff, jp2, jpx, j2k, fpx, pcd, pdf, bmp, psd, pspimage, thm, yuv, cdr
Videos:
qt, mov, movie, hdmov, mnv, flv, f4p, hdv, divx, mp4, mp4v, mpg, mpeg, mpeg4, mpeg1, rm, vob, wmv, wm, avi, m4v, gvi, m2ts
Audio:
wav, wma, mp3, mp4, mid
Text:
doc, docx, log, msg, pages, rtf, txt, wpd, wps, err, text, pwd, notes, vcf, xdl, wp, wp4, wp5, wp7, wsd
Other:
csv, xlr, xls, xlsx, key, pps, ppt, pptx, xml, zip, ics
Maximum file size allowed: 10 MB per file.
@OmarAlmonte - Two issues spotted here regarding what Jeffrey mentioned.
First, the warning message being returned should be the along the lines of “Unsupported File Type” instead of the generic one being reported.
Second, the API documentation needs to be updated with the list of supported file types so that other developers can see what can be uploaded or not. Plus it would be helpful adding the Document Fragment to it as not every developer uses the SDK.
Thank you for the feedback. I’ll raise both issues internally so we can improve the message and update the API documentation accordingly.
@OmarAlmonte
Not wanting to see this drop through the cracks.
I didn’t see this issue on the tracker list?
Hi @Jeffrey_Chimene, this is noted, I’ll add it to the tracker shortly.
Hi @Jeffrey_Chimene,
Quick follow-up on your feedback, happy to share that improvements to the V2 Files API have been released. Here’s what’s new:
-
Clearer error messages for unsupported file types
When a file extension isn’t supported, the API now returns a descriptive error that lists the allowed extensions. No more guessing which file types are accepted — the error message itself tells you. -
Stronger upload validation
- Requests are now validated to ensure the file parameter is present and not empty.
- file_name is checked to confirm it includes a valid extension before the upload is processed.
- Improved API documentation
The createFile and updateFile endpoints now correctly specify application/json as the media type for the form parts (file_name, contact_id, is_public, file_association), so the request format shown in our docs matches what the API expects.
Thanks again for reporting!
@OmarAlmonte Thanks for the update. Has the SDK been updated, or do I still rely on the provisional code posted earlier in this thread?
Yes, the SDK was updated.
Come on, folks:
retrieveContactModelUsingGET1
I’m sure it seemed like a good idea at the time.