market session breakout by rejection
tracks which side of the first session range forms first, then waits until session 1 closes before checking whether session 2 breaks the session 1 high or low first. configurable via start_date, end_date, and session windows.
Authorizations
Use your Edgeful API key as the bearer token. In the API Reference authorization drawer, paste only the key (for example, ef_live_<random>).
Path Parameters
ticker symbol. format varies by market_type: stocks use a plain symbol (e.g., SPY), forex uses a 6-character pair (e.g., EURUSD), crypto uses a contract pair (e.g., BTCUSD), futures uses the root symbol (e.g., ES).
"SPY"
"EURUSD"
"BTCUSD"
"ES"
market venue for the ticker. one of: forex, futures, crypto, stock. determines supported symbols and whether session-based intraday aggregation is available.
forex, futures, crypto, stock "stock"
"forex"
Query Parameters
session 1 start time, HH:MM:SS, interpreted in session1_timezone. session 1 defines the reference range.
session 1 end time, HH:MM:SS, interpreted in session1_timezone. session 2 break measurement starts only after this time.
IANA timezone used to interpret session 1 times.
session 2 start time, HH:MM:SS, interpreted in session2_timezone. breakouts of session 1 high or low are measured within this session after session 1 closes.
session 2 end time, HH:MM:SS, interpreted in session2_timezone.
IANA timezone used to interpret session 2 times.
when true, treats session 1 and session 2 as falling on separate calendar days; when false, both sessions belong to the same calendar day.
filter on where price ended session 1, measured as a percent of the session 1 range from the rejection side; ALL keeps every session.
0, 1, 2, 3, 4 intraday candle granularity used for the calculation. accepted values: 1min, 5min, 15min, 30min, 1hour. route-specific defaults are shown in the default field.
inclusive start date, YYYY-MM-DD, interpreted in the request timezone. sessions on or after this date are included in the calculation.
"2024-01-01"
inclusive end date, YYYY-MM-DD, interpreted in the request timezone. sessions on or before this date are included in the calculation.
"2024-12-31"
Response
Successful Response