Some of the fields in our environment are presenting incongruent values when comparing HubSpot UI and HubSpot API. The wrong values are timestamp values and I’m already considering timezone differences, but the values don’t add up
CURL:
curl --location https://api.hubapi.com/crm/v3/objects/tickets/TICKET\_ID?properties=HS\_DATE\_ENTERED\_112135850%2CHS\_DATE\_ENTERED\_112135851%2CHS\_DATE\_ENTERED\_112135852%2CHS\_DATE\_ENTERED\_112135853%2CHS\_DATE\_ENTERED\_112149878
Result:
{‘id’: ‘TICKET_ID’,
‘properties’: {‘createdate’: ‘2024-04-01T14:31:04.361Z’,
‘hs_date_entered_112135850’: ‘2024-04-01T14:31:04.361Z’,
‘hs_date_entered_112135851’: ‘2024-04-01T21:12:41.709Z’,
‘hs_date_entered_112135852’: ‘2024-04-05T11:25:02.547Z’,
‘hs_date_entered_112135853’: ‘2024-04-08T15:02:04.355Z’,
‘hs_date_entered_112149878’: ‘2024-04-08T15:02:04.355Z’,
‘hs_date_entered_112149879’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_entered_112149880’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_entered_112149881’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_entered_112149882’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_entered_112149883’: ‘2024-04-08T15:09:27.766Z’,
‘hs_date_entered_112149884’: ‘2024-04-08T15:09:27.766Z’,
‘hs_date_exited_112135850’: ‘2024-04-01T21:12:41.709Z’,
‘hs_date_exited_112135851’: ‘2024-04-05T11:25:02.547Z’,
‘hs_date_exited_112135852’: ‘2024-04-08T15:02:04.355Z’,
‘hs_date_exited_112135853’: ‘2024-04-08T15:02:04.355Z’,
‘hs_date_exited_112149878’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_exited_112149879’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_exited_112149880’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_exited_112149881’: ‘2024-04-08T15:08:46.001Z’,
‘hs_date_exited_112149882’: ‘2024-04-08T15:09:27.766Z’,
‘hs_date_exited_112149883’: ‘2024-04-08T15:09:27.766Z’,
‘hs_lastmodifieddate’: ‘2024-04-08T15:10:44.249Z’,
‘hs_object_id’: ‘2554640770’,
‘hs_time_in_112135850’: ‘24097348’,
‘hs_time_in_112135851’: ‘310340838’,
‘hs_time_in_112135852’: ‘272221808’,
‘hs_time_in_112135853’: ‘0’,
‘hs_time_in_112149878’: ‘401646’,
‘hs_time_in_112149879’: ‘0’,
‘hs_time_in_112149880’: ‘0’,
‘hs_time_in_112149881’: ‘0’,
‘hs_time_in_112149882’: ‘41765’,
‘hs_time_in_112149883’: ‘0’,
‘hs_time_in_112149884’: ‘1377206362’},
‘createdAt’: ‘2024-04-01T14:31:04.361Z’,
‘updatedAt’: ‘2024-04-08T15:10:44.249Z’,
‘archived’: False}
HubSpot UI:
Hi @PSanches,
Thank you for reaching out to the Community!
Just to make sure that I understand what’s happening here, I’d like to ask some clarifying questions:
1. Could you please give me the name of the property in the UI (only 1 example)? I see several properties in the screenshots so let’s focus on one to check.
2. What is the value in the UI for this property?
3. What is the value for this same property with the API call?
4. What is the record ID of the ticket?
5. When you look at the property history, maybe the value has been updated a minute or a second after?
6. Did you check that the API call was indeed for this same Record ID ticket?
I’d like to invite a couple of subject matter experts to this conversation: Hi @Teun, @zach_threadint and @ChrisoKlepke did you notice similar behavior on your end? Do you have suggestions to help @PSanches, please?
Also, if anybody else has anything to add and/or share, please feel free to join in the conversation ![]()
Thanks a lot and have a lovely day!
Best,
Bérangère
Hi @BérangèreL !
1. The property is “ticket status”;
2. The problem is the timestamps from when the status was changed in some of the values don’t match between UI and API. I will take as an example the change into the value “03 Início: Extração dos arquivos (Faturamento)” which has pipeline stage ID=112135852. The timestamp that the ticket entered this stage in UI is 04/08/2024 at 11:59 AM GMT-3 (MM/DD/YYYY);
3- The timestamp that the ticket entered this stage in API is 2024-04-05T11:25:02.547Z;
4- Ticket ID is 2554640770
5 - The value is three days after the change, so it was not a latency issue
6 - The curl was this one: curl --location ‘https://api.hubapi.com/crm/v3/objects/tickets/2554640770?properties=HS_DATE_ENTERED_112135850%2CHS_DATE_ENTERED_112135851%2CHS_DATE_ENTERED_112135852%2CHS_DATE_ENTERED_112135853%2CHS_DATE_ENTERED_112149878’






