You must enable javascript in order to use the Slack API Documentation. You can do this in your browser settings.
Go to Slack

team.integrationLogs

You're not signed into any teams. Sign in to test authentication.

Supported token types:
Expected scopes:

This method lists the integration activity logs for a team, including when integrations are added, modified and removed. This method can only be called by Admins.

Arguments

This method has the URL https://slack.com/api/team.integrationLogs and follows the Slack Web API calling conventions.

Argument Example Required Description
token xxxx-xxxxxxxxx-xxxx Required

Authentication token bearing required scopes.

app_id   Optional

Filter logs to this Slack app. Defaults to all logs.

change_type added Optional

Filter logs with this change type. Defaults to all logs.

count 20 Optional, default=100

Number of items to return per page.

page 2 Optional, default=1

Page number of results to return.

service_id   Optional

Filter logs to this service. Defaults to all logs.

user W1234567890 Optional

Filter logs generated by this user’s actions. Defaults to all logs.

Present arguments as parameters in application/x-www-form-urlencoded querystring or POST body. This method does not currently accept application/json.

Response

The response contains a list of activity logs followed by pagination information.

{
    "ok": true,
    "logs": [
        {
            "service_id": "1234567890",
            "service_type": "Google Calendar",
            "user_id": "U1234ABCD",
            "user_name": "Johnny",
            "channel": "C1234567890",
            "date": "1392163200",
            "change_type": "enabled",
            "scope": "incoming-webhook"
        },
        {
            "app_id": "2345678901",
            "app_type": "Johnny App"
            "user_id": "U2345BCDE",
            "user_name": "Billy",
            "date": "1392163201",
            "change_type": "added"
            "scope": "chat:write:user,channels:read"
        },
        {
            "service_id": "3456789012",
            "service_type": "Airbrake",
            "user_id": "U3456CDEF",
            "user_name": "Joey",
            "channel": "C1234567890",
            "date": "1392163202",
            "change_type": "disabled",
            "reason": "user",
            "scope": "incoming-webhook"
        }
    ],
    "paging": {
            "count": 3,
            "total": 3,
            "page": 1,
            "pages": 1
    }
}

Logs can contain data for either a service or API application. If it's a service, service_id and service_type will be returned, and if it's an API application, app_id and app_type will be returned.

Logs can also contain different change_types. The possible types are: added, removed, enabled, disabled, and updated.

If the log entry is an RSS feed, the log will also contain rss_feed (with a value of true), rss_feed_change_type, rss_feed_title and rss_feed_url.

When a disabled event is logged, its log entry will also contain a reason for why the event occurred. The list of possible reasons are:

  • user - Manually disabled by user
  • rate_limits - Rate limits exceeded
  • slack - Disabled by Slack
  • errors - Too many errors
  • system - A system change (i.e. channel archived)
  • admin - Admin (i.e. user deleted)
  • api_decline - User declined the API TOS
  • deauth - Service de-authorized

The paging information contains the count of logs returned, the total number of logs, the page of results returned in this response and the total number of pages available.

Errors

This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok params in the response.

Error Description
not_authed

No authentication token provided.

invalid_auth

Invalid authentication token.

account_inactive

Authentication token is for a deleted user or workspace.

no_permission

The workspace token used in this request does not have the permissions necessary to complete the request.

user_is_bot

This method cannot be called by a bot user.

invalid_arg_name

The method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.

invalid_array_arg

The method was passed a PHP-style array argument (e.g. with a name like foo[7]). These are never valid with the Slack API.

invalid_charset

The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.

invalid_form_data

The method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.

invalid_post_type

The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/x-www-form-urlencoded multipart/form-data text/plain.

missing_post_type

The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.

team_added_to_org

The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.

request_timeout

The method was called via a POST request, but the POST data was either missing or truncated.

Warnings

This table lists the expected warnings that this method will return. However, other warnings can be returned in the case where the service is experiencing unexpected trouble.

Warning Description
missing_charset

The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.

superfluous_charset

The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.

Argument Value
token Required Generate tokens to test with here.
app_id Optional
change_type Optional
count Optional, default=100
page Optional, default=1
service_id Optional
user Optional
Extra args