Connect Huntress
Ledger reads your Huntress organizations and agents over Huntress's REST API. It never installs an agent or changes any Huntress configuration.
1. Generate an API key and secret
- Log into the Huntress portal as an administrator.
- Go to your account's API Credentials settings.
- Generate a new API key and API secret pair. Huntress shows the secret once — copy both values before leaving the page.
2. Add the connection in Ledger
From Connections → Add connection → Huntress, fill in:
| Field | Value |
|---|---|
| API key | The API key from step 1 |
| API secret | The API secret from step 1 |
Ledger sends these as HTTP Basic auth (api_key:api_secret) on every
request — never recomputed or logged — and tests the connection
immediately.
What Ledger reads
Ledger lists your Huntress organizations and every agent under them (hostname, platform, MAC addresses, and Huntress's own agent metadata), solely to reconcile them against what your other tools report for the same devices.
Rate limits
Huntress enforces a request budget on its API; Ledger paces its own requests to stay comfortably under it, so a normal sync should never trigger throttling on your account.
Rotating credentials later
Generate a new key/secret pair in Huntress and update it from the connection's Rotate credentials action in Ledger — this re-tests the connection with the new pair and never leaves the old one stored.