younifyd
Menu

List Incident Log Entries

List log entries for an incident

GET/incidents/{id}/log_entries

Use it in a workflow

  1. Add a step and choose the PagerDuty connector.
  2. Pick the List Incident Log Entries action (under Incidents).
  3. Fill in the fields below, then reference the result from later steps as {{listIncidentLogEntries.response.data}}.

Request

Path parameters

idstringrequired

The ID of the resource.

Query parameters

limitinteger

The number of results per page.

offsetinteger

Offset to start pagination search results.

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 information.

Default false

time_zonestring (tzinfo)

Time zone in which results will be rendered. This will default to the account time zone.

sincestring (date-time)

The start of the date range over which you want to search.

untilstring (date-time)

The end of the date range over which you want to search.

is_overviewboolean

If `true`, will return a subset of log entries that show only the most important changes to the incident.

Default false

include[]string

Array of additional Models to include in response.

One ofincidentsserviceschannelsteams

Headers

Acceptstringrequired

The `Accept` header is used as a versioning header.

Default "application/vnd.pagerduty+json;version=2"

Content-Typestringrequired

One ofapplication/jsonDefault "application/json"

Response

Returns 200 with a any. Read it in later steps with {{listIncidentLogEntries.response.data.<field>}}.

Need more? See the PagerDuty guide for connection setup and behaviour shared by every action.