# Date/Time Format

Date/time values are found both as inputs and outputs in multiple places in the API.

## Output

We use [ISO 8601 format](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) including milliseconds for all output values. Here's an example showing standard date/time output formatting:

{% code lineNumbers="true" %}

```json
{
  "query": {
    "name": "body-position",
    "start-date": "2023-06-25T17:04:02.000Z",
    "end-date": "2023-06-25T17:04:03.000Z",
    //...
  }
}
```

{% endcode %}

## Input

When a date/time is required as an input to an API endpoint, you may use a variety of formats.

`[DATE_TIME]` must be a string value representing a date, parsed and interpreted using the same algorithm implemented by Javascript's [`Date.parse()`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/parse)

Examples include:

ISO 8601, no milliseconds:

{% code overflow="wrap" %}

```
GET https://api.radiantdrift.com/body-position/2023-06-25T17:04:02Z/[...]
```

{% endcode %}

ISO 8601, with milliseconds:

{% code overflow="wrap" %}

```
GET https://api.radiantdrift.com/body-position/2023-06-25T17:04:02.555Z/[...]
```

{% endcode %}

Date string:

{% code overflow="wrap" %}

```
GET https://api.radiantdrift.com/body-position/01%20Jan%201970%2000:00:00%20GMT/[...]
```

{% endcode %}

See [date time string format](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date#date_time_string_format) for caveats on using different formats.