> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-api/rest-api-v2/providers-and-actions/get-v2-providers-provider_id-actions.md).

# GET /v2/providers/{provider\_id}/actions

## List Provider Actions

> List a provider's actions; fetch a single action for its input/output schema.\
> \
> \*\*How to use\*\*\
> \
> Choose an action ID here, then fetch its detail before invoking it. List entries are for discovery and need not contain the full input/output contract.\
> \
> \*\*Authentication and permissions\*\*\
> \
> Required permissions: \`connections.read\`. Resource and owner access checks also apply.

```json
{"openapi":"3.1.0","info":{"title":"StackAI API","version":"0.1.0"},"tags":[{"name":"endpoint-listProviderActionsV2"}],"servers":[{"url":"https://api.stack-ai.com","description":"Hosted API. Use your deployment-specific origin for private installations."}],"security":[{"HTTPBearer":[]}],"components":{"securitySchemes":{"HTTPBearer":{"type":"http","scheme":"bearer","description":"Personal API key (sk_...) or supported user access JWT. See Authentication and authorization for endpoint restrictions and scopes. Use exactly one Authorization header."}},"schemas":{"OffsetBasedPaginationResponse_ProviderActionSummaryResponseV2_":{"properties":{"response_code":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Response Code","description":"Machine-readable response code, when provided."},"meta":{"additionalProperties":true,"type":"object","title":"Meta","description":"Additional metadata","default":{}},"data":{"items":{"$ref":"#/components/schemas/ProviderActionSummaryResponseV2"},"type":"array","title":"Data"},"offset":{"type":"integer","minimum":0,"title":"Offset","default":0},"limit":{"type":"integer","minimum":0,"title":"Limit","default":50},"total":{"type":"integer","minimum":0,"title":"Total","default":0}},"type":"object","title":"OffsetBasedPaginationResponse[ProviderActionSummaryResponseV2]"},"ProviderActionSummaryResponseV2":{"properties":{"action_id":{"type":"string","title":"Action Id"},"provider_id":{"type":"string","title":"Provider Id"},"name":{"type":"string","title":"Name"},"description":{"type":"string","title":"Description"},"tags":{"items":{"type":"string"},"type":"array","title":"Tags"},"deprecated":{"type":"boolean","title":"Deprecated","default":false},"deprecation_message":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Deprecation Message"}},"type":"object","required":["action_id","provider_id","name","description"],"title":"ProviderActionSummaryResponse","description":"A provider action's identity and metadata, without its input/output parameters.\n\nServes the actions-list endpoint. A catalog list is intentionally lean — identity and\nmetadata to scan and pick from, not the full resource — matching how iPaaS platforms expose\naction catalogs (browse the list, then fetch one action for its fields). Callers fetch a\nsingle action's detail (`ProviderActionResponseV2`) for its `input_parameters`/`output_parameters`."},"HTTPValidationError":{"properties":{"detail":{"items":{"$ref":"#/components/schemas/ValidationError"},"type":"array","title":"Detail"}},"type":"object","title":"HTTPValidationError"},"ValidationError":{"properties":{"loc":{"items":{"anyOf":[{"type":"string"},{"type":"integer"}]},"type":"array","title":"Location"},"msg":{"type":"string","title":"Message"},"type":{"type":"string","title":"Error Type"}},"type":"object","required":["loc","msg","type"],"title":"ValidationError"}}},"paths":{"/v2/providers/{provider_id}/actions":{"get":{"tags":["endpoint-listProviderActionsV2"],"summary":"List Provider Actions","description":"List a provider's actions; fetch a single action for its input/output schema.\n\n**How to use**\n\nChoose an action ID here, then fetch its detail before invoking it. List entries are for discovery and need not contain the full input/output contract.\n\n**Authentication and permissions**\n\nRequired permissions: `connections.read`. Resource and owner access checks also apply.","operationId":"listProviderActionsV2","parameters":[{"name":"provider_id","in":"path","required":true,"schema":{"type":"string","title":"Provider Id"}},{"name":"offset","in":"query","required":false,"schema":{"type":"integer","minimum":0,"description":"Number of items to skip","default":0,"title":"Offset"},"description":"Number of items to skip"},{"name":"limit","in":"query","required":false,"schema":{"type":"integer","maximum":100,"minimum":1,"description":"Number of items per page","default":50,"title":"Limit"},"description":"Number of items per page"}],"responses":{"200":{"description":"Successful Response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/OffsetBasedPaginationResponse_ProviderActionSummaryResponseV2_"}}}},"422":{"description":"Validation Error","content":{"application/json":{"schema":{"$ref":"#/components/schemas/HTTPValidationError"}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-api/rest-api-v2/providers-and-actions/get-v2-providers-provider_id-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
