Developer tools

PagerDuty in your product and your AI agents, through one API

The PagerDuty toolkit covers incidents, their notes and log entries, services, on-call shifts, users, escalation policies and priorities. Through Connect, a product or AI agent triggers and handles incidents in the customer's account, with the permissions of the user who created the token, without building the integration.

15 days to try it. No credit card.

POST https://connect.reportei.com/api/tools/pagerduty_create_incident/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json

{
  "customer_toolkit": "<connection UUID>",
  "arguments": {
    "incident": {}
  }
}
Example: the "Create incident" tool on an account your customer connected.

How it works

From a connected customer to the first PagerDuty call.

  1. 1

    Your customer connects the account

    Your system opens a Connect session for the toolkit and your customer connects their PagerDuty account. You get the connection id.

  2. 2

    Your product calls the tool

    A POST to /api/tools/{tool}/execute with the connection id and arguments. On success, Connect preserves the app's response status and body.

  3. 3

    Connect handles the rest

    It stores the credential encrypted, renews tokens for OAuth connections that support renewal and records executions in an audit trail available through the API.

Use cases

What your product does with PagerDuty.

  • Incidents from your monitoring

    Create an incident on a service when your product detects a failure, which notifies the escalation policy of that service.

  • On-call lookup for an agent

    Let an AI agent list who is on call right now, read the incident timeline from its log entries and post a note with what it found.

  • Incident triage

    List recent incidents, then acknowledge, reassign, escalate or resolve them from your own interface or from a chat with an agent.

Tools

12 PagerDuty tools

See all 12 tools

Connection

How your customer connects the account

Official PagerDuty documentation

API key

Your customer pastes the app's key on a Connect screen, or your system sends the key with POST /api/customer-toolkits, with no screen.

Questions about the PagerDuty toolkit

Do I need to build against the PagerDuty API?

No. Connect ships 12 PagerDuty tools, described and ready. Your customer connects the account and your system calls every tool through the same endpoint, with the same request format.

How does my customer connect their PagerDuty account?

With the mode the toolkit accepts: API key. Connect stores the credential encrypted and never returns it to your system.

Does it work with AI agents?

Yes. Each tool's input is described in JSON Schema, which your agent uses directly as a tool definition. The agent picks the tool and the arguments, and your system makes the call to Connect.

Does my customer need a Reportei account?

No. Your customer connects the account on a Connect screen, or your system sends the credential through the API, and they keep using only your product.

Toolkits in the same category

See all 100 toolkits

See Connect applied to your product.

Try it for 15 days with no card, or walk our team through your use case.