QTSurfer API (0.95.1)

Exchanges a long-lived API key for a short-lived JWT used by every other endpoint. This is the only endpoint that accepts an API key directly — callers should obtain a JWT here, then send it as Authorization: Bearer <token> to all other operations.

The returned JWT carries the caller's subscription tier as a claim and expires after expires_in seconds. Callers should refresh the token before expiry (or on a 401 response) by calling this endpoint again.

Serves exactly one hour of raw ticker data for the given instrument on the requested exchange. The payload is a native Lastra file — QTSurfer's columnar format for tick-precision timeseries — with no JSON envelope.

One segment = one hour, aligned to UTC. The hour query parameter selects the segment and must match YYYY-MM-DDTHH (no minutes/seconds, no timezone suffix). Example: hour=2026-01-15T10 returns h10.lastra for 2026-01-15, covering [10:00:00Z, 11:00:00Z). Hours not yet available return 404.

A format=parquet query parameter switches the response to on-the-fly Parquet conversion via lastra-convert for clients that don't yet read Lastra. Lastra is the primary format and cheaper when the client can consume it.

Clients:

• lastra-java — reference Java reader/writer with per-column codecs (ALP, Gorilla, delta-varint, ZSTD) and CRC32 integrity.
• lastra-ts — TypeScript reader (~4 kB bundle, browser + Node.js).
• duckdb-lastra — DuckDB extension for ad-hoc SQL over Lastra files.
• lastra-convert — CLI + Java API for converting to/from Parquet, Reef, and CSV.
• curl -OJ for offline dumps (the Content-Disposition header sets a descriptive filename).

Same shape and semantics as /exchange/{exchangeId}/tickers/{base}/{quote}, but serves klines (aggregated bars) instead of raw ticks. One Lastra segment = one hour of klines at the exchange's native kline cadence, aligned to UTC.

Klines use the same columnar layout as tickers — readers that handle one format read the other with the same code. Use this endpoint when a per-tick payload would be too large for the window of interest.

Enqueues a prepare task over the requested date range. Returns immediately with a jobId; poll GET /backtest/{exchangeId}/{type}/prepare/{jobId} for completion.

The same params always return the same jobId (idempotent). Repeated calls with identical params do not enqueue duplicate work — they reuse the existing job.

Retrieves the current state of the prepare job identified by jobId. Poll until status is Completed, Failed, or Aborted.

Enqueues an execute task that runs the strategy identified by strategyId over the data prepared by the prepare job identified by prepareJobId. The instrument and date range are recovered from the prepare job — they do not need to be sent again.

Returns immediately with a jobId; poll GET /backtest/{exchangeId}/{type}/execute/{jobId} for the result.

The same params (same prepareJobId, strategyId, storeSignals) always return the same jobId (idempotent).

Requests cancellation of the specified execution. The execution status will transition to Aborted once the cancellation is processed. Cancellation is asynchronous — poll the GET endpoint to confirm the final status.

Retrieves the current state and results of the execute job identified by jobId. Poll until state.status is Completed, Failed, or Aborted.

Submits raw strategy source for compilation. By default the call is synchronous and returns the strategyId once compilation succeeds. Set the header X-Compile-Async: true to enqueue the compile task and return immediately with a jobId — poll GET /strategy/{strategyId} to check status.

The strategyId is deterministic: the same source for the same user always produces the same id.

Polls the status of a strategy compilation. Useful when the strategy was submitted with X-Compile-Async: true. Returns the resolved strategyId once compilation completes.