Clock API and Extended Hours

Will the clock endpoint be updated to show when extended hours trading is active?

1 Like

No, not at this point. What kind of format/values would you expect in the response?

Something like pre_is_open and after_is_open bools.

1 Like

bump

Any chance of adding this support. Polygon has a market status endpoint which indicates if the market is in extended hours but, it doesn’t support Alpaca API keys.

https://polygon.io/docs/#!/Reference/get_v1_marketstatus_now

Response Can be open , closed or extended-hours

I am also in need of this feature.
Current response is:
{ timestamp: β€˜2020-03-06T01:37:37.902630648-05:00’,
is_open: false,
next_open: β€˜2020-03-06T09:30:00-05:00’,
next_close: β€˜2020-03-06T16:00:00-05:00’ }
Proposed change:
{ timestamp: β€˜2020-03-06T01:37:37.902630648-05:00’,
is_open: false,
next_open: β€˜2020-03-06T09:30:00-05:00’,
next_close: β€˜2020-03-06T16:00:00-05:00’,
extended_hours_is_open: false,
extended_hours_next_open: β€˜2020-03-06T09:30:00-05:00’,
extended_hours_next_close: β€˜2020-03-06T16:00:00-05:00’ }

2 Likes

I second the need for such a feature. My current strategy will involve extended hours trading (exclusively). Because such an endpoint does not currently exist, I will need to β€œhard-code” in hours based on your current extended hours trade policies.

Further, I suggest the following response for the clock endpoint:
{ timestamp: β€˜2020-03-06T01:37:37.902630648-05:00’,
is_open: open | closed | extended }

Notice I am suggesting removing next_open & next_close, as those values are already in the calendar endpoint and as currently redundant.

Please add support for Extended Hours to the clock!