Dogecoin API and its usage

February 14, 2020

Crypto APIs supports Dogecoin API among the rest of blockchain protocols. Firstly founded in 2013, Dogecoin emerged as a fork of Litecoin. It was initially seen as a community venture, which could be used in micro transactions in order to tip people and content on Reddit or Twitter. Particularly for the fan base, the coin soon became to represent a tone of appreciation for entertainment, rather than necessarily getting richer.

It has experienced flunctuations throughout the years, and at the moment of writing this, the Dogecoin is valued $0.003152 with a 24-hour trading volume of $ 75.39M across 70 exchanges.

Crypto APIs provides endpoints similar to Bitcoin API and Bitcoin Cash API related to: general information, addresses, transactions, wallets, payment forwarding and webhook notifications.

Dogecoin API – Addresses Endpoint

Based on Dogecoin as a resource for the address endpoint, Dogecoin API allows you to look up information on, for example:

public addresses on the blockchain

generate single-use, low-value key pairs with corresponding addresses

help generate multisig addresses

collect multiple addresses into a single shortcut for address viewing

Get address details

Through ECDSA in Dogecoin, the user can generate a public address and then use that as one of the query parameters for the GET request:

/v1/bc/doge/${NETWORK}/address/${ADDRESS}

Eventually, the returned object contains information about the address, including its balance in Dogecoins and the number of transactions that associate with it.

Dogecoin API – Wallets Endpoint

Similarly, Dogecoin API can leverage the usage of both HD Wallets and normal Wallets, just by using their $NAME instead of $ADDRESS. However, the results in this case show serially; that is to say, the results will appear as if each API call were done sequentially.

Create Wallet

Moreover, this endpoint allows the user to create a new wallet. POSTing a partially filled out Wallet or HDWallet object, depending on the endpoint, for instance:

Normal wallet – the user must include WALLET_NAME attribute and at least one public address in the ADDRESSES array

POST /v1/bc/doge/${NETWORK}/wallets

HD wallet – the user must include WALLET_NAME, the ADDRESS_COUNT and the PASSWORD attributes

POST /v1/bc/doge/${NETWORK}/wallets/hd

Dogecoin API – Transactions Endpoint

Refund Transaction

The Refund Transaction Endpoint allows users to easily return the amount in doge they have received from an unknown source. Only two fields are required: the txid of the transcation and the wif of the recipient address. Additionally, there is an optional field fee. If the user doesn’t set the fee field, the system will set the recommended fee from the Transaction Fee Endpoint.

POST /v1/bc/doge/${NETWORK}/txs/refund

Finally, these show a few examples of how endpoints help in integrating the Dogecoin API into your website

Read more on our docs here.