That API debugging messed up because of the timestamp parameter
When we interface with third-party APIs, one of the most common and error-prone parameters is time. Especially when debugging log query, data synchronization and other interfaces, I wasted a lot of time on the Unix timestamp conversion problem. Real scenario: "Time trap" in API debugging Last week, we were debugging a user data synchronization interface. The document clearly requires that the Unix timestamp (second level) be passed in. It seems simple, but various problems are encountered in actual operation: - Time unit confusion: some interfaces use second level timestamps, and some use millisecond level, and the wrong time is accidentally transmitted - Time zone...