crowdsec-service-apilisted

# CrowdSec Service API (SAPI) — cloud blocklist / allowlist / integration automation SAPI is the **premium** REST API behind the CrowdSec Console. It manages **cloud-side** objects (private blocklists, allowlists, decisions, firewall integrations) that then push down to enrolled engines and bouncers. It is **not** the local engine API — there is no `cscli` here, only HTTPS. - **Base URL:** `https://admin.api.crowdsec.net/v1` - **Auth:** `x-api-key: <key>` header on every call. (One exception: the integration *content* endpoint uses HTTP Basic with credentials minted at integration creation — see [references/integrations.md](./references/integrations.md).) - **Interactive API docs:** <https://admin.api.crowdsec.net/v1/docs> · spec <https://admin.api.crowdsec.net/v1/openapi.json> ## Boundary — this skill vs the `crowdsec` skill | You want to… | Use | |---|---| | Create/manage a **private blocklist** in the cloud, push IPs to it via API | this skill | | Wire a firewall/appliance (Palo Alto, Fortinet…) to a cloud **integration** | this skill | | Manage **cloud allowlists**, subscribe engines/tags/orgs to lists | this skill | | Create/manage **org-level decisions** (targeted or ad-hoc bans, non-IP scopes, per tag/entity) | this skill | | Pull **remediation ROI metrics** | this skill | | Install / run / debug the **local engine**, `cscli`, bouncers, WAF | the `crowdsec` skill | | **Enroll** an engine into the Console (`cscli console enroll`) | the `crowdsec` skill → `refe