But rarely the date time received is in the format yyyy-MM-dd’T’HH:mm:ss’Z’. (for instance : meeting end time & start time in above given snap)
Not only this can be seen in meeting start and end time, but this can be found in other datetime fields as well. But only when the seconds and the milliseconds are all zeros.
May I know why more than one date time format is used in the api’s and if there are any other formats other than the above mentioned ones, what are they ???
When working with HubSpot’s APIs, ensure timestamps for date properties use the ISO 8601 date format (YYYY-MM-DD) or a UNIX timestamp at midnight UTC, while datetime properties accept both ISO 8601 datetime format (YYYY-MM-DDThh:mm:ss.sTZD) and UNIX timestamps in milliseconds. This helps maintain consistency and accuracy in representing dates and times across the CRM. For detailed guidelines on formatting timestamps for HubSpot’s APIs, refer to the official documentation — How should I format timestamps for HubSpot’s APIs?
In the above post , I have used GET call(https://api.hubapi.com/crm/v3/objects/meetings) to fetch the list of meetings records . While using V3 API , I observed date time field values are in two different formats as I have mentioned in the above post .
May I know why more than one date time format is used in the api’s and if there are any other formats other than the above mentioned ones, what are they ???