UTC Date is in EST #2
Description
Hello,
We are in the midst of writing a processor to update custom_fields on specific calls. Because it is possible to have multiple calls from the same caller_number within a strict time period to an end point. We are searching for the specific call using filters using the times that are returned from the search activities API.
It appears your UTC dates for a specific "activity" are in EST under the call_path attribute when you fetch activities/ calls yet the time stamp ISO strings have the Z at the end for Zero time. By comparison the billed_at attribute has a correct UTC time stamp but does not designate the Z at the end of the ISO string.
Is this a known issue? Can we expect that this will be resolved?