I wanted to bring to your attention an issue that we've recently encountered with the created_date field returned by your API, specifically for the /activities endpoint.
Previously, the created_date field did not contain a leading + sign, however, we have noticed a change in its format lately. According to your documentation, the created_date_from field is not supposed to contain a + sign, and it seems that there might have been recent changes in the API response format.
Here's an example of the value returned for the created_date field:
'created_date': '+56201-11-02T12:56:40.000Z'
As you can see, the presence of the + sign deviates from the expected format and is causing compatibility issues on our end.
I wanted to bring to your attention an issue that we've recently encountered with the created_date field returned by your API, specifically for the /activities endpoint.
Previously, the created_date field did not contain a leading + sign, however, we have noticed a change in its format lately. According to your documentation, the created_date_from field is not supposed to contain a + sign, and it seems that there might have been recent changes in the API response format.
Here's an example of the value returned for the created_date field: 'created_date': '+56201-11-02T12:56:40.000Z'
As you can see, the presence of the + sign deviates from the expected format and is causing compatibility issues on our end.