Signal By ID

Overview

Returns one stored signal by signal_id. Use this endpoint when you already have an ID from /signals/latest, /signals/market/{market_id}, or WebSocket delivery and want to re-fetch the full payload.

Endpoint: GET /v1/signals/{signal_id}

Request

GET /v1/signals/9b2d6f4c-1a7e-4c2f-9f5a-3e8b7c1d5a22

Path Parameters

Response

{
  "signal": {
    "signal_id": "9b2d6f4c-1a7e-4c2f-9f5a-3e8b7c1d5a22",
    "signal_type": "SMART_MONEY_FLOW",
    "timestamp": "2026-04-01T09:03:11Z",
    "signal_expiry": "2026-04-01T15:03:11Z",
    "market": {
      "platform": "polymarket",
      "market_id": "0xabc123...",
      "question": "Will ETH reach $5000 before June?",
      "category": "CRYPTO",
      "volume_24h": 215000,
      "market_closes_at": "2026-06-01T00:00:00Z"
    },
    "signal": { ... },
    "analysis": { ... }
  }
}

The nested payload under signal matches the same engine-specific shape returned by:

• GET /v1/signals/latest
• GET /v1/signals/market/{market_id}
• POST /v1/signals/smart-money

Related Endpoints

• Use Latest Signals to build a feed and collect signal_id values.
• Use Market Signals to browse all stored signals for a specific market.
• Use GET /v1/signals/{signal_id}/entities to fetch ranked wallet rows attached to a stored smart-money signal.