The Lucca API normalizes the formating of some data types.
Z
character in the time-offset
part of the string is equivalent to a +00:00
timezone offset. In other words, in indicates the date-time is UTC.Type | Description | ABNF | Example |
---|---|---|---|
Date | Date of a day. | full-date | 2023-01-01 |
Date-Time (Local) | Timezoned date and time. | full-time | 2023-01-01T09:45:23.0001Z :br 2023-01-01T07:45:23.0001+02:00 |
Date-Time (Floating) | Date-time value that isn’t tied to a specific time zone. It’s occurs at the same displayed local time, wherever you are. | ||
Time (Local) | Timezoned time value. | full-time | 07:30Z |
Time (Floating) | Time value that isn’t tied to a specific time zone (e.g: the time of your alarm clock). | partial-time | 07:30 |
(date-time) createdAt
, (date) occursOn
, etc…2023-01-01--2023-01-31
represents the interval between two dates, outside of any timezone. Here, both the start and end date are included.2023-01-01T00:00:00--2023-01-02T00:00:00
represents the interval between two points in the time scale, oustide of any timezone. Here, the end date is NOT included.2023-01-01T00:00:00+02:00--2023-01-02T00:00:00+02:00
represents the interval between two points in the time scale, defined in reference to UTC. Here, the end date is NOT included.?date=2023-01-01/2023-01-31
, so the Lucca API does not officially support it. Besides, the Lucca API does not support ranges defined as a date and a duration either.".."
characters:
..--2023-01-01
: until Jan. 1st 2023 ;2023-01-01--..
: since Jan. 1st 2023.P2DT12H30M23S
indicates “2 days, 12 hours, 30 minutes and 23 seconds”.
value
property, followed by the unit
. But if calculations are needed, it is recommended to parse the iso
property, as the value
can be subject to rounding (e.g. “1h20” gives a decimal value of “1.3333…”).