At issue is the batch or post versions of the HubSpot API, propertyWithHistory doesn’t work.
A post of this, for example, https://api.hubapi.com/crm/v3/objects/contacts/search?propertiesWithHistory=firstname doesn’t return any of the property firstname history, just the contact objects properties indicated in the body.
Is there any way to trigger the group results returned for contact objects to include the propertiesWithHistory without having to look up each individual contact object?
Understand that a webhook could be created to update information when it’s changed. However, we are doing integration with an external system, simple fields, lastname, firstname, etc., and if we get a hit on firstname, we’ll get a second hit on lastname, etc. We need to know when a set of properities is changed on a contact object.
Hi, @gmphap1 
Thanks for the interesting question. You touch on a known limitation with how the propertiesWithHistory param can and cannot be used. There is not a method to change its behaviour.
Hey, @louischausse @ankitparmar09 @weiliang_lee do you have any workarounds or suggestions for @gmphap1?
Best,
Jaycee
Hi @gmphap1 ,
If you set up the workflow triggering the webhook this way, you shouldn’t get hit twice if fname and lname are updated at the same time because the contact would enroll only once in the workflow.
If the second property is updated a few minutes/hours/days later then you will get 2 hits, but there is no way you can’t prevent that.
Don’t forget to mark my reply as a solution if you are satisfied. If not, do not hesitate to ask me anything!