Docs
Latest Signals

Latest Signals

Fetch the most recent signals with optional type and category filters. Reference for GET /signals/latest.

Overview

Returns the most recent signals from Engine A, with optional filters. Useful for polling or building a unified signal feed ordered by creation time.

Endpoint: GET /v1/signals/latest

Request

GET /v1/signals/latest?limit=20

Query Parameters

ParameterTypeDefaultDescription
typeStringnullSMART_MONEY_FLOW — omit for all
market_categoryStringALLELECTION / CRYPTO / SPORTS / MACRO / OTHER / ALL
limitInt20Maximum results (1–100)
cursorStringnullPagination cursor

Response

{
  "data": [
    {
      "signal_id": "...",
      "signal_type": "SMART_MONEY_FLOW",
      "timestamp": "2026-04-01T09:03:11Z",
      "signal_expiry": "2026-04-01T15:03:11Z",
      "market": { ... },
      "signal": { ... },
      "analysis": { ... }
    }
  ],
  "pagination": {
    "next_cursor": "2026-04-01T09:02:00Z",
    "has_more": true
  }
}

The signal and analysis objects match the Engine A signal shape:

  • SMART_MONEY_FLOW items include flow_type, direction, consensus_wallet_count, etc.

The market object is enriched in this endpoint and includes platform, market_id, question, category, volume_24h, and market_closes_at.

See Engine A for full field descriptions.

Use GET /v1/signals/market/{market_id} or GET /v1/signals/{signal_id} when you need a market-specific history or a specific stored signal.

Pagination

Pass next_cursor from the previous response as the cursor parameter to fetch the next page:

GET /v1/signals/latest?cursor=2026-04-01T09:02:00Z&limit=20
GET /v1/signals/latest?market_category=CRYPTO

Continue until has_more is false.