Skip to main content
GET
Signals History
The historical counterpart to Signals. Returns cluster signals that would have fired on past days, so you can backtest a strategy. Each entry marks the token, how many wallets clustered, how much they invested, and when the signal triggered. Use it to answer questions like how often did a three KOL cluster precede a move, or to replay signals for a given day.
Look back with days. Each signal carries would_have_fired and the day it belongs to, along with triggered_at, so you can line signals up against price history from your own source.

Query Parameters

string
required
Chain. One of solana, bnb, base, eth, rh (Robinhood Chain).
string
required
Wallet category kol, smart or whale.
integer
How many past days to include.
integer
default:"3"
Minimum wallets that must have clustered for a historical signal.
integer
Maximum number of signals to return.
string
Your API key, required on https://api.cabalspy.xyz. Alternatively pass it as an Authorization Bearer header. Not needed on the demo server https://demo-api.cabalspy.xyz.
Try it without an API key: Try it runs on the demo server https://demo-api.cabalspy.xyz (20 requests per IP per day, data delayed 15 minutes, at most 5 rows), so you can send a request without a key. For live data, switch the server to https://api.cabalspy.xyz and enter your API key. Your own integration always calls api.cabalspy.xyz with your API key, as in the usage examples below. Get a free key · About the demo

Usage Example

Response

boolean
True on success.
object

Errors