List incident notes with the PagerDuty API
Lists the notes of an incident, each with its content, author and creation time.
- Identifier
- pagerduty_list_incident_notes
The request
POST https://connect.reportei.com/api/tools/pagerduty_list_incident_notes/execute
Authorization: Bearer <merchant token>
x-customer-token: <customer token>
Content-Type: application/json
Accept: application/json
{
"customer_toolkit": "<connection UUID>",
"arguments": {
"id": "<id>"
}
}Your system sends your customer's connection id and the tool arguments. The headers are the same as the rest of the Connect API: your product's token and your customer's token.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| id | string | Yes | Id of the incident, from List incidents. |
Supported connections
Your customer connects their PagerDuty account once, with one of the modes below. The same connection serves every tool of the toolkit.
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.
The response
On success, Connect preserves the app's response status and body. HTTP errors returned by the app use the {error, api_error} envelope; authentication or validation can fail before execution. The X-Toolkit-Execution-Id header identifies the recorded execution, available at GET /api/tools/executions/{uuid}.
Ready for AI agents
This tool's input is a JSON Schema, available at GET /api/tools/pagerduty_list_incident_notes. It becomes your agent's tool definition with no conversion.
Other PagerDuty tools
- List incidentsGETLists the incidents of the account created in the last month, or in the range of since and until. There is no filter by status, service or assignee here, so read status, service and assignments in each item. Page with limit and offset while more is true.
- Get incidentGETReturns one incident with its status, urgency, priority, service, assignments, acknowledgements and escalation policy.
- Create incidentPOSTCreates an incident on a service, which notifies the escalation policy of the service, or the users in assignments. Needs type, title and service. Send assignments or escalation_policy, never both. An incident the user assigns to themselves starts acknowledged, without notifying them.
- Update incidentPUTAcknowledges, resolves, reassigns or escalates an incident, or changes its title, urgency, priority or service. Send type and only the fields to change. Reassigning or escalating notifies the new responders, and setting status on a resolved incident reopens it.
- Create incident notePOSTAdds a note to an incident, signed by the user of the connection. An incident holds up to 2000 notes.
- List incident log entriesGETLists the timeline of an incident: triggers, notifications, acknowledgements, assignments, escalations, notes and resolution, each with the agent and the time. Page with limit and offset while more is true.
- List servicesGETLists the services of the account, each with its id, name, status and escalation policy. The id is what Create incident and Update incident ask for. Page with limit and offset while more is true.
- List on-callsGETLists who is on call, one entry per user, escalation policy and level, with the schedule when the shift comes from one. Without since and until it returns the on-calls of right now. Page with limit and offset while more is true.
Toolkits in the same category
See all 100 toolkitsSee Connect applied to your product.
Try it for 15 days with no card, or walk our team through your use case.
