How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hiro Transactions API

Endpoints to obtain transaction details and to broadcast transactions to the network

Hiro Transactions API is one of 26 APIs that Hiro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 17 operations across 17 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.hiro.so/, http://localhost:20443.

17 operations 17 paths 3 schemas 15 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.mainnet.hiro.so
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Hiro Transactions API declares 1 security scheme for authenticating requests. An API key is passed in the header as authorization (rpcAuth).

  • rpcAuth — Plain-text secret value that must exactly equal the node's configured password, which is set as connectionoptions.authtoken in the node's configuration file.

Paths & Operations 17

Across 17 paths, the API surfaces 17 operations — 15 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 17

Endpoints to obtain transaction details and to broadcast transactions to the network

GET
/extended/v1/tx/
Get recent transactions
get_transaction_list 14 params → 2004XX
GET
/extended/v1/tx/multiple
Get list of details for transactions
get_tx_list_details 5 params → 2004XX
GET
/extended/v1/tx/mempool
Get mempool transactions
get_mempool_transaction_list 9 params → 2004XX
GET
/extended/v1/tx/mempool/stats
Get statistics for mempool transactions
get_mempool_transaction_stats → 2004XX
GET
/extended/v1/tx/events
Transaction Events
get_filtered_events 5 params → 2004XX
GET
/extended/v1/tx/{tx_id}
Get transaction
get_transaction_by_id 5 params → 2004XX
GET
/extended/v1/tx/{tx_id}/raw
Get raw transaction
get_raw_transaction_by_id 3 params → 2004XX
GET
/extended/v1/tx/block/{block_hash}deprecated
Transactions by block hash
get_transactions_by_block_hash 4 params → 2004XX
GET
/extended/v1/tx/block_height/{height}deprecated
Transactions by block height
get_transactions_by_block_height 4 params → 2004XX
GET
/extended/v1/address/{principal}/mempool
Transactions for address
get_address_mempool_transactions 5 params → 2004XX
GET
/extended/v2/blocks/{height_or_hash}/transactions
Get transactions by block
get_transactions_by_block 3 params → 2004XX
GET
/extended/v2/addresses/{address}/transactions
Get address transactions
get_address_transactions 4 params → 2004XX
GET
/extended/v2/addresses/{address}/transactions/{tx_id}/events
Get events for an address transaction
get_address_transaction_events 4 params → 2004XX
POST
/v2/transactions
Broadcast raw transaction
broadcastTransaction body → 200400500
GET
/v3/transaction/{txid}
Retrieve transaction details by TXID
getTransactionById 1 param → 200400404500501
GET
/v2/transactions/unconfirmed/{txid}
Get unconfirmed transaction
getUnconfirmedTransactionById 1 param → 200400404500
POST
/v2/mempool/query
Query mempool for missing transactions
queryMempool 1 param body → 200400500

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. Each schema is shown below with its type and property counts.

TransactionSubmissionError
UnconfirmedTransaction
TransactionInfo

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hiro-transactions-api-openapi.yml Raw ↑

Other APIs Hiro publishes across the network.

Hiro Chainhooks API
Hiro Platform API
Hiro Accounts API
Hiro Atlas API
Hiro Blocks API
Hiro Blocks Proposals API
Hiro Burn Blocks API
Hiro Faucets API
Hiro Fees API
Hiro Fungible Tokens API
Hiro Info API
Hiro Mempool API
Where this information came from

This is an independent, third-party profile of Hiro Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.