Date/Time Format

All date and time values in the Scan2Evolve API follow a consistent format.

ISO 8601 Format

Date and Time Format

All date/time values in requests and responses are in Coordinated Universal Time (UTC), following the ISO 8601 date and time format. For example: 2024-11-18T10:30:00Zor 2024-11-18T10:30:00.000Z for milliseconds precision.

Format Specification

Date format: YYYY-MM-DD (e.g., 2024-11-18)
DateTime format: YYYY-MM-DDTHH:mm:ssZ (e.g., 2024-11-18T10:30:00Z)
With milliseconds: YYYY-MM-DDTHH:mm:ss.sssZ (e.g., 2024-11-18T10:30:00.000Z)
Timezone: Always UTC (indicated by the Z suffix)

Examples

Date Only

{
  "hireDate": "2024-11-18",
  "terminationDate": "2024-12-31"
}

DateTime with Seconds

{
  "recordedAt": "2024-11-18T10:30:00Z",
  "installedAt": "2024-11-18T14:45:30Z"
}

DateTime with Milliseconds

{
  "recordedAt": "2024-11-18T10:30:00.000Z",
  "modifiedAt": "2024-11-18T14:45:30.123Z"
}

Timezones

All timestamps in the API are in UTC. When sending requests, convert your local time to UTC. When receiving responses, convert UTC to your local timezone for display.

Important: Always use UTC for API requests. Do not include timezone offsets (e.g., +05:30 or -08:00). Use the Z suffix to indicate UTC.

Updated 1 day ago

Acceptable use policy