Skip to content

List all activity logs

Request

You can get a log of activities by all admins in an app.

Requires the read_admins OAuth scope.

Security
bearerAuth
Query
created_at_afterstring

The start date that you request data for. It must be formatted as a Unix timestamp. If you leave it out, it defaults to 30 days before the request.

Example:created_at_after=1677253093
created_at_beforestring

The end date that you request data for. It must be formatted as a Unix timestamp. If you leave it out, it defaults to the time of the request.

Example:created_at_before=1677861493
pageinteger

The page number of results to return. Defaults to the first page.

Default:1
Example:page=1
per_pageinteger, [ 1 .. 250 ]

The number of results per page. Must be between 1 and 250.

Default:20
Example:per_page=20
Headers
Intercom-Versionstring(intercom_version)

Intercom API version.
If you omit the header, the API uses the version set in your app package, and 1.0 if none is set.

Enum:"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"
Example:Preview
curl -i -X GET \
  'https://api.intercom.io/admins/activity_logs?created_at_after=1677253093&created_at_before=1677861493&page=1&per_page=20' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
  -H 'Intercom-Version: Preview'

Responses

Successful response

Bodyapplication/json
typestring

String representing the object's type. Always has the value activity_log.list.

Example:"activity_log.list"

The majority of list resources in the API are paginated to allow clients to traverse data over multiple requests.

Their responses are likely to contain a pages object that hosts pagination links which a client can use to paginate through the data without having to construct a query. The link relations for the pages field are as follows.

activity_logsArray of objects(Activity Log)

An array of activity logs

Response
{ "type": "activity_log.list", "pages": { "type": "pages", "next": null, "page": 1, "per_page": 20, "total_pages": 1 }, "activity_logs": [ { … }, { … } ] }