What to do instead
Poll the signal feed
GET /api/signals is the only delivery mechanism for signals. Responses cache 300s, so polling faster than that returns cached bytes.Push integrations
Slack, Discord, Teams, and Telegram receive outbound dispatches from the workspace API. That is push to a chat surface, not a webhook to your server.
Outbound integration dispatch
The workspace API can push to a connected chat surface:POST /integrations/{slack,teams,discord}/connect, then test it with POST /integrations/{id}/test. See Slack and Discord.
This is the closest thing to push delivery that exists, and it is deliberately one-way into a chat client — it will not call an arbitrary URL of yours.
Polling correctly
1
Poll no faster than the cache
300 seconds. Anything faster is wasted requests against
stale-while-revalidate bytes.2
Diff on signal_id, not on total
A feed whose count is unchanged may still have rotated its contents.
3
Check data_mode every time
A feed that flips to
empty means the producing host stopped running, not that risk disappeared. Alert on that transition.4
Treat generated_at as the freshness signal
A feed serving the same
generated_at for hours is a stalled producer.Also absent
Scienter publishes impersonal market signals of general and regular circulation. Nothing here is investment, legal, or tax advice, or a recommendation to buy, sell, or hold any asset. Scienter is not a registered investment adviser or broker-dealer. Trading digital assets can result in the total loss of your funds — see Disclaimers for the full text.