Issues with API V2

No Way of Resetting Values

Currently, there is no method available to reset a value to a state where it is not set. This poses a problem when attempting to reset a value to its default setting. Attempts to set the first_name or custom_attributes to an empty string "" or null are not accepted by the API. However, the internal API used by the frontend allows this action. It would be beneficial for the public API to support this functionality as well.

Updated_at Timestamp Not Reflecting Changes

When updating a person, the updated_at timestamp does not reflect changes made to custom_attributes and potentially other fields. This creates a challenge when trying to determine the last time a person's information was updated.

Timezone Discrepancies

The documentation specifies that created_at and updated_at timestamps should be in UTC. However, the timestamps received are in the local timezone, currently UTC+1. For example, a timestamp like "2025-02-27T17:02:55.310355Z" appears to be in the local timezone rather than UTC. This discrepancy causes issues when comparing timestamps with those from other sources.

Please consider addressing these issues to improve the functionality and reliability of the API.