Last night we deployed a fix for a bug that was reported in the advanced filtering feature of the LOCATE API. When submitting an ISO 8601 value with a timezone offset for a filter LOCATE was ignoring the timezone offset causing the base date/time to be interpretted in UTC without the offset. For example:
filter=issue_date >= “2020-12-04T00:00:00-08:00”
Was being interpreted as:
filter=issue_date >= “2020-12-04T00:00:00”
Timezone offsets are now properly accounted for should you choose to submit them. All dates/times submitted are presumed to be in UTC or a representation relative to UTC so keep that in mind when translating what a user requests to the LOCATE API.