docs/sources/acled.md

# ACLED

Provides conflict events, fatalities, event types, and locations.

- Auth: `ACLED_EMAIL` and `ACLED_PASSWORD`. `ACLED_USER` or `ACLED_USERNAME` may be used as aliases for `ACLED_EMAIL`.
- Flow: OAuth password grant is tried first, then cookie session fallback.
- Failure modes are classified as `no_credentials`, `auth_failed`, `access_denied`, or `api_failed`.
- Behavior: missing, rejected, or unauthorized credentials produce degraded source health with a concise operator message.
- Secret handling: debug output never prints bearer tokens, cookies, or the configured password.
- Test: run `node --test test/acled-source.test.mjs`; with real credentials, run `node apis/sources/acled.mjs`, then check `/api/health`.

`access_denied` normally means the login worked but the account cannot read API data. Check that ACLED terms are accepted, required profile fields are complete, and API access is enabled for the account.
docs: add registry dockge and dashboard operations 2026-05-16 21:18:51 +02:00			`# ACLED`

			`Provides conflict events, fatalities, event types, and locations.`

fix: improve acled auth diagnostics 2026-05-17 14:05:01 +02:00			- Auth: `ACLED_EMAIL` and `ACLED_PASSWORD`. `ACLED_USER` or `ACLED_USERNAME` may be used as aliases for `ACLED_EMAIL`.
docs: add registry dockge and dashboard operations 2026-05-16 21:18:51 +02:00			`- Flow: OAuth password grant is tried first, then cookie session fallback.`
fix: improve acled auth diagnostics 2026-05-17 14:05:01 +02:00			- Failure modes are classified as `no_credentials`, `auth_failed`, `access_denied`, or `api_failed`.
			`- Behavior: missing, rejected, or unauthorized credentials produce degraded source health with a concise operator message.`
			`- Secret handling: debug output never prints bearer tokens, cookies, or the configured password.`
			- Test: run `node --test test/acled-source.test.mjs`; with real credentials, run `node apis/sources/acled.mjs`, then check `/api/health`.

			`access_denied` normally means the login worked but the account cannot read API data. Check that ACLED terms are accepted, required profile fields are complete, and API access is enabled for the account.