Skip to main content
GET
Get All Signals
Signal events are radar events that have been scored for market relevance. The canonical significance field is a numeric score indicating how significant the event is — higher scores mean greater potential market impact. Signals are a subset of radar: not every radar event qualifies as a signal. The live API returns both canonical field names and legacy compatibility fields during the schema transition. New integrations should build against the canonical names:
  • summary
  • bullets
  • owners
  • participants
  • evidence
  • latestEvidenceTimestamp
  • significance
Use this endpoint to pull a complete scored feed since a given timestamp.
This is a bulk feed endpoint intended for higher-tier polling and export workflows. For most applications, prefer /v1/signal/top, /v1/signal/byOrganizationId, or /v1/signal/byCategory.

Query Parameters

  • since (string, required) — ISO 8601 timestamp. Only return events newer than this time. See Polling Guide.
  • limit (integer, default: 25, max: 25)
  • offset (integer, default: 0, max: 250)
  • cursor (string, optional) — Opaque cursor token from a previous next_cursor response. When provided, since is required and offset is ignored.
The since parameter is required. Requests without it return 400:
Invalid timestamps (e.g. since=garbage) are also rejected with 400.This endpoint is for recent monitoring, not deep historical replay. The since timestamp cannot be older than 7 days. For deeper history, use scoped routes or contact Shoal about export access.

Request

cURL

Response (200)

Legacy compatibility fields are still present for existing clients:
  • globalSummary -> summary
  • bulletSummary -> bullets
  • eventOwner -> owners
  • eventParticipants -> participants
  • posts -> evidence
  • latestPostTimestamp -> latestEvidenceTimestamp
  • signal -> significance