OVERVIEW
Hi,
I'm using Intapp Integrate to connect to our HighQ instance, with the intention of downloading attachments from an iSheet column. While I can connect to the instance, locate the iSheet column and use the API as described in the following article to connect and confirm (200 response) that the attachment is there - I can't seem to get the file. The content response is empty (or at least Intapp Integrate thinks it is), and I'm expecting a binary stream of the attachment. Has anyone tried to use this method of getting an iSheet attachment via the API with success? Is there any other way I can test this to make sure it's not Integrate which is causing the issue? Sorry for the novice questions but I'm a bit stuck and could do with some help to get over the final hurdle!
API guidance: https://collaborate.highq.com/sitepoint/viewWikiPage.action?metaData.siteID=714&metaData.wikiID=26415
Thanks,
David
Blog Comments
Cheers Andrew. The API works for me in Postman (using the Send and Download option), however like David, I'm having issues downloading the attachment using Intapp Integrate which is an appliance used for all sorts of data integration. I've sent Intapp a support ticket since the issue is with the appliance. Thanks again for your help.
Hi Mani Sodhi (David Searle), the reason you are receiving a blank (body) response is because you need to supply a "User-Agent" (header) string. It can be anything, but it needs to be sent with your request, otherwise a blank 200 will be your response.
This is not mentioned in any of the API documentation, and was found through trial and error, on other upload/download of binary content.
Imran Aziz, can we get the documentation updated, or something mentioned in the Getting Started, as this small oversight trips a lot of people up (includin myself). It might be worth also including why this is the case from the API dev's (mandatory for audit logs?) Thanks in advance.
Hope this helps,
Andrew
Hi David - did you ever get a response regarding this issue. I seem to be having the same problem.
Thank you so much for your help with this Andrew Quinn, glad it wasn't me going crazy! Have logged a ticket with support. Imran Aziz - FYI.
Hi David Searle, I can confirm this is endpoint (in Collaborate 5.1.5) is not working (again) . Your best bet is to raise this as a bug with HighQ Support - you might be lucky and have it fixed in a point release.
Comments
12 Comments