API
This section contains the JSON-RPC API technical documentation for Dogecoin wallets.
info
Click here to learn how to authenticate and send JSON-RPC requests.
Endpoint
The JSON-RPC API is exposed at https://api.coinrpc.com/dogecoin
.
Transaction Object
Below describes a transaction object
returned by some API methods.
amount
: (string) The amount of tokens transacted.block_number
: (int) The number of the block containing the transaction.null
when transaction is not yet in a block.category
: (string) The type of transaction.SEND
orRECEIVE
.comment
: (string) Optional comment only visible to the wallet owner.confirmed_at
: (int) The unix timestamp of when the transaction was confirmed by the platform.null
when status isPENDING
.created_at
: (int) The unix timestamp of when the transaction was first seen by the platform.currency
: (string) Thecurrency_id
of tokens transacted.guid
: (string) The unique transaction ID on the platform.network_fee
: (string) The network fee paid for the transaction. Paid in DOGE.recipient
: (string) The address of the receipient.service_fee
: (string) The service fee paid for the transaction. Paid incurrency
. IfSEND
, the service fee is paid in addition to theamount
. IfRECEIVE
, the service fee is paid from theamount
.status
: (string) The status of the transaction.PENDING
,SUCCESS
orFAILED
.tx_hash
: (string) The transaction hash on the blockchain.
{
"amount": "1",
"block_number": 2778168,
"category": "RECEIVE",
"comment": "my transaction",
"confirmed_at": 1698953511,
"created_at": 1698953511,
"currency": "DOGE",
"guid": "ABCD1234ABCD",
"network_fee": "0.0000165",
"recipient": "DFTk7F6ujZ5Tpq7hNCvYwgJboA5MMsrytc",
"service_fee": "0",
"status": "SUCCESS",
"tx_hash": "9f54f3268ef2a741867ae155d1e8dc6c9480c167b5007699a6218b9f0c0f43d9",
}