admin.functions.list

View other methods

Look up functions by a set of apps

Reference docs Tester

Facts

Method access

HTTP

JavaScript

Python

Java

HTTP

POSThttps://slack.com/api/admin.functions.list

Bolt for Java

app.client().adminFunctionsList

Bolt for Python

app.client.admin_functions_list

Bolt for JavaScript

app.client.admin.functions.list

Required scopes

User tokensadmin.workflows:read

Content types

application/x-www-form-urlencodedapplication/json

Rate limits

Tier 2

Arguments

Required arguments

token

token

·Required

Authentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.

Example

xxxx-xxxxxxxxx-xxxx

app_ids

array

·Required

Comma-separated array of app IDs to get functions for; max 50

Example

A02,A1234

Optional arguments

cursor

string

·Optional

Set cursor to next_cursor returned by the previous call to list items in the next page

Example

dXNlcjpVMDYxTkZUVDI=

limit

integer

·Optional

The number of results that will be returned by the API on each invocation. Must be between 1 and 1000, both inclusive

Default

100

Example

20

team_id

·Optional

The team context to retrieve functions from

Example

T00000001

Usage info

List all functions installed by a set of app IDs; returns an array of function objects.

Example responses

Common successful response

Typical success response

{
    "ok": true,
    "functions": [
        {
            "id": "123ABC456DE",
            "callback_id": "sample_function",
            "title": "Sample function",
            "description": "A sample function",
            "type": "app",
            "input_parameters": [
                {
                    "type": "string",
                    "name": "message",
                    "description": "Message to be posted",
                    "title": "Message",
                    "is_required": true
                },
                {
                    "type": "slack#/types/user_id",
                    "name": "user",
                    "description": "The user invoking the workflow",
                    "title": "User",
                    "is_required": false
                }
            ],
            "output_parameters": [
                {
                    "type": "string",
                    "name": "updatedMsg",
                    "description": "Updated message to be posted",
                    "title": "Updated Msg",
                    "is_required": true
                }
            ],
            "app_id": "789FGH1011IJ",
            "date_created": 1692283027,
            "date_updated": 1692725035,
            "date_deleted": 0
        }
    ],
    "response_metadata": {
        "next_cursor": "aWQ6MTE3MDk1NTIzNDAxOQ=="
    }
}

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
`invalid_cursor`	Value passed for `cursor` was not valid or is no longer valid.
`not_allowed`	The user is not allowed to access this API method
`access_denied`	Access to a resource specified in the request is denied.
`account_inactive`	Authentication token is for a deleted user or workspace when using a `bot` token.
`deprecated_endpoint`	The endpoint has been deprecated.
`ekm_access_denied`	Administrators have suspended the ability to post a message.
`enterprise_is_restricted`	The method cannot be called from an Enterprise.
`invalid_auth`	Some aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.
`is_bot`	This method cannot be called by a legacy bot.
`method_deprecated`	The method has been deprecated.
`missing_scope`	The token used is not granted the specific scope permissions required to complete this request.
`not_allowed_token_type`	The token type used in this request is not allowed.
`not_authed`	No authentication token provided.
`no_permission`	The workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.
`org_login_required`	The workspace is undergoing an enterprise migration and will not be available until migration is complete.
`token_expired`	Authentication token has expired
`token_revoked`	Authentication token is for a deleted user or workspace or the app has been removed when using a `user` token.
`two_factor_setup_required`	Two factor setup is required.
`accesslimited`	Access to this method is limited on the current network
`fatal_error`	The server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.
`internal_error`	The server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.
`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_arguments`	The method was either called with invalid arguments or some detail about the arguments passed is invalid, which is more likely when using complex arguments like blocks or attachments.
`invalid_array_arg`	The method was passed an array as an argument. Please only input valid strings.
`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/json` `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.
`ratelimited`	The request has been ratelimited. Refer to the `Retry-After` header for when to retry the request.
`request_timeout`	The method was called via a `POST` request, but the `POST` data was either missing or truncated.
`service_unavailable`	The service is temporarily unavailable
`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.

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.

API response

URL

POST body

Submit your arguments to see the API response