Hookmetry access control
Access to endpoints, webhook logs, replay, observability, and CLI diagnostics is enforced through authenticated account credentials. Public capture and share URLs have separate purposes and security properties.
Access paths
| Access path | Protection and scope |
|---|---|
| Dashboard | Authenticated account session. |
| REST API | Bearer JWT scoped to the authenticated account. |
| CLI | Locally stored bearer token with account-scoped operations. |
| Capture URL | Public sender endpoint; use signature validation to authenticate supported providers. |
| Debug share link | Public, time-limited read-only access to one selected log. |
Credential handling
- Do not commit JWTs, CLI tokens, or webhook secrets to source control.
- Do not include signing secrets in capture URLs or query strings.
- Use separate secrets for test and production environments.
- Rotate credentials after suspected disclosure or device loss.
Ownership checks
Authenticated log and endpoint operations verify account ownership. A credential cannot retrieve another account’s log through the normal customer API.