GET /incidents/{id}/log_entries

List log entries for the specified incident.

An incident represents a problem or an issue that needs to be addressed and resolved.

A Log Entry are a record of all events on your account.

For more information see the API Concepts Document

Scoped OAuth requires: incidents.read

Servers

Path parameters

Name Type Required Description
id String Yes

The ID of the resource.

Request headers

Name Type Required Description
Accept String Yes

The Accept header is used as a versioning header.

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

Content-Type String Yes

Possible values:

  • "application/json"

Default value: "application/json"

Query parameters

Name Type Required Description
time_zone String No

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

limit Integer No

The number of results per page.

include String No

Array of additional Models to include in response.

Possible values:

  • "channels"
  • "incidents"
  • "services"
  • "teams"
until String No

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

since String No

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

is_overview Boolean No

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

Default value: false

offset Integer No

Offset to start pagination search results.

total Boolean No

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

Default value: false

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.