Incomplete List of Properties - Recently Updated Contacts


#1

I am trying to update an internal system with recently updated contacts from HubSpot but when I call “https://api.hubapi.com/contacts/v1/lists/recently_updated/contacts/recent?hapikey=” and view the contact properties it doesn’t include all properties.
If I were to call “https://api.hubapi.com/contacts/v1/contact/vid/XXXXXXXX/profile?hapikey=” for that same contact I get a bunch of additional properties…including the ones that I need.
Any idea how to get around this issue?
Thanks,
Bill


#2

@wghipps You could use the property tag on the get contact by VID endpoint to get just the contact properties you want. Here is the documentation for that endpoint. http://developers.hubspot.com/docs/methods/contacts/get_contact


#3

I am already getting all of the properties when using get contact by VID but when I get RECENTLY UPDATED contacts it is not including all of the properties.


#4

@wghipps gotcha, The way we have it set up to restrict a total payload size that would be sending out to prevent any failed requests. You could still use the property tag here to grab the properties you need most. You can use the count parameter as well to limit the amount of contacts you bring back as well in the case you name a large number of properties and want to prevent any timeouts from occurring.


#5

When I call the following with no properties specified I get “all” of the properties(including one called “hs_email_optout”.
GET https://api.hubapi.com/contacts/v1/contact/vid/:contact_id/profile

When I call the following with no properties specified I get only 4 properties.
GET https://api.hubapi.com/contacts/v1/lists/recently_updated/contacts/recent

Is there something in the configuration that limits what properties are exposed thru the API?

We are trying to run a process nightly to get contacts updated in the past 24 hours and see update our system if they have opted out to a newsletter.


#6

@wghipps The first endpoint is designed to bring back only one contact. Therefore we can return all of the properties with out causing a timeout due to payload size. The second endpoint is designed to bring back multiple contacts so we restrict the number of properties that will come back with each one.


#7

I understand that but when I call GET https://api.hubapi.com/contacts/v1/lists/recently_updated/contacts/recent and specify “hs_email_optout” I don’t get the property back. Can this property be returned? What is the limit on properties?


#8

@wghipps Can I see the call you are making? I can get it back when I hit the endpoint. Here is the GET call I am making.

 https://api.hubapi.com/contacts/v1/lists/recently_updated/contacts/recent?hapikey=xxxxx&property=hs_email_optout

This is part of the response.
“properties”: {
“lastmodifieddate”: {
“value”: “1476546901287”
},
“hs_email_optout”: {
“value”: “”
}
},


#9

This was extremely frustrating. We wasted hours and hours of tracing and debugging on this issue.

Why doesn't the API documentation mention this restriction! We should not discover it the hard way.