Skip to main content
New data arrives once each business morning (UTC). To keep your own copy current, pull only what changed since your last call: every signal carries an updated_at, and changed_since returns the signals that changed after it.

How updated_at works

updated_at is the time of the daily build at which anything the API serves about a signal last changed: its lifecycle, its opening evidence, its outcomes (realised fills in as sessions pass) or its structures. Times are UTC with a Z, so you can paste them into a URL as they are.

Pull only what changed

1

First pull

Page through /v1/signals?changed_since=2000-01-01&limit=1000. With changed_since, there is no default date window: you get every signal. Store each signal and remember the largest updated_at you saw.
2

Each morning

Call /v1/signals?changed_since=<largest updated_at>. Replace the signals it returns.
3

Remove withdrawn signals

The same response lists withdrawn: signals removed since then. Delete them from your copy.
changed_since accepts 2026-11-03T12:05:36Z, an offset such as +00:00, or a date (2026-11-03). Other text answers 400.

Withdrawn signals

Rarely, an upstream restatement of exchange data moves or removes a signal. The API then withdraws it rather than forgetting it:
  • /v1/signals/{id} answers 410 Gone with status: "withdrawn", withdrawn_at and last_known, the signal as it was last published.
  • /v1/signals?changed_since=… lists it under withdrawn once.
  • If the signal comes back in a later run, it is live again, with a new updated_at.

Revalidate with ETags

Every response carries an ETag and Cache-Control: private, max-age=300. Send the ETag back in If-None-Match: until the next run, the API answers 304 Not Modified with no body. An ETag belongs to one run and one URL.
Last modified on November 3, 2026