Getting Started
The Rust Crate for ZBD API is available under zebedee-rust
. When building tools with ZBD support we encourage you to include zbd
in the keywords
field in Cargo.toml
.
All you have to do to get started is add zebedee-rust
as a dependency to your Rust-based project. You can do so using cargo
:
cargo add zebedee_rust
Now let's authenticate a specific Wallet with that ZBD Project's API Key.
Authentication
In order to authenticate your Project Wallet with the ZBD API, you will need to provide your ZBD Project's API Key to the zebedee-rust
crate. You can find your Project API Key in the ZBD Developer Dashboard.
First you must import the zebedee-rust
crate client into your codebase, and then instantiate it with your Project API Key (replace `YOUR_API_KEY_HERE` below with your actual ZBD Project's API Key).
use zebedee_rust::{ZebedeeClient};
let zbd_client = ZebedeeClient::new()
.apikey(YOUR_API_KEY_HERE)
.build();
let payment = GamertagPayment{...};
let payment_res = zbd_client.pay_gamertag(&payment).await.unwrap();
You're all set. Now let's move some money at the speed of the internet! Check the SDK API Reference below for more information on how to use the zebedee-rust
crate.
zebedee-rust
The goal of the project is to create a beautiful and extensible experience for developers using ZBD APIs in a Rust environment. The ZBD community has taken on the challenge and built the Rust SDK themselves. The focus is to provide parity with ZBD REST API, as well as providing further stability for developers.
API Reference
Below is a comprehensive list of the methods and functions available in the zebedee-rust
crate. These methods are ONLY available to the ZebedeeClient
client instance after it's been properly authenticated with a Project's API Key.
Method | Entity | Description | |||||||||||||
create_charge | Charge | Creates a new Charge / Payment Request in the Bitcoin Lightning Network, payable by any Bitcoin Lightning wallet. Struct:
Parameters:
Resources:
| |||||||||||||
get_charge | Charge | Retrieves all information relating to a specific Charge / Payment Request. Parameters:
Resources:
| |||||||||||||
create_withdrawal_request | Withdrawal Request | A Withdrawal Request is a QR code that allows someone to scan and receive Bitcoin (e.g. Withdrawals). Struct:
Parameters:
Resources:
| |||||||||||||
get_withdrawal_request | Withdrawal Request | Retrieves details about a specific Withdrawal Request. Parameters:
Resources:
| |||||||||||||
pay_ln_address | Lightning Address | Send Bitcoin payments directly to a Lightning Address. A Lightning Address is an internet identifier (akin to an email address -- andre@zbd.gg) that anyone can send Bitcoin Lightning Network payments to. Struct:
Parameters:
Resources:
| |||||||||||||
validate_ln_address | Lightning Address | Not all internet identifiers are Lightning Addresses / compatible with the Lightning Address protocol. Use this endpoint in order to validate whether a user's entered Lightning Address is valid. Parameters:
Resources:
| |||||||||||||
fetch_charge_ln_address | Lightning Address | Generates a Bitcoin Lightning Charge / Payment Request for a given Lightning Address destination. Depending on your system's configuration or your product's UX, you may need the ability to generate Charges for specific users using a different provider than ZBD. Struct:
Parameters:
Resources:
| |||||||||||||
get_wallet_details | Wallet | Retrieves the total balance of a given Project Wallet. Resources:
| |||||||||||||
internal_transfer | Wallet | Initiates a transfer of funds between two Project Wallets you own. Struct:
Parameters:
Resources:
| |||||||||||||
keysend | Keysend | This endpoint exposes the ability to make payment directly to a Lightning Network node Public Key, without the need for a Payment Request / Charge. Struct:
Parameters:
Resources:
| |||||||||||||
pay_invoice | Payment | Pays a Charge / Payment Request in the Bitcoin Lightning Network. Struct:
Parameters:
Resources:
| |||||||||||||
get_payment | Payment | Retrieves all the information related to a specific Payment. Parameters:
Resources:
| |||||||||||||
pay_gamertag | ZBD Gamertag | This API endpoint is used to send Bitcoin payments directly to a user's ZBD Gamertag. Struct:
Parameters:
Resources:
| |||||||||||||
get_gamertag_tx | ZBD Gamertag | Get a given ZBD Gamertag when provided with a ZBD User's ID. Parameters:
Resources:
| |||||||||||||
get_userid_by_gamertag | ZBD Gamertag | Get a given ZBD User's ID when provided with a ZBD Gamertag. Parameters:
Resources:
| |||||||||||||
get_gamertag_by_userid | ZBD Gamertag | Invoked when the app first loads. If a plugin reloads, it's invoked again with the existing app. Parameters:
Resources:
| |||||||||||||
get_is_supported_region_by_ip | Utility | If you wish to know whether the incoming user request is coming from a region/country where ZBD is supported or not, you can use this simple API endpoint and pass the target IP address as a parameter. Parameters:
Resources:
| |||||||||||||
get_prod_ips | Utility | The ZBD API relies on callback URLs for keeping you informed about updates that occur to any Charges, Payments, or Withdrawals you've created. In order to ensure that any incoming callback message is indeed from a trusted ZBD API infrastructure server, we provide this API endpoint for you to know which IP addresses real requests come from. Resources:
| |||||||||||||
get_btc_usd | Utility | Get the latest price for Bitcoin in US Dollars. The exchange rate feed is refreshed every 5 seconds and is based upon a combination of industry-leading partner exchange providers's price feeds. Resources:
|
Community Support
Feature Request? Bugfix? Recommendations? We're all ears! Head on over to the zebedee-rust Issues page and submit one. We also welcome Pull Requests and other contributions to the library.