Request for Modification: Why does Service Now REST API not support ISO 8601 time stamps by default

esguaravkumar
Tera Contributor

‎04-16-2025 04:53 PM

Sample time stamps in REST API

"2025-04-13 13:15:00"

This is:

  • Not ISO 8601 because:

    • It uses a space instead of a T between date and time.

    • It does not include the timezone offset (Z for UTC or +/-HH:MM)

The standard has been more or less final since 2019.

Instead of requiring each developer to create a scripted web service or do a client side transformation, it would be more elegant for Service Now to fix this at the source.


We are aware on how to convert to and from, the commentary is that it should be available by default.

Already we have to use the &sysparm_display_value=all to get both UTC and User Time Zone timestamps which doubles the bytes over the wire.   Lot of devs may be relying on the display value,  and possibly the Service Now own UI relies on it, but Service Now could use the value field in the API response as a starting point to start migrating to industry best practices.

 



0 Helpfuls
  • 330 Views
1 REPLY 1

Robert H
Mega Sage

‎04-16-2025 10:47 PM

Hello @esguaravkumar ,

 

The Idea Portal (support.servicenow.com/ideas) is where ServiceNow users can view, vote on, and submit ServiceNow product enhancement requests as Ideas. 

 

Regards,

Robert

0 Helpfuls