Aident logoAident logo centerAident Loadout
Use CasesPricingDocs
ENStart Now
AppsPagerDuty ToolsPagerduty Retrieve Service Change Events By Id
PagerDuty Tools

Pagerduty Retrieve Service Change Events By Id

Retrieves change events associated with a specific PagerDuty service. This endpoint allows you to fetch informational updates about recent changes such as code deploys, system configuration modifications, and other significant alterations related to the specified service. It's p…

Write actionRisk level 2 of 5API key connection
Use Pagerduty Retrieve Service Change Events By Id

Pricing and limits

Aident logo

Product

Aident LoadoutAident Playbook EditorOpen-CUAK

About

AppsSkillsUse CasesDocsBlogPricingDownloadsPrivacy PolicyTerms of Service

Alternatives

vs Composiovs Zapier
llms.txtGet an AI summary of Aident LoadoutSummarize with ChatGPTSummarize with ClaudeSummarize with GeminiSummarize with Perplexity

© Aident Labs, 2024-2026

Pricing
Free
Unified payment
Not currently supported

Inputs

  • idstring
    Required
    The ID of the resource.
  • limitinteger
    The number of results per page.
  • sincestring
    The start of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes.
  • totalboolean
    By default the `total` field in pagination responses is set to `null` to provide the fastest possible response times. Set `total` to `true` for this field to be populated. See our [Pagination Docs](https://developer.pagerduty.com/docs/rest-api-v2/pagination/) for more informatio…
  • untilstring
    The end of the date range over which you want to search, as a UTC ISO 8601 datetime string. Will return an HTTP 400 for non-UTC datetimes.
  • offsetinteger
    Offset to start pagination search results.
  • team__idsarray
    An array of team IDs. Only results related to these teams will be returned. Account must have the `teams` ability to use this parameter.
  • integration__idsarray
    An array of integration IDs. Only results related to these integrations will be returned.

Observable output

  • data
    Required
    Data from the action execution
  • errorstring
    Error if any occurred during the execution of the action
  • successfulboolean
    Required
    Whether or not the action execution was successful or not

Skills that use this Action

Related use cases

No verified related use cases are linked yet.

Official source

Provider source

Skills that use this Action

No published Skills explicitly reference this Action yet.