api.radiantdrift.com
  • Radiant Drift API
    • Subscription Plans
    • Educational Use and Research
    • API End Points
  • Getting Started
    • About your account
    • Request Authentication
    • Managing API Keys
    • OpenAPI Specification
    • Date/Time Format
    • Validity, Accuracy, and Precision
  • Usage Guidelines
    • Acceptable Use Policy
    • Usage Credits and Call Costs
    • Attribution
    • Rate Limits
  • Julian Day
  • Delta-T
  • Rise, Transit, Set Times
  • Body Position
    • Request Parameters
    • Position at a given time
    • Positions for a time range
    • Observer location
  • Solar Eclipses
    • Embeddable Web Widgets
      • Eclipse Map
      • Eclipse Simulator
    • Besselian Elements
    • Local Circumstances
    • Eclipse Paths
    • Five Millennium Canon of Solar Eclipses
  • The Moon
    • Lunar Libration
    • Lunar Limb Profile
  • Geospatial
    • Geodesic
    • Elevation
  • Reference
    • Definitions
    • Errors
Powered by GitBook
On this page
  • Output
  • Input
  1. Getting Started

Date/Time Format

PreviousOpenAPI SpecificationNextValidity, Accuracy, and Precision

Last updated 1 year ago

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

Output

We use including milliseconds for all output values. Here's an example showing standard date/time output formatting:

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

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

Examples include:

ISO 8601, no milliseconds:

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

ISO 8601, with milliseconds:

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

Date string:

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

See for caveats on using different formats.

ISO 8601 format
Date.parse()
date time string format