The Issue
According to Intercom’s documentation, the android_last_seen_at field should be a UNIX timestamp (seconds since epoch). However, It has been discovered that in some responses, Intercom actually returns this field as an ISO format string instead.
This inconsistency can cause parsing errors or unexpected behavior if your code expects only one format.
Solution
Recommend creating a flexible parser that can handle both formats:
This has only confirmed with the android_last_seen_at field, but it might be prudent to apply this approach to all timestamp fields from Intercom’s API.