Crypto Accounting & Audit

Accounting software can add up the transactions it is given. What it cannot do is prove it was given all of them — and completeness, not arithmetic, is what an auditor actually tests. An extended public key fixes the address set, and syncing fixes the history: derive every address the key can produce, pull each one's full transaction record, and you have a ledger whose boundary you can demonstrate rather than assert.

100+ REST APIs
35+ Networks
99.99% Uptime
Start on the free plan Let's discuss your project

Some of the features you can use

One key defines the address set

Derive every receiving and change address an account can produce from its extended public key — a public key, never a private one. The set is complete by construction, so there is no question of an address having been missed.

Full history, not the recent window

Sync an address and read its entire transaction record, not just the last fortnight. Coin transfers, token transfers and EVM internal transactions all come back through the same endpoints, so a contract-mediated movement is not silently absent from the books.

Reconcile against the chain, continuously

Subscribe to confirmed transactions on the addresses you track and check your own ledger against what actually settled — the same day, rather than at the period close when the discrepancy is expensive to unpick.

An audit trail that does not depend on us

Every figure traces to a transaction hash on a public chain. A reviewer can verify it independently, and your records stay yours whether or not you keep using the API.

The benefits of using Crypto APIs

Developed to save time. Designed to be robust.

Save on development time

Leverage the power of a proven blockchain infrastructure trusted by industry leaders. Integrate once, go to market in days.

Reduce maintenance costs

Our flexible pricing plans offer the best cost to performance ratio. Get access to full product suite and features. Upgrade or downgrade anytime.

Enterprise-grade security

We apply encryption to REST, encryption to memory, and encryption in transit on all sensitive data. We are fully ISO 27001 certified.

All-in-one dashboard

One dashboard for all of your crypto operations. Get API keys, generate addresses, setup webhooks, monitor failed requests, callbacks and more.

How to reconcile crypto in your books

1

Map wallets to accounts

Register each wallet's addresses so every movement has a ledger home.

2

Capture every movement

Read full history including internal transactions, which plain transfer lists miss.

3

Value at transaction time

Pull the rate at each timestamp so the book value matches the moment it moved.

4

Get notified, not surprised

Subscribe to webhooks so new activity reaches the ledger as it happens.

You might also be interested in

Frequently Asked Questions

Which blockchains does the Address History API support?

The Address History API covers two families of chains. On the account-based side it supports Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, and Tron; on the UTXO side it supports Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. All of these are available on both mainnet and their respective testnets.

Does the Address History API support Solana?

Address History focuses on the EVM and UTXO chains plus XRP for time-ranged historical transaction data. Solana on-chain data (addresses, transactions, balances) is available through the Crypto APIs Solana endpoints; check the docs for the exact historical coverage per chain, as it varies by network.

Do I have to sync an address before I can query its history?

Yes. Address history requires you to first register (sync) the address you want to track, after which its full transaction history becomes queryable. You can add an address with the Sync Address endpoint, list your synced addresses, and later activate or delete them. Once synced, you can pull confirmed transactions, statistics, and token or internal-transaction data for that address.

How far back does the historical data go?

Address History returns the full history of a synced address from the Genesis block up to the present. For each address you can list all confirmed transactions (including in ascending or descending order, or from a given timestamp) and retrieve aggregate statistics across its entire history.

Can I get token transfers and internal transactions for an address?

Yes, on the EVM chains. For Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, and Tron you can list an address's token transfers, its internal transactions, and the tokens it holds. UTXO chains such as Bitcoin and Litecoin instead expose transaction history and unspent outputs (UTXOs) rather than token or internal-transaction data.

Which blockchains does the CryptoAPIs Transactions Data API support?

The Transactions Data API covers 35+ networks across four architectures. This includes EVM chains (Ethereum, Ethereum Classic, BNB Smart Chain, Polygon, Avalanche C-Chain, Tron, Arbitrum, Base, Optimism), UTXO chains (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash), plus XRP, Solana, and Kaspa. Both mainnet and testnet networks are available for most chains.

Does the Transactions Data API support Solana?

Yes. Solana is a live chain for the Transactions Data API, alongside XRP and Kaspa. You can retrieve detailed transaction data on Solana mainnet and its devnet network.

What data does the Transactions Data API return for a transaction?

It returns comprehensive details for any provided transaction, including the participating addresses (senders and recipients). This lets developers and businesses track and analyze blockchain activity and integrate transaction details into their applications. Coverage spans EVM, UTXO, XRP, Solana, and Kaspa chains.

Does the Transactions Data API cover Bitcoin and other UTXO chains?

Yes. UTXO chains are fully supported for transactions data, including Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, and Zcash. Both mainnet and testnet networks are available for these chains.

Can I query transactions on both mainnet and testnet?

Yes. Most supported chains expose both a mainnet and a test network, such as Ethereum mainnet and Sepolia, Bitcoin mainnet and testnet, and Solana mainnet and devnet. Kaspa is currently mainnet only.

What data does the Crypto APIs Market Data API return for a cryptocurrency?

It returns current asset details including live price, circulating and max supply, market capitalization, 24-hour trading volume, and token contract addresses across protocols. You can look up an asset by its symbol (e.g. BTC) or by its unique asset ID. Data is sourced from CoinMarketCap.

Does the Market Data API provide OHLCV candlesticks or order-book data?

No. The Market Data API provides current price and current asset-to-asset exchange rates only. It does not include OHLCV/candlestick history or per-exchange order-book data.

How do I get the exchange rate between two assets, like BTC to USD?

Use the exchange-rate endpoints, which return the current rate between any two assets. You can request the rate either by asset symbols (for example BTC to USD) or by the two assets' unique asset IDs.

How many assets does the Crypto APIs Market Data API cover?

The API covers approximately 14,600 crypto and fiat assets, sourced from CoinMarketCap. You can enumerate the full supported list via the list-supported-assets endpoint, which supports pagination and a filter for crypto or fiat asset types.

Can I look up assets by symbol or do I need an asset ID?

Both are supported. Asset details and exchange rates can be requested either by human-readable symbol (such as BTC or ETH) or by the asset's unique asset ID. Symbol-based lookups are convenient, while asset IDs disambiguate tokens that share a ticker.