CryptoQuant

A Postman API kit for CryptoQuant, providing ready-to-import requests for on-chain, market, flow, and network data across Bitcoin (BTC), Ethereum (ETH), and XRP.

At a Glance

Item	Included
Configured requests	223
Assets	BTC, ETH, XRP
Coverage	Exchange flows, indicators, markets, miners, networks, funds, and mempool
Authentication	Environment-based bearer token
Postman format	Collection schema v2.1

flowchart LR
    E["CryptoQuant environment"] --> A["Authorization: Bearer api_key"]
    A --> C["BTC, ETH, or XRP request"]
    C --> API["CryptoQuant API"]

Loading

Table of Contents

• Overview
• CryptoQuant API Details
• Getting Started
• Using the Collection
• Available Endpoints
• Contributing
• License
• Resources

Overview

This repository contains a Postman collection (CryptoQuant.postman_collection.json) and a companion environment file (CryptoQuant.postman_environment.json) for the CryptoQuant API. CryptoQuant provides on-chain and market data for major crypto assets, and this kit organizes its endpoints into folders per asset (BTC, ETH, XRP) and per data category (exchange flows, indicators, network stats, and more) so they can be explored and called directly from Postman.

CryptoQuant API Details

• Base URL: https://api.cryptoquant.com (set as the base_url variable in the environment file, and used as the host for every request in the collection).
• Authentication: Bearer token. Every request sends Authorization: Bearer {{api_key}}, with {{api_key}} resolved from the environment. Get your API key from your CryptoQuant account.

Rate limits and quota details are governed by your CryptoQuant plan; see the official docs linked in Resources for current specifics, as they aren't captured in the collection itself.

Getting Started

Prerequisites

• Postman installed.
• A CryptoQuant account and an API key.

Installation

1. Import both CryptoQuant.postman_collection.json and CryptoQuant.postman_environment.json into Postman (Import → File, or drag-and-drop).
2. In Postman's environment selector (top right), choose the CryptoQuant environment.
3. Open the CryptoQuant environment and set the api_key variable to your own key (e.g. YOUR_API_KEY). Never commit a real key back into this repository — the shipped environment file always keeps api_key empty.

Using the Collection

Authentication is pre-wired: every request already references {{api_key}} in its Authorization: Bearer {{api_key}} header, and {{base_url}} as its host. Once you've set api_key in the environment (as above), you can open any request and hit Send — no additional headers, scripts, or configuration are required. There is no pre-request script in this collection because none is needed: plain variable substitution handles authentication end-to-end.

Available Endpoints

The collection is organized by asset, then by data category. Folder names below match the collection exactly:

BTC

• Entity-Status
• Exchange-Flows
• Flow-Indicator
• Market-Indicator
• Network-Indicator
• Miner-Flows
• Inter-Entity-Flows
• Fund-Data
• Market-data
• Miner-Data
• Network-Data
• Mempool-Statistics
• Lightning-Network-Statistics

ETH

• Entity-Status
• Exchange-Flows
• Flow-Indicator
• Market-Indicator
• ETH-2.0
• Fund-Data
• Market-data
• ETH-Network-Data

XRP

• XRP-Entity-Status
• XRP-Entity-Flows
• XRP-Flow-Indicator
• XRP-Market-Data
• XRP-Network-Data
• XRP-Network-Indicator
• XRP-Dex-Data
• XRP-AMM-Data

Each category folder contains one or more requests for specific metrics (e.g. BTC > Exchange-Flows > Reserve, BTC > Flow-Indicator > Miners' Position Index (MPI)). Browse the collection tree in Postman for the full, current list of requests.

Project Status

The 223-request collection and its environment validate successfully and ship without an API key. Metric availability and history depend on the user's CryptoQuant plan, so use the provider documentation for current access and quota details.

This repository is part of the Crypto API Postman toolkit.

Contributing

Contributions are welcome. If you add or change requests, please:

• Keep collection and environment file names in the <Name>.postman_collection.json / <Name>.postman_environment.json format, with no spaces or version suffixes.
• Never commit a real API key or other credential — environment variables that hold secrets should always ship empty ("").
• Validate any JSON you edit with jq . <file> before committing.

License

This project is licensed under the MIT License — see LICENSE for the full text.

Resources

• CryptoQuant
• CryptoQuant API Documentation
• Postman Documentation