Kaspa API

Kaspa is a scalable proof-of-work blockchain using GHOSTDAG for fast transactions and instant confirmations. Its blockDAG architecture improves efficiency, speed, and decentralization, ideal for high-throughput applications.

Networks Mainnet
Released 2021
Consensus Proof of work (PoW)
Smart contracts Yes
Block time 1 second
Smart contract language(s) supported GoLang, Rust
Get started with Kaspa

Bitcoin
Ethereum
XRP Ledger
Ethereum Classic
Bitcoin Cash
Dash
Litecoin
Dogecoin
Zcash
View all supported

The Kaspa API — build without running a node

Access Kaspa blockchain data through one unified REST API: transaction and address data, balances, block data, and real-time webhooks for on-chain events — with no Kaspa node to run and maintain. Start free and scale as you grow.

Blockchain data

Read Kaspa transactions, addresses, balances, UTXOs, and block data through one REST API.

Real-time webhooks

Subscribe to on-chain events — incoming and outgoing transactions, confirmations, and mined blocks.

No node to run

Skip the infrastructure — managed, always-synced access with no node to operate or maintain.

View the API docs Start building free

Building a full wallet? Explore HD Wallets.

Need prices too? See the crypto price API, or run your own Kaspa RPC nodes.

Scalable PoW blockchain with BlockDAG structure

Kaspa blockchain was developed to address scalability limitations and enhance transaction throughput by using a Directed Acyclic Graph (DAG) structure. Its design enables fast transaction confirmations, increased security, and decentralization, overcoming challenges faced by traditional blockchains.

Frequently Asked Questions

Which blockchain does Kaspa run on?

Kaspa settles on Kaspa. Balances are the sum of unspent outputs as on Bitcoin, but blocks arrive roughly once a second, so a deposit watcher sees confirmations far sooner and should reason in confirmation counts rather than elapsed minutes.

What kind of chain is Kaspa?

It is a UTXO chain with a blockDAG consensus, so blocks confirm in parallel rather than in a single line.

Can I test Kaspa without spending real funds?

Not on Kaspa — the API serves its mainnet only. Build against a chain that does have a testnet first, then switch the network parameter: the endpoints and the request shapes are the same.

How do I read Kaspa balances and transfers?

Use Address Latest for current state and recent activity — it needs no setup and answers for roughly the last 14 days. For a full history, Address History requires the address to be synced first, which then bills per address per day for as long as it stays synced.

What does reading Kaspa data cost?

It depends on the endpoint family rather than on Kaspa itself: single-record calls are charged per request, while list endpoints are charged per page returned, and a synced address adds a daily monitoring charge. The pricing calculator has the current per-chain figures.