Skip to main content

​
Overview

The list_change_events tool retrieves all change events in your PagerDuty account. Change events represent changes to systems, services, and applications that can be correlated with incidents to provide context for troubleshooting.
This is a read-only tool that does not modify any data in your PagerDuty account.

​
Parameters

​
limit
integer
default:"25"
Maximum number of results to return. Must be between 1 and 100.Example: 50
​
offset
integer
default:"0"
The offset of the first record returned. Used for pagination.Example: 25
​
total
boolean
Set to true to include the total count of change events in the response. By default, this is not included for faster response times.Example: true
​
team_ids
array
Filter change events by team IDs. Only returns change events related to the specified teams.Example: ["TEAM123", "TEAM456"]
​
integration_ids
array
Filter change events by integration IDs. Only returns change events created by the specified integrations.Example: ["INT123", "INT456"]
​
since
datetime
The start of the date range to search. Returns change events occurring after this timestamp.Example: "2024-01-01T00:00:00Z"
​
until
datetime
The end of the date range to search. Returns change events occurring before this timestamp.Example: "2024-12-31T23:59:59Z"

​
Response

Returns a list of change event objects.
​
response
array
Array of change event objects

​
Example Usage

"Show me all change events from the last week"

​
Use Cases

  • Incident correlation - Find change events that coincided with incidents
  • Audit deployments - Review all changes made to your systems
  • Team visibility - View changes made by specific teams
  • Integration tracking - See which integrations are creating change events
  • Timeline analysis - Build a timeline of system changes

​
Response Example

{
  "response": [
    {
      "id": "CHGEVT123",
      "type": "change_event",
      "summary": "Deployed v2.3.1 to production",
      "timestamp": "2024-01-15T14:30:00Z",
      "source": "deployment-pipeline",
      "services": [
        {
          "id": "PSVC123",
          "type": "service_reference"
        }
      ]
    }
  ]
}

Build docs developers (and LLMs) love

Get started for freeTalk to us