← All APIs

Crypto Signal Track Record API

The price 1 minute to 24 hours after every published market signal, with hit rates and median moves by type, venue, size and hour.

  • 18 sources
  • spot and perpetual futures
  • free plan

What's inside

  • Six horizons from 1 minute to 24 hours
  • Share in the signal's direction, median and quartiles
  • Breakdown by venue, size, hour of day and coin

Endpoints

GET/stats/by-typeOutcomes by signal typeBASIC
GET/statusPlan and data freshnessBASIC
GET/stats/breakdownOutcomes by venue, size, hour or coinPRO
GET/events/scoredIndividual signals with measured outcomesPRO

On the right: the plan that opens each endpoint.

Example

curl --request GET \
  --url 'https://hookscreener.com/v1/p/track-record/stats/by-type' \
  --header 'X-API-Key: YOUR_KEY'

Questions

How is an outcome measured?
From the first trade after the signal to the price at each horizon on the same venue. A horizon whose price is not yet known is null, never carried forward.
What does "in the signal's direction" mean?
A buy-side wall or a buying robot counts as up, the mirror as down; a liquidity sweep counts as a fade, so an upward spike counts as down.
How fresh is the data on each plan?
BASIC: updated nightly; PRO: updated nightly; ULTRA: updated nightly; MEGA: updated nightly.
What period do the statistics cover?
The last 30 days on every plan; MEGA can also ask for the full archive. Scored events reach back 7 days on PRO and 30 days on ULTRA and MEGA; one request covers at most 24 hours and 200 rows.

18 exchange sources: spot and perpetual futures. Derived events and aggregates only: no raw order books, no trade tape, no detection rules. History is a rolling window up to 30 days back. The licence covers use inside your own application, bot, dashboard or research. Redistributing the data as a feed, an API or a dataset, or re-hosting it as an MCP server, is not allowed. Informational purposes only. Not financial advice.