What's new 
Is anyone using the “contnet management” APIs? There are three documeneted public facing endpoints “Generate pre-signed upload URL”, “Verify file upload to Amazon S3” & “Delete files from Amazon S3”.
While I inspect web traffic and attempt to upload a file I see that the internal endpoints for “https://yourORG.hexnodemdm.com/generate_signed_url/”, “https://yourORG.hexnodemdm.com/save_files_information/” & “https://yourORG.hexnodemdm.com/getFiles/” are used.
What’s the purpose of the public facing APIs if they are not used while uploading files as content in Hexnode? I would like to update this content outside of the web portal and the public APIs don’t seem to point to a file if I follow the path for generating a presigned url, then uploading with the returned UUID, I always get a file not found response.
There is probably a larger discussion to be had here about the internally documented endpoints, I and likely others would like to use these so we can get value out of the platform. Is there a plan to better document these endpoints and make them “publically” availiable in the sense that an API key can authenticate vs. the Cookie/ Session authentication method?
Thank you for the conversation.
27 Views
