REST v2 - List Orders - Date Time Zone

API Q&A
1

@OmarAlmonte - Could you do me a favour and verify something for me please.

I am trying out the List Orders Endpoint for REST v2, and have the following filter set:

created_since_time==2026-04-21T00:00:00.000Z;created_until_time==2026-04-21T23:59:59.000Z

When I get the results back on the Creation Time I check if it matches the Order Date in the application.

2026-04-21 21:42:05 - Correct, shows the “2026-04-21”.
2026-04-21 22:19:27 - Correct, shows the “2026-04-21”.
2026-04-21 23:06:17 - Incorrect, shows the date “2026-04-22”.
2026-04-21 23:04:34 - Incorrect, shows the date “2026-04-22”.

It seems to me that there is a 1 Hour offset from the date range.

in the XMl-RPC API, the Dates are in the United States - EST Time Zone.

Does the Date and Time get adjusted if the application is in a different Time Zone? Or is it always in EST time?

2

Hi @Pav,

I wasn’t able to reproduce the behavior on my end with the same filter and date range. That said, I’ve raised this internally so we can take a closer look at the code and verify whether there might be a bug in the current logic.

As a general rule in REST v2, date/time fields are expected to be returned in UTC using ISO 8601 format. However, this particular endpoint has a different implementation and is returning dates in EST.

We’ll review this in more detail and follow up once we have more information.

3

Just want to make it clearer for your team.

Here is an example of the Creation Date returned: 2026-04-21 23:06:17

This is what XML-RPC “Job” table is returning: 2026-04-21 19:06:17

This is what the application is showing for the Order Date “2026-04-22”.

image
image920×368 20.6 KB

The application Time Zone is set to the UK. As it is now British Summer Time, it is +1 hour from the UTC time.

There is a 4 hour difference between the 2 dates returned via the API.

The time difference between the UK and EST is 5 Hours,

Hope that helps.

4

Thank you! I’ll get back to you as soon as we have more info.