Blinks are distributable experiences that can be embedded anywhere a link can exist. They represent a modern alternative to traditional SDKs, offering a streamlined, maintainable way to expose your services to the world.
As a blink provider, your backend is the engine that powers these experiences, delivering functionality to clients and integrations effortlessly.
The Blinks Provider ecosystem equips you with the tools and infrastructure to create, manage, and serve blinks from your backend, ensuring they’re reliable, scalable, and easy to distribute.
Think of your blink providers as hosted endpoints, that you provide for devs to easily integrate with your service using nothing but an URL.
Blink Providers are APIs that deliver signable transactions and messages.
Blink Clients determine if URLs conform to the Actions spec and introspect the underlying Blink Provider APIs to construct interfaces for them.
Blinks, or Blockchain Links, are hosted at URLs and are sharable with this URL. They are built from the following components:
actions.json
file, and embedding an Blink URL in an interstitial
site.GET
route that interacts with the Blink Provider. It can send a GET
request to the URL and receive a GET
response in return to present the client with human-readable information.POST
route that interacts with the Blink Provider. It can send a POST
request to the URL and get a response back to construct transactions, sign them, and submit them to the blockchain.Ready to dive in? Here are three paths to get you started!
Want to get started? Let’s build your first blink together! Follow our step-by-step tutorial to see it in action.
Not your first rodeo or need more complex solutions? Check out our guides section for in-depth examples and best practices.
Prefer to experiment on your own? Clone our starters and start building right away.