Solana Actions and Blockchain Links (Blinks)

Read the docs to get started

Solana Actions are specification-compliant APIs that return transactions on the Solana blockchain to be previewed, signed, and sent across a number of various contexts, including QR codes, buttons + widgets, and websites across the internet. Actions make it simple for developers to integrate the things you can do throughout the Solana ecosystem right into your environment, allowing you to perform blockchain transactions without needing to navigate away to a different app or webpage.

Blockchain links – or blinks – turn any Solana Action into a shareable, metadata-rich link. Blinks allow Action-aware clients (browser extension wallets, bots) to display additional capabilities for the user. On a website, a blink might immediately trigger a transaction preview in a wallet without going to a decentralized app; in Discord, a bot might expand the blink into an interactive set of buttons. This pushes the ability to interact on-chain to any web surface capable of displaying a URL.

Simplified Type Definitions

The types and interfaces declared within this readme files are often the simplified version of the types to aid in readability.

For better type safety and improved developer experience, the @solana/actions-spec package contains more complex type definitions. You can find the source code for them here.

Contributing

If you would like to propose an update the Solana Actions specification, please publish a proposal on the official Solana forum under the Solana Request for Comments (sRFC) section: https://forum.solana.com/c/srfc/6

Specification

The Solana Actions specification consists of key sections that are part of a request/response interaction flow:

• Solana Action URL scheme providing an Action URL
• OPTIONS response to an Action URL to pass CORS requirements
• GET request to an Action URL
• GET response from the server
• POST request to an Action URL
• POST response from the server

Each of these requests are made by the Action client (e.g. wallet app, browser extension, dApp, website, etc) to gather specific metadata for rich user interfaces and to facilitate user input to the Actions API.

Each of the responses are crafted by an application (e.g. website, server backend, etc) and returned to the Action client. Ultimately, providing a signable transaction or message for a wallet to prompt the user to approve, sign, and send to the blockchain.

URL Scheme

A Solana Action URL describes an interactive request for a signable Solana transaction or message using the solana-action protocol.

The request is interactive because the parameters in the URL are used by a client to make a series of standardized HTTP requests to compose a signable transaction or message for the user to sign with their wallet.

1solana-action:<link>

• A single link field is required as the pathname. The value must be a conditionally URL-encoded absolute HTTPS URL.

• If the URL contains query parameters, it must be URL-encoded. URL-encoding the value prevents conflicting with any Actions protocol parameters, which may be added via the protocol specification.

• If the URL does not contain query parameters, it should not be URL-encoded. This produces a shorter URL and a less dense QR code.

In either case, clients must URL-decode the value. This has no effect if the value isn't URL-encoded. If the decoded value is not an absolute HTTPS URL, the wallet must reject it as malformed.

OPTIONS response

In order to allow Cross-Origin Resource Sharing (CORS) within Actions clients (including blinks), all Action endpoints should respond to HTTP requests for the OPTIONS method with valid headers that will allow clients to pass CORS checks for all subsequent requests from their same origin domain.

An Actions client may perform "preflight" requests to the Action URL endpoint in order check if the subsequent GET request to the Action URL will pass all CORS checks. These CORS preflight checks are made using the OPTIONS HTTP method and should respond with all required HTTP headers that will allow Action clients (like blinks) to properly make all subsequent requests from their origin domain.

At a minimum, the required HTTP headers include:

• Access-Control-Allow-Origin with a value of *
  • this ensures all Action clients can safely pass CORS checks in order to make all required requests
• Access-Control-Allow-Methods with a value of GET,POST,PUT,OPTIONS
  • ensures all required HTTP request methods are supported for Actions
• Access-Control-Allow-Headers with a minimum value of Content-Type, Authorization, Content-Encoding, Accept-Encoding

For simplicity, developers should consider returning the same response and headers to OPTIONS requests as their GET response.

The actions.json file response must also return valid Cross-Origin headers for GET and OPTIONS requests, specifically the Access-Control-Allow-Origin header value of *.

See actions.json below for more details.

GET Request

The Action client (e.g. wallet, browser extension, etc) should make an HTTP GET JSON request to the Action's URL endpoint.

• The request should not identify the wallet or the user.
• The client should make the request with an Accept-Encoding header.
• The client should display the domain of the URL as the request is being made.

GET Response

The Action's URL endpoint (e.g. application or server backend) should respond with an HTTP OK JSON response (with a valid payload in the body) or an appropriate HTTP error.

• The client must handle HTTP client errors, server errors, and redirect responses.

• The endpoint should respond with a Content-Encoding header for HTTP compression.

• The endpoint should respond with a Content-Type header of application/json.

• The client should not cache the response except as instructed by HTTP caching response headers.

• The client should display the title and render the icon image to user.

Error responses (i.e. HTTP 4xx and 5xx status codes) should return a JSON response body following ActionError to present a helpful error message to users. See Action Errors.

GET Response Body

A GET response with an HTTP OK JSON response should include a body payload that follows the interface specification:

1export type ActionType = "action" | "completed";
2
3export type ActionGetResponse = Action<"action">;
4
5export interface Action<T extends ActionType = "action"> {
6  /** type of Action to present to the user */
7  type: T;
8  /** image url that represents the source of the action request */
9  icon: string;
10  /** describes the source of the action request */
11  title: string;
12  /** brief summary of the action to be performed */
13  description: string;
14  /** button text rendered to the user */
15  label: string;
16  /** UI state for the button being rendered to the user */
17  disabled?: boolean;
18  links?: {
19    /** list of related Actions a user could perform */
20    actions: LinkedAction[];
21  };
22  /** non-fatal error message to be displayed to the user */
23  error?: ActionError;
24}

• type - The type of action being given to the user. Defaults to action. The initial ActionGetResponse is required to have a type of action.

  • action - Standard action that will allow the user to interact with any of the LinkedActions
  • completed - Used to declare the "completed" state within action chaining.

• icon - The value must be an absolute HTTP or HTTPS URL of an icon image. The file must be an SVG, PNG, or WebP image, or the client/wallet must reject it as malformed.

• title - The value must be a UTF-8 string that represents the source of the action request. For example, this might be the name of a brand, store, application, or person making the request.

• description - The value must be a UTF-8 string that provides information on the action. The description should be displayed to the user.

• label - The value must be a UTF-8 string that will be rendered on a button for the user to click. All labels should not exceed 5 word phrases and should start with a verb to solidify the action you want the user to take. For example, "Mint NFT", "Vote Yes", or "Stake 1 SOL".

• disabled - The value must be boolean to represent the disabled state of the rendered button (which displays the label string). If no value is provided, disabled should default to false (i.e. enabled by default). For example, if the action endpoint is for a governance vote that has closed, set disabled=true and the label could be "Vote Closed".

• error - An optional error indication for non-fatal errors. If present, the client should display it to the user. If set, it should not prevent the client from interpreting the action or displaying it to the user (see Action Errors). For example, the error can be used together with disabled to display a reason like business constraints, authorization, the state, or an error of external resource.

• links.actions - An optional array of related actions for the endpoint. Users should be displayed UI for each of the listed actions and expected to only perform one. For example, a governance vote action endpoint may return three options for the user: "Vote Yes", "Vote No", and "Abstain from Vote".

  • If no links.actions is provided, the client should render a single button using the root label string and make the POST request to the same action URL endpoint as the initial GET request.

  • If any links.actions are provided, the client should only render buttons and input fields based on the items listed in the links.actions field. The client should not render a button for the contents of the root label.

1export type LinkedActionType =
2  | "transaction"
3  | "message"
4  | "post"
5  | "external-link";
6
7export interface LinkedAction {
8  /** Type of action to be performed by user */
9  type: LinkedActionType;
10  /** URL endpoint for an action */
11  href: string;
12  /** button text rendered to the user */
13  label: string;
14  /**
15   * Parameters to accept user input within an action
16   * @see {ActionParameter}
17   * @see {ActionParameterSelectable}
18   */
19  parameters?: Array<TypedActionParameter>;
20}

• type - the type of action that will be performed by the user

  • transaction - This tells blink client that the action endpoint will return a transaction type response.
  • message - This tells blink client that the action endpoint will return a sign message type response.
  • post - This tells blink client, that the action endpoint will not return a transaction object.
  • external-link - This tells blink client, that the action endpoint will return an external link to allow the user to click and navigate to.

The ActionParameter allows declaring what input the Action API is requesting from the user:

1/**
2 * Parameter to accept user input within an action
3 * note: for ease of reading, this is a simplified type of the actual
4 */
5export interface ActionParameter {
6  /** input field type */
7  type?: ActionParameterType;
8  /** parameter name in url */
9  name: string;
10  /** placeholder text for the user input field */
11  label?: string;
12  /** declare if this field is required (defaults to `false`) */
13  required?: boolean;
14  /** regular expression pattern to validate user input client side */
15  pattern?: string;
16  /** human-readable description of the `type` and/or `pattern`, represents a caption and error, if value doesn't match */
17  patternDescription?: string;
18  /** the minimum value allowed based on the `type` */
19  min?: string | number;
20  /** the maximum value allowed based on the `type` */
21  max?: string | number;
22}

The pattern should be a string equivalent of a valid regular expression. This regular expression pattern should by used by blink-clients to validate user input before before making the POST request. If the pattern is not a valid regular expression, it should be ignored by clients.

The patternDescription is a human readable description of the expected input requests from the user. If pattern is provided, the patternDescription is required to be provided.

The min and max values allows the input to set a lower and/or upper bounds of the input requested from the user (i.e. min/max number and or min/max character length), and should be used for client side validation. For input types of date or datetime-local, these values should be a string dates. For other string based input types, the values should be numbers representing their min/max character length.

If the user input value is not considered valid per the pattern, the user should receive a client side error message indicating the input field is not valid and displayed the patternDescription string.

The type field allows the Action API to declare more specific user input fields, providing better client side validation and improving the user experience. In many cases, this type will resemble the standard HTML input element.

The ActionParameterType can be simplified to the following type:

1/**
2 * Input field type to present to the user
3 * @default `text`
4 */
5export type ActionParameterType =
6  | "text"
7  | "email"
8  | "url"
9  | "number"
10  | "date"
11  | "datetime-local"
12  | "checkbox"
13  | "radio"
14  | "textarea"
15  | "select";

Each of the type values should normally result in a user input field that resembles a standard HTML input element of the corresponding type (i.e. <input type="email" />) to provide better client side validation and user experience:

• text - equivalent of HTML “text” input element
• email - equivalent of HTML “email” input element
• url - equivalent of HTML “url” input element
• number - equivalent of HTML “number” input element
• date - equivalent of HTML “date” input element
• datetime-local - equivalent of HTML “datetime-local” input element
• checkbox - equivalent to a grouping of standard HTML “checkbox” input elements. The Action API should return options as detailed below. The user should be able to select multiple of the provided checkbox options.
• radio - equivalent to a grouping of standard HTML “radio” input elements. The Action API should return options as detailed below. The user should be able to select only one of the provided radio options.
• Other HTML input type equivalents not specified above (hidden, button, submit, file, etc) are not supported at this time.

In addition to the elements resembling HTML input types above, the following user input elements are also supported:

• textarea - equivalent of HTML textarea element. Allowing the user provide multi-line input.
• select - equivalent of HTML select element, allowing the user to experience a “dropdown” style field. The Action API should return options as detailed below.

When type is set as select, checkbox, or radio then the Action API should include an array of options that each provide a label and value at a minimum. Each option may also have a selected value to inform the blink-client which of the options should be selected by default for the user (see checkbox and radio for differences).

This ActionParameterSelectable can be simplified to the following type definition:

1/**
2 * note: for ease of reading, this is a simplified type of the actual
3 */
4interface ActionParameterSelectable extends ActionParameter {
5  options: Array<{
6    /** displayed UI label of this selectable option */
7    label: string;
8    /** value of this selectable option */
9    value: string;
10    /** whether or not this option should be selected by default */
11    selected?: boolean;
12  }>;
13}

If no type is set or an unknown/unsupported value is set, blink-client should default to text and render a simple text input.

The Action API is still responsible to validate and sanitize all data from the user input parameters, enforcing any “required” user input as necessary.

For platforms other that HTML/web based ones (like native mobile), the equivalent native user input component should be used to achieve the equivalent experience and client side validation as the HTML/web input types described above.

POST Request

The client must make an HTTP POST JSON request to the action URL with a body payload of:

1{
2  "account": "<account>"
3}

• account - The value must be the base58-encoded public key of an account that may sign the transaction.

The client should make the request with an Accept-Encoding header and the application may respond with a Content-Encoding header for HTTP compression.

The client should display the domain of the action URL as the request is being made. If a GET request was made, the client should also display the title and render the icon image from that GET response.

POST Response

The Action's POST endpoint should respond with an HTTP OK JSON response (with a valid payload in the body) or an appropriate HTTP error.

• The client must handle HTTP client errors, server errors, and redirect responses.
• The endpoint should respond with a Content-Type header of application/json.

Error responses (i.e. HTTP 4xx and 5xx status codes) should return a JSON response body following ActionError to present a helpful error message to users. See Action Errors.

POST Response Body

A POST response with an HTTP OK JSON response should include a body payload of:

1/**
2 * Response body payload returned from the Action POST Request
3 */
4
5export type PostActionType = LinkedActionType;
6
7/**
8 * Generic response from an Action API request
9 */
10export interface ActionResponse {
11  type?: PostActionType;
12  message?: string;
13  links?: {
14    next: NextActionLink;
15  };
16}
17
18/**
19 * Response body payload returned from the Action POST Request if the action is a transaction
20 */
21export interface TransactionResponse extends ActionResponse {
22  type?: Extract<PostActionType, "transaction">;
23  transaction: string;
24}
25
26/**
27 * Response body payload returned from the Action POST Request if the action is a POST request
28 */
29export interface PostResponse extends ActionResponse {
30  type: Extract<PostActionType, "post">;
31}
32
33/**
34 * Response body payload returned from the Action POST Request if the action is an External Link
35 */
36export interface ExternalLinkResponse extends ActionResponse {
37  type: Extract<PostActionType, "external-link">;
38  externalLink: string;
39}
40
41export interface SignMessageResponse extends ActionResponse {
42  type: Extract<PostActionType, "message">;
43  // See Message Signing for more details
44}
45
46/**
47 * Response body payload returned from the Action POST Request
48 */
49export type ActionPostResponse =
50  | TransactionResponse
51  | SignMessageResponse
52  | PostResponse
53  | ExternalLinkResponse;

• type - If this is of type

  • transaction then client will pop-up the user to sign the transaction and then after confirmation render links.next.
  • post then client will skip the pop-up and render the links.next.

• transaction - The value must be a base64-encoded serialized transaction. The client must base64-decode the transaction and deserialize it.

• message - The value must be a UTF-8 string that describes the nature of the transaction included in the response. The client should display this value to the user. For example, this might be the name of an item being purchased, a discount applied to a purchase, or a thank you note.

• links.next - An optional value use to "chain" multiple Actions together in series. After the included transaction has been confirmed on-chain, the client can fetch and render the next action. See Action Chaining for more details.

• The client and application should allow additional fields in the request body and response body, which may be added by future specification updates.

The application may respond with a partially or fully signed transaction. The client and wallet must validate the transaction as untrusted.

POST Response - Transaction

If the transaction signatures are empty or the transaction has NOT been partially signed:

• The client must ignore the feePayer in the transaction and set the feePayer to the account in the request.
• The client must ignore the recentBlockhash in the transaction and set the recentBlockhash to the latest blockhash.
• The client must serialize and deserialize the transaction before signing it. This ensures consistent ordering of the account keys, as a workaround for this issue.

If the transaction has been partially signed:

• The client must NOT alter the feePayer or recentBlockhash as this would invalidate any existing signatures.
• The client must verify existing signatures, and if any are invalid, the client must reject the transaction as malformed.

The client must only sign the transaction with the account in the request, and must do so only if a signature for the account in the request is expected.

If any signature except a signature for the account in the request is expected, the client must reject the transaction as malicious.

Action Chaining

Solana Actions can be "chained" together in a successive series. After an Action is completed (i.e. message signed or transaction confirmed on-chain), the next action can be obtained and presented to the user.

Action chaining allows developers to build more complex and dynamic experiences within blinks, including:

• providing multiple transactions to a user
• ask the user to sign a message (i.e. authentication message)
• customized action metadata based on the user's wallet address
• refreshing the blink metadata after a successful transaction
• receive an API callback with the transaction signature for additional validation and logic on the Action API server
• customized "success" messages by updating the displayed metadata (e.g. a new image and description)

To chain multiple actions together, in any ActionPostResponse include a links.next of either:

• PostNextActionLink - POST request link with a same origin callback url to receive the signature and user's account in the body. This callback url should respond with a NextAction.
• InlineNextActionLink - Inline metadata for the next action to be presented to the user immediately after the transaction has confirmed. No callback will be made.

1export type NextActionLink = PostNextActionLink | InlineNextActionLink;
2
3/** @see {NextActionPostRequest} */
4export interface PostNextActionLink {
5  /** Indicates the type of the link. */
6  type: "post";
7  /** Relative or same origin URL to which the POST request should be made. */
8  href: string;
9}
10
11/**
12 * Represents an inline next action embedded within the current context.
13 */
14export interface InlineNextActionLink {
15  /** Indicates the type of the link. */
16  type: "inline";
17  /** The next action to be performed */
18  action: NextAction;
19}

NextAction

After the ActionPostResponse included transaction is signed by the user and confirmed on-chain, the blink client should either:

• execute the callback request to fetch and display the NextAction, or
• if a NextAction is already provided via links.next, the blink client should update the displayed metadata and make no callback request

If the callback url is not the same origin as the initial POST request, no callback request should be made. Blink clients should display an error notifying the user.

1/** The next action to be performed */
2export type NextAction = Action<"action"> | CompletedAction;
3
4/** The completed action, used to declare the "completed" state within action chaining. */
5export type CompletedAction = Omit<Action<"completed">, "links">;

Based on the type, the next action should be presented to the user via blink clients in one of the following ways:

• action - (default) A standard action that will allow the user to see the included Action metadata, interact with the provided LinkedActions, and continue to chain any following actions.

• completed - The terminal state of an action chain that can update the blink UI with the included Action metadata, but will not allow the user to execute further actions.

If no links.next is not provided, blink clients should assume the current action is final action in the chain, presenting their "completed" UI state after the transaction is confirmed.

Message Signing

Message singing allows verifying a user's wallet account address by the user cryptographically signing a plaintext message via their wallet to create a signature that can be later verified by the Action API. This is commonly used to provide no-cost authentication functionality while still being able to verify they control the account address in question.

To prompt a user to sign a plaintext authentication message with their wallet, the Action API should return a SignMessageResponse for the POST response:

1export interface SignMessageResponse extends ActionResponse {
2  type: "message";
3  /** data for the user to sign */
4  data: string | SignMessageData;
5  /**
6   * normally a [Message Authentication Code](https://en.wikipedia.org/wiki/Message_authentication_code) (MAC)
7   * or JWT created using a secret stored on the Action API server (allowing the server to verify this value)
8   */
9  state?: string;
10  /** `links.next` is required for sign message to validate the signature created */
11  links: {
12    next: PostNextActionLink;
13  };
14}

The state should be a utf-8 string used by the API server to aid in validation of the data, such as a MAC created by the Action API server using a secret stored on that server. This enables API servers to cryptographically verify that the initial sign message request came from their server by generating a HMAC on their server. It also enabled it so they are not required to maintain server state of which messages their API requested users sign.

The state value should NOT be modified by the client, but simply relayed back to the API server in the body of the POST request (along side the signature).

1/**
2 * Structured data that the user was requested to sign
3 */
4export type SignMessageData = {
5  /** domain requesting the user to sign the message */
6  domain: string;
7  /** base58 string of the Solana address requested to sign this message */
8  address: string;
9  /** human readable string message to the user */
10  statement: string;
11  /**
12   * a random alpha-numeric string at least 8 characters. this value is
13   * generated by the Action API, should only be used once, and is used
14   *  to prevent replay attacks
15   */
16  nonce: string;
17  /** ISO-8601 datetime string. This represents the time at which the sign request was issued by the action api. */
18  issuedAt: string;
19  /**
20   * Chain ID compatible with CAIPs, defaults to Solana mainnet-beta in clients.
21   * If not provided, the blink client should not include chain id in the message to be signed by the user.
22   */
23  chainId?: string;
24};

When received by the blink client, the user should be shown the plaintext data value and prompted to sign it with their wallet to generate a signature.

The data can be a plaintext string or a structured SignMessageData object.

When using SignMessageData, it must be formatted as a standardized, human-readable plaintext suitable for signing. Both the client and server must generate the message using the same method to ensure proper verification. The following template must be used by both the Action API and the client to format SignMessageData:

${domain} wants you to sign a message with your account:
${address}

${statement}

Chain ID: ${chainId}
Nonce: ${nonce}
Issued At: ${issuedAt}

If chainId is not provided, the Chain ID line should be omitted from the message to be signed.

Client should not prefix, suffix or otherwise modify the SignMessageData value before signing it. Client should perform validation on the SignMessageData before signing to ensure that it meets expected criteria and to prevent potential security issues.

The following function illustrates how to create a human-readable message text from SignMessageData:

1export function createSignMessageText(input: SignMessageData): string {
2  let message = `${input.domain} wants you to sign a message with your account:\n`;
3  message += `${input.address}`;
4  message += `\n\n${input.statement}`;
5  const fields: string[] = [];
6
7  if (input.chainId) {
8    fields.push(`Chain ID: ${input.chainId}`);
9  }
10  fields.push(`Nonce: ${input.nonce}`);
11  fields.push(`Issued At: ${input.issuedAt}`);
12  message += `\n\n${fields.join("\n")}`;
13
14  return message;
15}

After signing, the blink client will continue the chain-of-actions by making a POST request to the provided PostNextActionLink endpoint with a payload of MessageNextActionPostRequest. This payload is similar to the normal ActionPostRequest fields (see Action Chaining), but with the following modifications:

• signature (required) - the signature created by the account singing the data (as a base58 encoded string)
• data (required) - the same unmodified data value the Action api initially provided, relayed back from the client.
• state (optional) - the same unmodified state value the Action api initially provided, relayed back from the client.

Action Errors

Actions APIs should return errors using ActionError in order to present helpful error messages to the user. Depending on the context, this error could be fatal or non-fatal.

1export interface ActionError {
2  /** simple error message to be displayed to the user */
3  message: string;
4}

When an Actions API responds with an HTTP error status code (i.e. 4xx and 5xx), the response body should be a JSON payload following ActionError. The error is considered fatal and the included message should be presented to the user.

For API responses that support the optional error attribute (like ActionGetResponse), the error is considered non-fatal and the included message should be presented to the user.

actions.json

The purpose of the actions.json file allows an application to instruct clients on what website URLs support Solana Actions and provide a mapping that can be used to perform GET requests to an Actions API server.

The actions.json file response must also return valid Cross-Origin headers for GET and OPTIONS requests, specifically the Access-Control-Allow-Origin header value of *.

See OPTIONS response above for more details.

The actions.json file should be stored and universally accessible at the root of the domain.

For example, if your web application is deployed to my-site.com then the actions.json file should be accessible at https://my-site.com/actions.json. This file should also be Cross-Origin accessible via any browser by having a Access-Control-Allow-Origin header value of *.

Rules

The rules field allows the application to map a set of a website's relative route paths to a set of other paths.

Type: Array of ActionRuleObject.

1interface ActionRuleObject {
2  /** relative (preferred) or absolute path to perform the rule mapping from */
3  pathPattern: string;
4  /** relative (preferred) or absolute path that supports Action requests */
5  apiPath: string;
6}

• pathPattern - A pattern that matches each incoming pathname.

• apiPath - A location destination defined as an absolute pathname or external URL.

Rules - pathPattern

A pattern that matches each incoming pathname. It can be an absolute or relative path and supports the following formats:

• Exact Match: Matches the exact URL path.

  • Example: /exact-path
  • Example: https://website.com/exact-path

• Wildcard Match: Uses wildcards to match any sequence of characters in the URL path. This can match single (using *) or multiple segments (using **). (see Path Matching below).

  • Example: /trade/* will match /trade/123 and /trade/abc, capturing only the first segment after /trade/.
  • Example: /category/*/item/** will match /category/123/item/456 and /category/abc/item/def.
  • Example: /api/actions/trade/*/confirm will match /api/actions/trade/123/confirm.

Rules - apiPath

The destination path for the action request. It can be defined as an absolute pathname or an external URL.

• Example: /api/exact-path
• Example: https://api.example.com/v1/donate/*
• Example: /api/category/*/item/*
• Example: /api/swap/**

Rules - Query Parameters

Query parameters from the original URL are always preserved and appended to the mapped URL.

Rules - Path Matching

The following table outlines the syntax for path matching patterns:

Operator	Matches
*	A single path segment, not including the surrounding path separator / characters.
**	Matches zero or more characters, including any path separator / characters between multiple path segments. If other operators are included, the ** operator must be the last operator.
?	Unsupported pattern.

License

The Solana Actions JavaScript SDK is open source and available under the Apache License, Version 2.0. See the LICENSE file for more info.