API Keys

Overview — what it does

Administration ▸ API Keys issues keys so external apps and hosts PUSH data to InfraGuard. The page shows two integration tracks.

• Track A · Incident reporter (Laravel + Pulse) — external Laravel PHP errors POST to /api/v1/incidents → auto-listed on the Service ▸ Problem Resolution board.
• Track B · Security scan reporter (host cron) — each host crons infr_seccheck_probe.cjs --min and POSTs to /api/v1/security/scan → Security Diagnostics.

Layout · how to use

1. [Issue key] — enter a name only. The plaintext key is shown once (issued modal). Only key_hash (a hash) is stored; the list is masked.
2. Put the issued key in the target project/host .env or reporter script.
3. Copy the on-screen integration code (env/config/reporter/bootstrap + curl · shell reporter + crontab) and deploy it.

curl -s {URL}/api/v1/ping -H "Authorization: Bearer igk_..."

Scopes are incident.write · scan.write. The canonical snippets live in resources/stubs/infraguard/*.stub, and their comments are translated to the session locale.

Data sources

• infr_api_key (key_hash + secret_enc for recovery · scopes) · App\Support\ReporterSnippet

Access

level≥10 (admin) + audit (issue/toggle/revoke).

Related

• Backup report integration · Security Diagnostics · Service ▸ Problem Resolution