DocumentationOpen PingAgain
Browse

Developer API

API keys, authentication, and scopes

Create scoped API keys and send Bearer authentication safely.

API requests use a scoped key in the Authorization header.

Authenticate

curl --header "Authorization: Bearer pa_example_token" \
  "${PINGAGAIN_BASE_URL}/api/v1/monitors"

Never place a key in a query string, screenshot, repository, browser log, or support message. Use separate keys for separate systems so one integration can be revoked without interrupting another.

Available scopes

ScopePurpose
monitors:readList and read monitor information
monitors:writeCreate or change monitor configuration
monitors:controlPause, resume, or request a recheck
incidents:readList incident information

Grant only what the client needs. A resource identifier never overrides the key’s account or scopes. Revoke keys when ownership changes or if a value may have been exposed.

Next: make a first API request or use the Monitors API.