GET /users/{id}/audit/records
The response will include audit records with changes that are made to the identified user not changes made by the identified user.
The returned records are sorted by the execution_time from newest to oldest.
See Cursor-based pagination for instructions on how to paginate through the result set.
For more information see the Audit API Document.
Scoped OAuth requires: audit_records.read
Servers
- https://api.pagerduty.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
id |
String | Yes |
The ID of the resource. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Accept |
String | Yes |
The Default value: "application/vnd.pagerduty+json;version=2" |
Content-Type |
String | Yes |
Possible values:
Default value: "application/json" |
Query parameters
| Name | Type | Required | Description |
|---|---|---|---|
limit |
Integer | No |
The minimum of the |
until |
String | No |
The end of the date range over which you want to search. If not specified, defaults to |
since |
String | No |
The start of the date range over which you want to search. If not specified, defaults to |
cursor |
String | No |
Optional parameter used to request the "next" set of results from an API. The value provided here is most commonly obtained from the |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.