Skip to main content
GET
Discover the action names, permissions, safety hints, and JSON input schemas available to one API key.

Authentication

A paid account’s API key in x-api-key or Authorization: Bearer vc_…. OAuth access tokens are rejected by this REST route.

Request examples

Follow the documented encoding and authentication for this route. The action API’s envelope and idempotency rules apply only to action invocations.

Response

Representative excerpt from the actions array. The actual array contains every action whose primary and additional scopes are granted to this credential. Each entry includes name, title, description, scope, additionalScopes, readOnly, destructive, longRunning, openWorld, mcpAvailable, and inputSchema.
HTTP 200

Operation notes

  • The response is a single unpaginated actions array.
  • An action is listed only when every required scope is granted. action_request_get is listed independently of scopes, then checks every permission of the original action when called.
  • Successful discovery consumes no monthly integration call. Authentication, paid-plan checks, shared account rate limiting, and the route’s 3000 requests/minute public HTTP guard still apply.
  • Send credentials in a header, never access_token or api_key in the query. A supplied Authorization header must use the Bearer scheme; conflicting header credentials are rejected.
  • Authentication resolves current user, ownership, and team membership on every request. Discovery does not bypass resource ownership or role checks performed by actions.
  • Discovery is returned directly, without the action endpoint’s custom error wrapper. Do not require every discovery failure to have the action error envelope.
  • REST discovery includes REST-only actions. mcpAvailable indicates whether an action is also available through MCP; use MCP tools/list for the tools available to your connection.

Errors