# sRFC 26: Multi-Actions (Solana Actions v2) **URL:** \ **Category:** sRFC\ **Created:** [June 25, 2024, 1:12pm UTC](https://forum.solana.com/t/srfc-26-multi-actions-solana-actions-v2/1720 "2024-06-25T13:12:48Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![jnwng](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.solana.com/jnwng/32/147_2.png) [@jnwng](https://forum.solana.com/u/jnwng)\ **Post date:** [June 25, 2024, 1:12pm UTC](https://forum.solana.com/t/srfc-26-multi-actions-solana-actions-v2/1720/1 "2024-06-25T13:12:48Z")
**Authors** : nick@dialect.to, alexey@dialect.to The Multi-Action Specification (MAS) is a extension of [sRFC 25: Solana Actions](https://forum.solana.com/t/srfc-25-solana-actions-v1/1719) and retains interoperability (but not strict backwards-compatibility). See detailed specification [here](https://solana.com/docs/advanced/actions#get-response-body). Two notable differences: 1. The metadata returned from `GET https://example-action-endpoint.xyz` may include more than just `label` and `icon`, and may include more informational data (e.g., `title`, `description`) as well as a set of up to four linked Action endpoints. 1. Linked Actions introduces the concept of an input with dynamic input. An Action with dynamic input cannot be the first Action as backwards-compatibility with the v1 Actions Spec does not allow input. Actions with dynamic input receive additional parameters in the body of the `POST` request alongside the `account` public key. 2. All linked Actions themselves respect the v1 Solana Actions specification, and can individually respond to the `GET` / `POST` flow, with the exception of Actions with dynamic input. 2. The transaction returned from `POST https://example-action-endpoint.xyz` will always be the first of the set of linked Actions from the metadata retrieval step. ## Rationale Allowing the return of additional metadata + multiple Actions allows for more expressive, Action-driven interfaces to be built.