REST API - TakeProfit

Historical market data and the security catalog over plain HTTP. Every endpoint answers GET only, returns JSON, and takes the API key in the x-api-key header.

curl -G "https://public-api.takeprofit.com/api/v1/marketdata/candles" \
  -H "x-api-key: $TAKEPROFIT_API_KEY" \
  --data-urlencode "exchange=CXBNCE" \
  --data-urlencode "symbol=BTC/USDT" \
  --data-urlencode "timeframe=1h" \
  --data-urlencode "from=2026-09-01T00:00:00Z" \
  --data-urlencode "limit=100"

Base URL: https://public-api.takeprofit.com/api/v1/marketdata. Live data is a separate protocol — see the WebSocket API.

Endpoints

Group	Endpoint	Returns
Candles	`GET /candles`	Historical candles for one security and timeframe.
	`GET /timeframes`	Every supported timeframe id, with the count rules that build them.
Footprint	`GET /footprint`	Volume footprint profiles: buy and sell volume and trade counts per price row.
	`GET /footprint/row-size-scale`	The row size step and bounds a settings UI can offer for a security and timeframe.
TPO	`GET /tpo`	TPO (Market Profile) profiles with point of control, initial balance and time blocks.
Securities	`GET /search`	Ranked search over securities by text or exact ISIN.
	`GET /exchanges`	Exchanges that have publicly served securities.
	`GET /exchanges/{exchange}/securities`	Securities listed on one exchange.
	`GET /exchanges/{exchange}/securities/{symbol}`	One security specification: type, assets, tick size, precision.

Each endpoint page in the sidebar lists its parameters and response fields and has a Try it playground.

Only exchange, symbol and timeframe are required. Leave the range out and the endpoint answers with the most recent data it has — the last 1000 candles, or the profiles that fit the default window. Add from, to, period or limit to narrow it down.Exchange codes come from GET /exchanges. They are TakeProfit codes, not the MIC of the listing venue: US equities are served under BATS, so AAPL lives at exchange=BATS. An unknown code answers 404 exchange not found, a symbol that is not listed there 404 security not found.

Parameter	Applies to	Notes
`exchange`, `symbol`	all data endpoints	Required. Take the pair from the Securities endpoints; ISINs work in search only.
`timeframe`	candles, footprint, TPO	Required. Ids come from `GET /timeframes`. Footprint takes minute to month frames, TPO only day, week and month frames.
`from`	candles, footprint, TPO	Optional. Unix seconds or an RFC3339 timestamp. Left out, the window is measured backwards from `to`.
`to`	candles, footprint, TPO	Optional, and greater than `from`. Defaults to now when `from` is omitted.
`period`	candles, footprint, TPO	Optional duration in seconds (`86400`, not `1d`), counted forward from `from` or backwards from `to`. Not available on tick timeframes.
`limit`	candles	Optional candle count, counted from whichever end of the range you pinned. Defaults to 1000, and is the only range control tick timeframes accept.
`sessionType`	candles, footprint, TPO	Optional filter: `MAINSESSION`, `PRE_MARKET`, `POST_MARKET`. Repeat the parameter or pass comma-separated values.
`rowSize`, `rowSizeValue`	footprint	Price row height in ticks, or an absolute value echoed back from a previous response to pin the same price grid.
`blockSize`, `mergeSessions`	TPO	Time block duration as a timeframe id (default `30m`, not seconds) and whether sessions merge into one profile per period.

Combine what you need: from alone reads forward from that point, to alone reads backwards from it, from with to pins both ends, and period sets the length from whichever end you gave. Unknown query parameters are still rejected with 400, so a typo fails loudly instead of being silently ignored — passing limit to footprint or TPO is one of those typos, since only candles take it. Every authenticated response carries the quota headers x-ratelimit-limit, x-ratelimit-remaining and x-ratelimit-reset (the reset is a Unix timestamp). They count credits, not requests: your account gets 100,000 credits per 60 seconds, and every request costs at least 1,000. Prices, caps and what to do on 429 are in Credits and limits. Every response, errors included, also carries an x-request-id worth quoting in a support request.

Reading the responses

Prices and volumes are decimal strings. Nothing is rounded into a float on the way to you.
Profile rows are positional arrays. A footprint row is [price, volumeBuy, volumeSell, tradesCountBuy, tradesCountSell], a TPO row is [price, blockIndexes, volumeBuy, volumeSell]. Future fields are appended, so ignore extra trailing elements.
price is the lower bound of the half-open interval [price, price + rowSize).
Footprint history depth is limited per timeframe, counted back from the security’s newest candle: 30 days for minute frames below 5m, rising with the timeframe to 3 years for 1w and above. A from older than the limit is trimmed rather than rejected, so the response can start later than you asked, and a range that ends before the limit comes back empty. TPO has no such limit, only a cap of 400 profiles per request. Both start on 29 May 2026 at the earliest, when collection began, with no plans to backfill earlier periods; the depth of every timeframe is listed in History depth.

Errors

Every failure returns an HTTP status and a JSON body, {"error": {"code": "...", "message": "..."}}. Branch on code: it is stable, while message is for people.

Status	Code	Meaning
`400`	`invalid_argument`	A malformed or unknown query parameter, such as a candle `limit` above `10000`
`400`	`too_much_data`	The range is over the per-request cap of 10,000 candles, 1,000 footprint profiles or 400 TPO profiles; narrow the window or use a longer timeframe
`401`	`unauthenticated`	The API key is missing or invalid
`403`	`permission_denied`	The key lacks the `MARKETDATA:ALL:READ` scope. Keys created in Settings always have it
`404`	`not_found`	The exchange, the security or the data is not served
`429`	`rate_limited`	Not enough credits left in the window; retry after `Retry-After` seconds
`502`, `503`, `504`	`bad_gateway`, `unavailable`, `deadline_exceeded`	A temporary upstream problem; retry with exponential backoff

Requests rejected with 400, 404 or 429 are not billed. New here? Quickstart walks through the first three requests, and Authentication covers creating a key.

​Endpoints

​Parameters the history endpoints share

​Reading the responses

​Errors

Endpoints

Parameters the history endpoints share

Reading the responses

Errors