Documentation Index

Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt

Use this file to discover all available pages before exploring further.

Get Action List

Prev Next

Available in Classic and VPC

Get the list of Cloud Functions actions.

Request

This section describes the request format. The method and URI are as follows:

Method URI
GET /api/v2/packages/{packageName}/actions
Note

Singapore and Japan Regions are available only in the VPC environment.

Request headers

For information about the headers common to all Cloud Functions APIs, see Cloud Functions request headers.

Request path parameters

You can use the following path parameters with your request:

Field Type Required Description
packageName String Required Package name
  • Enter the special character "-" for actions that are not part of a package.
    • Example: /packages/-

Request query parameters

You can use the following query parameters with your request:

Field Type Required Description
platform String Optional Platform type
  • vpc | classic (default)

Request example

The request example is as follows:

curl --location --request GET 'https://cloudfunctions.apigw.ntruss.com/api/v2/packages/package003/actions?platform=classic' \
--header 'Content-Type: application/json' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Sub Account Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'

Response

This section describes the response format.

Response body

The response body includes the following data:

Field Type Required Description
content Object - Action list details
content.action Array - Action list: action

action

The following describes action.

Field Type Required Description
description String - Action description
name String - Action name
runtime String - Language in use
web Boolean - Web action configuration

Response status codes

For information about the HTTP status codes common to NAVER Cloud Platform, see Ncloud API response status codes.

Response example

The response example is as follows:

{
    "content": {
        "actions": [
            {
                "description": "Create Action",
                "name": "action003",
                "runtime": "nodejs:16",
                "web": false
            },
            {
                "description": "Create Action",
                "name": "action002",
                "runtime": "nodejs:16",
                "web": false
            },
            {
                "description": "Create Action",
                "name": "action001",
                "runtime": "nodejs:16",
                "web": false
            },
            {
                "description": "Create Action",
                "name": "action000",
                "runtime": "nodejs:16",
                "web": false
            }
        ]
    }
}