Alert logs

Consult the alerts built from fraud reports across the ecosystem. Where the Reporting section is about writing reports, this section is about reading the aggregated result: searching alerts, viewing one in full, and exporting the feed into your own systems.

An alert groups every report on the same IBAN. Each alert carries an aggregate qualification (PENDING, CONFIRMED, REJECTED, UNDER_INVESTIGATION) and counts of its reports, sightings, and false positives.

Endpoints

Sent vs received

• Sent — alerts where your institution submitted one or more reports. Results split each alert into myReports and otherReports so you can see your contribution alongside the ecosystem's.
• Received — alerts on IBANs whose account you manage (you are the holder). These are the ones you typically need to qualify.

Both search endpoints are paginated and support filters such as iban, qualification, and a date range (sent search also supports bic and author). Responses include page, totalPages, and totalAlerts.

Alert details

GET /sharing/v1/alerts/{alertId} returns the full picture for a single alert: every linked report, the qualification notes added by the holder, participant observations, comments, and whether each report is marked for deletion.

Exporting

GET /sharing/v1/alerts/export is designed to sync alerts into your own database:

• Returns minimal rows (id, iban, bic, qualification, reportsCount, updatedAt, isActive).
• Cursor-based and incremental — pass the returned nextCursor to fetch the next page; it is null once you have caught up. Use updatedAfter to resume from a known point.
• The isActive flag tells you when to deactivate or remove an alert locally.

🚧

Rate limiting

The export endpoint is rate-limited per tenant and may return 429 if called too frequently. Paginate with the cursor rather than re-fetching from the start.