I think you'll notice the difference when you go to create some engagements. Take a look here for example: https://developers.hubspot.com/docs/methods/engagements/create_engagement. There's some sample JSON in the right sidebar, which includes a timestamp. And there's also a description of the timestamp field on that page:
Optional timestamp, should be used for logical ordering (e.g. when a call occurred, vs when it was last modified)
So if you create a note engagement for example using the sample JSON on that page, you'll get the engagement's JSON back in the response. You'll notice that the createdAt field is the time when the enagement itself was created. The timestamp field corresponds to when the engagement occurred.
I think you'll notice the difference when you go to create some engagements. Take a look here for example: https://developers.hubspot.com/docs/methods/engagements/create_engagement. There's some sample JSON in the right sidebar, which includes a timestamp. And there's also a description of the timestamp field on that page:
Optional timestamp, should be used for logical ordering (e.g. when a call occurred, vs when it was last modified)
So if you create a note engagement for example using the sample JSON on that page, you'll get the engagement's JSON back in the response. You'll notice that the createdAt field is the time when the enagement itself was created. The timestamp field corresponds to when the engagement occurred.