It looks like the timestamp 1569384000 isn't in UNIX miliseconds and I can confirm this by converting the timestamp here: https://currentmillis.com/ and the timestamp was converted to 19 Jan 1970 (Which is likely why you ain't getting back the ticket that you've added the note)
In this case, you just have to add three zeros behind this timestamp 1569384000 so that it's in miliseconds like this: 1569384000000 and using this timestamp in the endpoint.
On my end, when testing this out, I was able to see the ticket title test being return.
The reason why you're seeing multiple changes is because there's a list of changes for the ticket object id 43089088 at different time. You can understand what changes has been make by looking into the changedProperties (This will show the internal value of the contact property. For example, when looking at num_notes that's the internal value for the Number of sales activities property). Learn more about properties and internal value here: Edit properties.
Currently, the Get all tickets API doesn't support filtering. That said, you can loop through all tickets and page backward using the hasMore and offset properties. As mentioned by Connor here: Get all Tickets api with filter.
Sep 30, 20199:21 AM - edited Sep 30, 20199:22 AM
Member
Get all updated tickets
It's impossible to go over all tickets every time we need to get an information... This is not the right track to do.. can you imagine if you have millions of tickets? The correct way should be filtering by date. I hope you guys consider and improve that API.
Sep 26, 201911:54 AM - edited Sep 26, 201912:07 PM
Member
Get all updated tickets
Hi Wendy tk u for replying to me.
I just added a note to my ticket test to see the API returns and it's return 3 positions... I'm assuming it should be only one once it's only one note...
Could you please clarify why it's returning the result below?