# Missing properties on get file signed url

**URL:** <https://community.hubspot.com/t/missing-properties-on-get-file-signed-url/69662>\
**Category:** APIs & Integrations\
**Created:** [November 21, 2022, 1:41pm UTC](https://community.hubspot.com/t/missing-properties-on-get-file-signed-url/69662 "2022-11-21T13:41:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thulani](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@thulani](https://community.hubspot.com/u/thulani)\
**Post date:** [November 21, 2022, 1:41pm UTC](https://community.hubspot.com/t/missing-properties-on-get-file-signed-url/69662/1 "2022-11-21T13:41:46Z")

</div>

The documentation here [CMS API | Files (hubspot.com)](https://developers.hubspot.com/docs/api/files/files) shows multiple properties that should be returned as shown below

 ![thulani_0-1669038090614.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/7/f/7f65668457a722cd191ae1e0243540b84dd1602b.png)

Only the url however is returned on calling these endpoints as shown below

 ![thulani_1-1669038099396.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/3/3/335f287924672399a42280a2ca65d2607a2ab156.png)

---

<div class="post-metadata">

**Author:** ![Jaycee\_Lewis](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/jaycee_lewis/32/61352_2.png) [@Jaycee\_Lewis](https://community.hubspot.com/u/Jaycee_Lewis)\
**Post date:** [November 21, 2022, 10:49pm UTC](https://community.hubspot.com/t/missing-properties-on-get-file-signed-url/69662/2 "2022-11-21T22:49:52Z")

</div>

Hey, @thulani 👋 Thanks for the great question. What is the file type for the file you are getting the signed URL for?

I have a working example from another thread we can use here to test with:

- I created test dataset as a CSV

- I uploaded the file

- I attached the file to an object

- I used the [GET Signed URL](https://developers.hubspot.com/docs/api/files/files) endpoint from the Files API  
My Request  
`GET https://api.hubspot.com/filemanager/api/v3/files/91671366960/signed-url​`

- It retuned the following response body

Thanks for the additional information.

Best,

Jaycee

---

<div class="post-metadata">

**Author:** ![thulani](https://avatars.discourse-cdn.com/v4/letter/t/ee7513/32.png) [@thulani](https://community.hubspot.com/u/thulani)\
**Post date:** [November 23, 2022, 11:46am UTC](https://community.hubspot.com/t/missing-properties-on-get-file-signed-url/69662/3 "2022-11-23T11:46:57Z")

</div>

Thanks for the response Jaycee  
The file type here is a pdf. A question from your steps, was the attachment of the file to an object necessary for reproducing this? Are any of those properties related to that?  
If these properties show up only in certain scenarios that could be good to document and indicate in the published Open API specs. Various tools that generate clients based on such specs will put validation in place to indicate these as required and indicate this to the JSON deserializers, which of course causes issues when the properties end up not being there.