GET /alerts and GET /alerts/configurations are available on Pro+
and Enterprise plans. Both endpoints consume zero credits. See
Pricing and Credits.1. List alert configurations
GET /alerts/configurations returns the authenticated user’s alert IDs, filters,
frequency, and descriptions. It does not consume usage credits.
2. Request matching deals
Pass a comma-separated list of alert IDs and an inclusive UTC date range.data.alerts with a flattened deals array.
Deals are sorted newest first and deduplicated within the API response. Each match
also includes reasoning that explains why the deal satisfied the alert and an
articles array containing its related sources.
Use narrower date ranges or fewer alert IDs to keep response payloads smaller and
downstream processing faster.
3. Process matches safely
Use the deal UUID as the idempotency key in your destination.- Read the last successful UTC checkpoint.
- Request a short overlapping time window.
- Upsert or skip each deal by UUID.
- Record per-item failures for retry.
- Advance the checkpoint only when the complete batch succeeds.
4. Route by alert
KeepalertId, alertName, and the match reasoning with each downstream record.
Those fields let you route different alerts to different Slack channels, CRM lists,
email sequences, or analyst queues without reimplementing the filter logic.
Funding Alerts API
Review query parameters and the response schema.
Alert configurations
Retrieve the alerts available to the authenticated user.

