> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dbhost.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Connection events

> Read bounded authenticated PgBouncer events for a managed database.

When the B10 history rollout is enabled, `GET
/api/v1/databases/{id}/connection-events` returns events attributed to the
selected managed database by its generated role name and the signed private
source. A database-scoped API key is required. Use `limit` (1–100, default
25\) and the opaque `nextCursor` to page older events. The response is
`no-store` and is always restricted to that database.

Raw events are retained for seven days. `kind` is one of `attempt`,
`authenticated`, `auth_refused` and `closed`; an attempt does **not** prove a
successful login. `tls` may be `true`, `false` or `null`. `source` is
`pgbouncer_log`, and `sampled` is `false`. No SQL text, password, token,
client IP or cipher is returned. The `daily` array contains outcome/TLS
counts for up to 30 days. `coverage` is `unavailable`, `gap_recorded` or
`no_recorded_gap`; the last value does not promise a complete connection
history.

This first attribution path is limited to DBHost generated managed-role
names. Events that cannot be bound to an immutable database ID stay in the
private source inbox and are not shown to another tenant. Direct PostgreSQL
migration sessions and the older sampled-client list are separate sources.

CLI: `dbhost databases events <id> [--limit 1-100] [--cursor CURSOR] [--json]`.
The endpoint returns `FEATURE_NOT_AVAILABLE` while the customer rollout is
off.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.