Dates and times

How to work with dates and times in the ComplyAdvantage Mesh API

Wherever there is a user provided date and time in an API request, it needs to follow the ISO 8601 format and must include the timezone.

Guide to ISO 8601 format

Date and times should be in the format YYYY-MM-DDThh:mm:ss[.f]TZD, where:

  • YYYY = four-digit year
  • MM = two-digit month (eg 03=March)
  • DD = two-digit day of the month (01 through 31)
  • T = a set character indicating the start of the time element
  • hh = two digits of an hour (00 through 23)
  • mm = two digits of a minute (00 through 59)
  • ss = two digits of a second (00 through 59)
  • f = fractional part of a second
  • TZD = time zone designator (Z or +hh:mm or -hh:mm), the + or - values indicate how far ahead or behind a time zone is from UTC

The following parts of the date and time are mandatory when provided in a request:

  • YYYY
  • MM
  • DD
  • T
  • hh
  • mm
  • ss
  • TZD - either Z for UTC or +hh:mm or -hh:mm for UTC offset.

Timezone examples

  • 2024-01-11T09:49:49.718369Z indicates that the timezone is UTC as Z is used as the time zone designator.
  • 2024-01-11T09:49:49.718369-4:00 indicates that the timezone is behind UTC by 4 hours.

Responses

All responses returned by the API will be in UTC, and will be indicated as such using the above UTC format (i.e. 2024-01-11T09:49:49.718369Z).