Recued
Menu
← Back to packs

Full PagerDuty REST API

by recued-core v2 app_pack 8 views

Complete callable PagerDuty REST API suite pinned to the official OpenAPI document: all 465 method/path operations with no exclusions. The compatibility root keeps all 14 prior operation IDs and wire routes while seven dependency packs carry 451 additional operations. Reads are uncached; sensitive reads are marked sensitive-read. Mutations are grant-off and approval-gated, with administrative and destructive changes requiring approval every run. JSON int64 values remain exact. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base.

What this pack installs

Trust & control

What installing this whole pack would let it do. Recued grants these permissions at install — review them there before approving.

What it's allowed to do

Destructive Web APIs pagerduty external change
Read: user.current · No approvalRead: user.search · No approvalRead: service.search · No approvalRead: service.read · No approvalRead: escalation_policy.search · No approvalRead: escalation_policy.read · No approvalRead: schedule.search · No approvalRead: schedule.read · No approvalRead: on_call.search · No approvalRead: incident.search · No approvalRead: incident.read · No approvalRead: incident.note.search · No approvalDestructive: incident.status.update · Always asksWrite: incident.note.create · Asks approval

Data it touches

SurfacesWeb APIs

About

Tags

pack:pagerdutypagerdutyincidentson-callschedulesservicesautomationanalyticsapicomposition