Skip to main content

Date n time

Date and time in Hii Retail integrations

Date and time is always problematic between systems. For ease of integrating we have adopted the ISO standard for how to deal with dates and time formats.

Basically it means that in any input API where a date and/or time is expected, we require that you specify the time as a fully qualified time and/or date and time according to the ISO 8601 standard.

And just to be explicit:

  • Date and time format: YYYY-MM-DDThh:mm:ss.sTZD
  • Time format: hh:mm:ss.sTZD

Where:

  • YYYY = four-digit year
  • MM = two-digit month (01=January, etc.)
  • DD = two-digit day of month (01 through 31)
  • hh = two digits of hour (00 through 23) (am/pm NOT allowed)
  • mm = two digits of minute (00 through 59)
  • ss = two digits of second (00 through 59)
  • s = one or more digits representing a decimal fraction of a second
  • TZD = time zone designator (Z or +hh:mm or -hh:mm)

Date and time examples:​

  • 2023-04-15T00:00:00Z - April 15th at 00:00:00 Coordinated Universal Time (UTC)
  • 2023-04-15T00:00:00+01:00 - April 15th at 00:00:00 for London on British Summer Time
  • 2023-04-15T00:00:00-10 - April 15th at 00:00:00 for Honolulu

Time examples:​

  • 00:00:00Z - April 15th at 00:00:00 Coordinated Universal Time (UTC)
  • 00:00:00+01:00 - April 15th at 00:00:00 for London on British Summer Time
  • 00:00:00-10 - April 15th at 00:00:00 for Honolulu
  • T00:00:00-10 - April 15th at 00:00:00 for Honolulu including the literal T to specifically state that it is a time part