Compatible with
account required
PagerDuty
PagerDuty sends a test event, stores the provider message id when offered, and records health. PagerDuty is not a partnership.
Verification: test_verified. Connection: unknown. Credentials: none. Live E2E: no.
PagerDuty routing key is not configured.
What sslcertificates.io can do
PagerDuty sends a test event, stores the provider message id when offered, and records health. PagerDuty is not a partnership. Capabilities: send, health. Authentication uses api_key.
Required permissions
PagerDuty token or webhook. Least privilege.
Setup
Open Dashboard → Integrations → PagerDuty. Enter the credentials described on this page. Values are encrypted at rest and never shown again. Run Test connection. Discovery runs only after authentication succeeds. Select a discovered resource. Do not paste opaque IDs unless the provider cannot enumerate them. Perform the certificate or notification action, then confirm the external system matches. Disconnect removes stored credentials and owned test resources created by sslcertificates.io.
Known limitations
Incoming webhook URLs are secrets. Legacy Microsoft Office connectors are not implemented; Teams uses Workflows.
Official sources
Fact checked 2026-09-20. https://developer.pagerduty.com/docs/events-api-v2/overview/ PagerDuty is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.
Capabilities
Connect
PagerDuty is a trademark of its owner. sslcertificates.io is not a partner or certified reseller unless a written agreement exists.