Feedback Submissions API - Retrieve more properties

[CarlosEMS]

Hello!

I am starting to work with the Feedback Submissions API. I managed to find all the internal names of the Feedback Submissions properties, however when I try to build a List request in https://developers.hubspot.com/docs/api/crm/feedback-submissions some key properties seem to be missing, and I don't know why:

• hs_survey_id
• hs_survey_name
• hs_survey_type
• hs_value
• hs_response_group
• hs_submission_name

Only hs_survey_channel is returned when I explicitly include all of the above in the property list for the request. No matter the language I use (cURL or another).

Is it due to the API being in Beta or is there something else going on that I need to ckeck?

Thanks!

[dennisedson]

@CarlosEMS 

Would you do us a favor and add an example of your code?

[CarlosEMS · Accepted solution]

Hello Dennis,

Oddly enough, 2 days ago and yesterday I tried and nothing, I have just tried now and I get all the desired properties!

The cURL request I tried, minus the API key, is as follows:

https://api.hubapi.com/crm/v3/objects/feedback_submissions?limit=100&after=342022468&properties=hs_c...

So now it works!

[AWare]

What is that 'after' value supposed to be? I've tried using converters to get dates in milliseconds and it's not working. How do you get actual dates as in your example it just looks like a random number? Thank you.

[CarlosEMS]

Hello,

As far as I remember it is an ID. If you go through the documentation of the feedback submissions endpoint you can see that the after parameter is
"The paging cursor token of the last successfully read resource"
Best,
Carlos

[AWare]

Hi Carlos

Thanks for this, I did try putting in gibberish as a value and it says I've tried an invalid paging token. The thing is if you don't know what these are in the first place, how are you supposed to specify an 'after' value? I know this API is in the beta phase but it could really use some work couldn't it :).
For anyone else reading, I sort of noticed that the difference between a given date in milliseconds and the 'after' value was roughly a factor of 10.992. Dividing the milliseconds of a date (https://currentmillis.com/) by 10.992 got me the value I needed, roughly. I was trying to get everything back but for only the previous week and...it worked well enough 😕 

[dennisedson]

@CarlosEMS ,

Every take a car to the mechanic and magically, it just works and they just stare at you like you are crazy? 🤣