Actions

Actions are APIs that deliver signable transactions, and soon signable messages.

Blockchain links, or Blinks, are clients that determine if URLs conform to the Actions spec and introspect the underlying Actions APIs to construct interfaces for them.

Any client that fully introspects an Actions API to build a complete interface for it is a Blink. Therefore, there are all clients that consume Actions APIs are not Blinks.

Actions are hosted at URLs and are sharable with this URL. They are built from the following components:

1. A URL scheme for identifying Actions providers. There are three ways this can work--explicitly sharing an Action URL, sharing a link to a website with a properly-configured actions.json file, and embedding an Action URL in an 'interstitial' site. Find more here.

2. A GET route that interacts with the Action URL. It can send a GET request to the URL and receive a GET response in return to present the client with human-readable information.

3. A POST route that interacts with the Action URL. It can send a POST request to the URL and get a response back to construct transactions (and soon messages), sign them, and submit them to the blockchain.

This documentation covers:

• The Actions specification;

• How the specification relates to blinks;

• More practical guides on how to build actions;

• How to build blinks clients, whether natively into a web or mobile dApp, or via a Chrome extension for delivery on 3rd party sites like Twitter;

• Materials on Security and the Public Registry.

Let's get started.