Pushover connection
Connect Pushover and understand provider behavior.
Credentials
Anchor requires a Pushover application API token and the user or group key that should receive notifications. Credentials are owner-specific and encrypted at rest.
You can replace credentials from Settings. Anchor never returns the stored secrets through its API.
Delivery behavior
Anchor records each provider request before sending it. Accepted deliveries may include a Pushover receipt that Anchor checks until Pushover reports acknowledgment, expiry, or cancellation.
Provider timeouts are treated as ambiguous: Anchor does not assume that a timed-out request was rejected. Its retry and reconciliation behavior avoids fabricating acknowledgments.
Automated tests use local fakes and never contact Pushover.