Count the active CrowdSec decisions by origin and scenario
Returns how many decisions are active across every origin, blocklists included, with the count per origin and the ten scenarios with the most decisions.
session<token>Session cookie authentication.
Request fulfilled, document follows
application/json- response
Counts of the active CrowdSec decisions across every origin.
byOrigin*array<>Every origin, the most decisions first.
topScenarios*array<>The ten scenarios with the most decisions, the most first.
total*integercurl -X GET 'https://geometrikks.example.com/api/v1/crowdsec/stats'{ "byOrigin": [ { "count": 0, "origin": "string" } ], "topScenarios": [ { "count": 0, "scenario": "string" } ], "total": 0}List the traffic from DROP networks, with their bans GET
Returns each Spamhaus DROP network that sent requests in the window, busiest first, with the Range decision on it. The totals cover every network with traffic, not only the page. A client inside nested networks counts under the narrowest one. When the LAPI does not answer, you still get the traffic, with every `decision` null and `decisionsAvailable` false.
Get the CrowdSec integration status GET
Returns whether the integration is on, whether bans and alerts are available, whether the LAPI answers and whether `/ws/crowdsec` streams changes. Unlike the other CrowdSec endpoints, it answers while the integration is off, with every field false.