The copper api uses Unix Epoch times (seconds snice 1970).
Weird, but ok. It really should use rfc 3339 (iso 8601). But, since it doesn’t, it leads to this problem…
it uses unix epoch with respect to some timezone. And this is making integration complex. If its going to be in epoch, it really needs to be in UTC..
How can i know what timezone it is with respect to now? there is no api call to figure that out. and, which sub-timezone. etc.
Is this global to the copper world? to a specific customer?to an object or lead?
so for example, when i ceate activity events, they end up in the future since i want to supply UTC. but if i can’t, then i need to know the DST/STD settings as well as the utc offset of the copper server.