List timeframes

GET/timeframes

Returns the timeframes a run, or a definition run over history, can use.

Scope	Heavy call	Long poll	CLI
`scripts:read`	No	No	None

Guidance

The list is fixed: 1m, 5m, 15m, 30m, 1h, 2h, 4h, 1d and 1w. Read it once and cache it.
Any other value in timeframe on Create a run, List events or Run a definition over history gets 400 unsupported_timeframe. Upper case is lowered on runs, so 5M works there.
One run holds at most 50,000 bars, so a long window needs a larger timeframe: 90 days of 1m is about 130,000 bars and is refused, while 90 days of 5m is about 26,000.

200 with data, an array of strings. The list is not paginated.

Status	Code	Meaning
`200`	-	The supported timeframes
`401`	`unauthorized`	No key, or it is wrong, expired or revoked

Example request

curl https://api.chartnaut.com/v1/timeframes \
  -H "Authorization: Bearer cn_live_XXXX"

Example response

200 OK

{
  "data": ["1m", "5m", "15m", "30m", "1h", "2h", "4h", "1d", "1w"]
}

401 Unauthorized

{
  "error": {
    "code": "unauthorized",
    "message": "Invalid API token."
  }
}

From the CLI

The CLI has no command for this call; chartnaut run --help lists the same timeframes under --tf.