BLOG
This is the most straightforward guide available. The first part consists of defining API and related concepts, including what keys are. The second part introduces the Blink API and lets everyone know what they can do with it and how.
At the heart of today’s app ecosystem, APIs connect it all. The acronym stands for Application Programming Interface and that interface connects two computers. At one end of the proverbial wire, there’s a client, at the other, there’s a server. Using the API as an intermediary, the client asks for files or resources, and the server provides them.
For a metaphor, let’s consult the open-source experts at Red Hat:
“APIs are sometimes thought of as contracts, with documentation that represents an agreement between parties: If party 1 sends a remote request structured a particular way, this is how party 2’s software will respond.”
That’s the gist of it.
Using that simple architecture, coders perform miracles.
However, why should companies and developers use APIs in the first place?
Using APIs maintains order, control, and security. Also, APIs connect diverse clients through a protocol and solve problems simply, enhancing user experience.
Let’s go back to Red Hat for another way of looking at the situation:
“APIs are a simplified way to connect your own infrastructure through cloud-native app development, but they also allow you to share your data with customers and other external users.”
Companies use external APIs to connect to an ecosystem and go beyond what their internal group of developers can do. Implementing other people’s APIs requires minimal technical knowledge; they simplify complex tasks and automatically receive maintenance and enhancements as a bonus.
For their part, companies that create APIs expect their contribution to motivate coders to play in their sandboxes and develop apps that connect to their technology. If their ecosystem grows, the company benefits in many ways.
It’s a win/ win situation.
Every technological development generates slang, a new set of words and terms necessary to explain certain aspects of it. We’ll enlist Amazon to help us define some API-related terms:
Bitcoiners worldwide are extremely familiar with keys. The network uses them to guarantee security. Some APIs use similar technology to authenticate users' and clients’ authorization to contact servers. Since keys are unique to each client, they are also useful for monitoring their usage and habits.
Authentication tokens are an alternative to keys and perform a similar function.
The Blink API, however, uses keys.
At its core, the Blink API is a payment gateway. It “enables any bitcoin business that wants to add bitcoin as a payment method without developing its own bitcoin and lightning infrastructure.” Besides instant global payments, the API’s differentiating characteristic is pairing Bitcoin’s power with US$-denominated stablesats, Blink’s own lightning-network-powered synthetic dollar. Using them in tandem with Bitcoin can help businesses navigate volatility and keep accounting simple.
Another great advantage? Integrate the Blink API and get the lowest fees on the market:
“Robust infrastructure (built on Galoy) and well-managed Lightning channels allow us to provide the lowest possible fees, whether for Lightning (LN) payments, onchain bitcoin transactions, or BTC to Stablesats conversions.”
Companies, reduce friction by joining financial app Bringin and these ATM brands in letting your users transact seamlessly in Bitcoin and stablesats. To take it one step further, use the Blink plugin to connect to the BTCPay Server and avoid setting up a Lightning node.
Another cool characteristic of the Blink plugin is that it was “developed through a community-driven bounty, this is a prime example of what we achieve together in the open-source bitcoin world.”
The process couldn’t be simpler:
1.- Log in to the Blink API Dashboard using your Blink Wallet’s credentials. You don’t need a password, the system will send a code to your phone or email.
2.- Create an API Key with the desired parameters.
3.- Connect to plugins, your system, or whatever is compatible. Here are some use cases to play with.
That’s it on our end. We told you it was simple. Now, it’s your turn to create something wonderful.
