| description |
|---|
The mirror node REST API offers the ability to query transaction information. |
The Hedera Mirror Node REST API enables developers to access historical transaction data from Hedera's mainnet, testnet, and previewnet. Each transaction generates a record stored in a record file, which can be accessed via the Mirror Node REST APIs.
To make a request, use the network endpoint and the REST API of choice.
For example, To get a list of transactions on the Hedera mainnet, use the following API endpoint:
https://mainnet.mirrornode.hedera.com/api/v1/transactionsThis will return a JSON response containing transaction details such as transaction ID, timestamps, and fees.
If you are using curl, you can make a request like this:
curl -X GET "https://mainnet.mirrornode.hedera.com/api/v1/transactions" -H "Accept: application/json"Hedera provides interactive Swagger UI for its Mirror Node REST API. Developers can use these environments to explore available endpoints, check request parameters, and test API calls without writing code.
| Network | Swagger UI URL |
|---|---|
| Mainnet | Mainnet Swagger UI |
| Testnet | Testnet Swagger UI |
| Previewnet | Previewnet Swagger UI |
Hedera provides three different network environments for interacting with the Mirror Node API.
| Network | Base URL |
|---|---|
| Mainnet | https://mainnet.mirrornode.hedera.com/ |
| Testnet | https://testnet.mirrornode.hedera.com/ |
| Previewnet | https://previewnet.mirrornode.hedera.com/ |
Each of these base URLs serves as the foundation for all API calls.
You may also check out Validation Cloud, DragonGlass, or Arkhia as alternatives.
{% hint style="warning" %} Public mainnet mirror node requests per second (RPS) are currently throttled at 50 per IP address. These configurations may change in the future depending on performance or security considerations. At this time, no authentication is required. {% endhint %}