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, & 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, not all clients that consume Actions APIs are Blinks.

Actions are hosted at URLs, and are therefore sharable by their URL.

Actions are comprised of URL scheme, a GET route, and a POST route to the Action Provider:

1. A URL scheme for identifying Actions Providers

2. A GET request and response, to and from, an action URL, for presenting the client with human-readable information.

3. A POST request and response, to and from an action URL, for constructing transactions (and soon messages) for signing and submission to the blockchain.

This documentation covers:

• the Actions specification,

• how the specification relates to blinks, as well as

• more practical guides on how to build actions and

• 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, and

• materials on Security and the Public Registry.

Let's get started.