I wouldn’t advise using the offset in any case, because any library capable of accurately knowing the offset also knows how to use Z/UTC.
Yeah- that makes sense! Thank you, Sandy! Using the Z (UTC timezone) certainly does help to stick with a standard timezone and thus avoid any confusion. 😊
If anyone is trying to update users, not leads the format for /management/v1/users/{userid}/update.json is
yyyyMMdd'T'HH:mm:ss.SSS't'Z
Example: 20241118T14:29:56.222t+0000
Note that the time-zone does not contain the colon and Z is not accepted (which is really weird).
That's really bizarre but you're right, for buggy reasons it doesn't accept the everyday ISO 8601 yyyy-MM-dd'T'HH:mm:ss'Z'
. We were too confident that this endpoint works like all the others!