From 77f63a10b681d3512bd08cd08de0ce67520250db Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 21:32:13 +0530 Subject: [PATCH 01/14] Expand Coinpath Explained docs: SEO metadata, worked examples, cross-links - Overview: added intro, use-cases table, chain-type comparison, navigation - How to Read: added intro summary, Next Steps footer with cross-links - EVM: added LRFS worked example, supported networks, Ethereum query - UTXO: added proportional attribution table, change output section, Bitcoin query - Ledger-Based: expanded 4 challenge sections, comparison table - All pages: SEO front matter (title, description, keywords), cross-links Made-with: Cursor --- .../Fund Tracking/EVM_Chains.md | 94 ++++++++++++++++--- .../Fund Tracking/Ledger_Based_Chains.md | 57 ++++++++--- .../Fund Tracking/UTXO_Chains.md | 94 ++++++++++++++++--- .../How_to_read_coinpath_graph.md | 15 +++ .../Coinpath-Explained/Overview.md | 53 ++++++++++- 5 files changed, 272 insertions(+), 41 deletions(-) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md index 7386178..aabedc8 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md @@ -1,21 +1,91 @@ --- sidebar_position: 1 +title: "Coinpath for EVM Networks — LRFS Fund Tracking" +description: "How Coinpath traces fund flows on EVM chains (Ethereum, BSC, Polygon, etc.) using the Last-Received First-Spent algorithm. Includes a worked example and a ready-to-run query." +keywords: [Coinpath, EVM, Ethereum, BSC, Polygon, LRFS, fund tracking, money flow, Bitquery] --- # Coinpath for EVM Networks -EVM Chains have balances, associated with accounts, and transfer is a -record of changing these balances of adding / subtracting amounts. +EVM chains have balances associated with accounts, and a transfer is a record of adding or subtracting amounts from those balances. Coinpath supports all EVM-compatible networks, including **Ethereum, Binance Smart Chain (BSC), Polygon, Cronos, Celo and Avalanche C-Chain**, and others. -- The algorithm is recursive, meaning that it starts at the initial address(es) and then calculates the money flow for each subsequent level, going deeper and deeper into the graph. -- At each level, the algorithm considers all of the incoming and outgoing transactions for the addresses on that level. It then uses a set of rules to determine how to associate the incoming and outgoing transactions, and how to assign amounts to the money flow edges. -- The algorithm can be implemented in a number of different ways, but the two most common methods are the "last received - first spent" (LRFS) method and the "proportional" method. -- The LRFS method is the simpler of the two methods, and it is the method that is used by the Coinpath API. With the LRFS method, the algorithm always associates incoming transactions with outgoing transactions in the order that they were received. +## How the Algorithm Works -### Here is a simplified explanation of how the LRFS method works: +The algorithm is **recursive**: it starts at the initial address(es) and calculates the money flow for each subsequent depth level, going deeper into the graph. -1. The algorithm starts at the initial address(es) and calculates the money flow for each subsequent level, going deeper and deeper into the graph. -2. At each level, the algorithm considers all of the incoming and outgoing transactions for the addresses on that level. -3. The algorithm then associates each incoming transaction with the first outgoing transaction that is equal to or less than the amount of the incoming transaction. -4. If there is more than one outgoing transaction that is equal to or less than the amount of the incoming transaction, the algorithm gives priority to the outgoing transaction that was sent first. -5. The algorithm repeats steps 3 and 4 until all of the incoming transactions have been associated with outgoing transactions. +At each level, Coinpath considers all incoming and outgoing transactions for every address and uses the **Last-Received First-Spent (LRFS)** method to associate incoming funds with outgoing ones. + +### LRFS Step by Step + +1. Start at the initial address and move to the next depth level. +2. Collect all incoming and outgoing transactions for each address at the current level. +3. Associate each incoming transaction with the **first** outgoing transaction whose amount is equal to or less than the incoming amount. +4. When multiple outgoing transactions qualify, the one **sent earliest** gets priority. +5. Repeat until all incoming transactions are matched or the specified depth is reached. + +### Worked Example + +Suppose address `0xABC` receives three deposits and makes two withdrawals in this order: + +| # | Direction | Amount | Time | +|---|---|---|---| +| 1 | IN | 5 ETH | 10:00 | +| 2 | IN | 3 ETH | 10:05 | +| 3 | OUT | 4 ETH | 10:10 | +| 4 | IN | 2 ETH | 10:15 | +| 5 | OUT | 6 ETH | 10:20 | + +Under LRFS: + +- **OUT #3 (4 ETH)** is matched against **IN #1 (5 ETH)** — the earliest unspent receipt that covers the amount. 4 ETH is attributed; 1 ETH remains unmatched from IN #1. +- **OUT #5 (6 ETH)** consumes the remaining **1 ETH from IN #1**, then **3 ETH from IN #2**, then **2 ETH from IN #4** — totalling 6 ETH. + +This gives a precise, deterministic attribution of which incoming funds were spent in each outgoing transfer. + +## Example Query — Ethereum Outbound Fund Flow + +Track where funds went from an address over 2 hops on Ethereum: + +[Open this query on IDE](https://ide.bitquery.io/destination-of-funds-for-upbit-hackers) + +```graphql +{ + ethereum(network: ethereum) { + outbound: coinpath( + initialAddress: { is: "0xa09871aeadf4994ca12f5c0b6056bbd1d343c029" } + currency: { is: "ETH" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + date: { since: "2018-03-01", till: "2021-01-31" } + ) { + sender { + address + annotation + } + receiver { + address + annotation + } + amount + currency { + symbol + } + depth + count + } + } +} +``` + +## Related + +- [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. +- [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. +- [UTXO Fund Tracking](./UTXO_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) +- [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) +- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md index 03b8227..e8a0c2d 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md @@ -1,20 +1,55 @@ --- sidebar_position: 3 +title: "Coinpath for Ledger-Based Networks — Multi-Currency Fund Tracking" +description: "How Coinpath handles the unique challenges of payment-ledger blockchains like Ripple (XRP) and Stellar (XLM): cross-currency payments, multi-issuer tokens, and implicit transfers." +keywords: [Coinpath, Ripple, XRP, Stellar, XLM, ledger, payment, fund tracking, cross-currency, money flow, Bitquery] --- # Coinpath for Ledger-Based Networks -Payment ledger blockchains, as Stellar and Ripple, impose additional complexity due to the following features of payment transactions: +Payment-ledger blockchains — primarily **Ripple (XRP Ledger)** and **Stellar (XLM)** — work differently from both UTXO and EVM chains. Instead of simple value transfers, a single payment transaction can involve currency conversions, multiple issuers, and implicit intermediate transfers. -1. **Payments can be sent in one currency and received in another currency.** This means that the money flow graph must be able to track the conversion of currencies between addresses. -2. **There may be multiple conversions between currencies in one payment transaction.** This means that the money flow graph must be able to track all of the conversions that occur in a single transaction. -3. **Currencies may have multiple issuers.** This means that the money flow graph must be able to track the flow of money between different issuers of the same currency. -4. **Blockchain API for Ripple does not allow to explicitly determine all transfers between addresses in scope of one transaction.** This means that the money flow graph must be able to infer all of the transfers that occur in a single transaction, even if they are not explicitly specified in the blockchain data. +## Challenges Specific to Payment Ledgers -To address these challenges, the money flow graph implementation for payment ledger blockchains makes the following adaptations: +### 1. Cross-Currency Payments -- Every transfer have separately defined sent and received amounts, with sent and received currencies, that may be different. -- Pre-processing extracts all value transfers between addresses, even when they are implicitly done inside a transaction. -- The money flow graph represents edges with different currencies on the same path. -- The money flow graph allows the same address to exist on the path on level N and N+1 (transferring himself as a result of trading). -- Only "taker" trades appear in the money flow result, as the "maker" side is not involved in the money flow path. +A sender can pay in one currency while the receiver receives a different currency. For example, Alice sends **USD** and Bob receives **EUR** — the ledger's built-in DEX converts between them automatically inside the same transaction. + +Coinpath handles this by recording **separate sent and received amounts and currencies** on every edge, so the money-flow graph accurately reflects what each party actually sent and received. + +### 2. Multiple Conversions in a Single Transaction + +A payment may pass through several order-book hops before settling. A single Ripple `Payment` transaction can trigger a chain like USD → XRP → EUR → GBP behind the scenes. + +Coinpath extracts **each intermediate hop** as a distinct edge in the fund-flow graph, giving you visibility into the full conversion path rather than just the start and end points. + +### 3. Multiple Issuers for the Same Currency + +On Ripple and Stellar, anyone can issue a token with the same symbol. "USD" from Gateway A is a different asset than "USD" from Gateway B. Two tokens named `USD` are not fungible unless they share the same issuer. + +Coinpath distinguishes assets by **(symbol + issuer)** so that fund-flow edges are never incorrectly merged across different trust lines. + +### 4. Implicit Transfers (Ripple-Specific) + +The Ripple API does not always surface every address-to-address transfer within a transaction. Some transfers happen implicitly as a side effect of order-book matching or path-finding. + +Coinpath's **pre-processing layer** reconstructs all implicit value transfers between addresses, even when they are not explicitly listed in the raw transaction data. + +## Adaptations in the Money-Flow Graph + +To address these challenges, the Coinpath graph for ledger-based chains differs from EVM/UTXO graphs in several ways: + +| Feature | EVM / UTXO | Ledger-based | +|---|---|---| +| Edge currencies | Same on both sides | May differ (sent currency ≠ received currency) | +| Same address at consecutive levels | Not allowed | Allowed (self-trades from DEX matching) | +| Trade visibility | All transfers explicit | Only **taker** side appears; maker side excluded from path | +| Pre-processing | Minimal | Extracts implicit transfers from raw tx data | + +## Related + +- [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. +- [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. +- [EVM Fund Tracking](./EVM_Chains) | [UTXO Fund Tracking](./UTXO_Chains) +- [Ripple schema reference](/docs/Schema/ripple/overview) +- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md index 75a89cc..bed7dd1 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md @@ -1,31 +1,97 @@ --- sidebar_position: 2 +title: "Coinpath for UTXO Networks — Proportional Attribution" +description: "How Coinpath traces fund flows on UTXO chains (Bitcoin, Litecoin, Dogecoin, etc.) using proportional input-output amount attribution. Includes a worked example and a ready-to-run query." +keywords: [Coinpath, UTXO, Bitcoin, Litecoin, Dogecoin, fund tracking, proportional attribution, money flow, Bitquery] --- # Coinpath for UTXO Networks -UTXOs are the basic unit of value on UTXO chains, and they represent the amount of tokens that can be spent in a single transaction. +UTXOs (Unspent Transaction Outputs) are the basic unit of value on UTXO-based blockchains. Each UTXO represents a discrete amount that can be consumed as an input to a new transaction. Coinpath supports all major UTXO networks, including **Bitcoin, Litecoin, Dogecoin, Bitcoin Cash, Zcash, and Dash**. -Coinpath also uses a proportional input-output amount attribution formula to split the amounts between inputs and outputs in a transaction. This formula takes into account the amount of each input and output, as well as the total amount of all inputs. +## How the Algorithm Works -For example, consider the following transaction: +Unlike EVM chains where balances change in-place, UTXO transactions consume one or more inputs and create one or more outputs. The challenge is: when a transaction has multiple inputs from different addresses, how much of each output should be attributed to each input? + +Coinpath uses a **proportional input-output amount attribution** formula. Each output's amount is split across the inputs in proportion to their share of the total input value. + +### Worked Example + +Consider a transaction with two inputs and three outputs: ``` Inputs: -Address A: 1 BTC -Address B: 2 BTC + Address A: 1 BTC + Address B: 2 BTC + ───────────────── + Total: 3 BTC Outputs: -Address C: 0.5 BTC -Address D: 2 BTC -Address B: 0.49 BTC - + Address C: 0.5 BTC + Address D: 2.0 BTC + Address B: 0.49 BTC (change) + ───────────────────── + Total: 2.99 BTC (0.01 BTC fee) ``` -Using the proportional input-output amount attribution formula, Coinpath would attribute the following amounts to each output: +**Proportional attribution:** + +Address A contributed 1/3 of the total input, Address B contributed 2/3. So each output is attributed proportionally: + +| Output | Total | From A (1/3) | From B (2/3) | +|---|---|---|---| +| Address C: 0.5 BTC | 0.5 | 0.167 BTC | 0.333 BTC | +| Address D: 2.0 BTC | 2.0 | 0.667 BTC | 1.333 BTC | +| Address B: 0.49 BTC (change) | 0.49 | 0.163 BTC | 0.327 BTC | + +### Change Outputs + +In UTXO mode, **change outputs are treated as separate outputs** and attributed like any other output. This is important because change goes back to one of the input addresses, and you may need to distinguish it from genuine transfers when analyzing fund flows. (In account-based / EVM mode, change is not a concept and is ignored.) + +## Example Query — Bitcoin Outbound Coinpath + +Track where BTC moved from an address over 2 hops: + +[Open this query on IDE](https://ide.bitquery.io/Bitcoin-outbound-coinpath-example) + +```graphql +{ + bitcoin(network: bitcoin) { + outbound: coinpath( + initialAddress: { is: "12cbQLTFMXRnSzktFkuoG3eHoMeFtpTu3S" } + currency: { is: "BTC" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + ) { + sender { + address + annotation + } + receiver { + address + annotation + } + amount + currency { + symbol + } + depth + count + } + } +} +``` -- Address C: 0.5 BTC -- Address D: 1.51 BTC (2 BTC - 0.49 BTC change) -- Address B: 0.49 BTC (change) +## Related -The change output is treated as a separate output in UTXO mode, but it is ignored in account-based mode. +- [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. +- [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. +- [EVM Fund Tracking](./EVM_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) +- [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) +- [Bitcoin Coinpath API examples](/docs/Examples/bitcoin/Bitcoin-Coinpath-API) +- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md b/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md index cdaffa1..0502e00 100644 --- a/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md +++ b/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md @@ -1,9 +1,14 @@ --- sidebar_position: 2 +title: "How to Read a Coinpath Graph — Nodes, Edges, Levels & Grouping" +description: "Learn to interpret Coinpath's money-flow DAG: nodes (addresses), edges (transfers), depth levels, transaction vs transactions grouping, and finalAddress vs sender/receiver filters." +keywords: [Coinpath graph, DAG, money flow, nodes, edges, depth, transaction grouping, finalAddress, Bitquery] --- # How to Read Coinpath Graph +Coinpath represents fund flows as a **directed acyclic multigraph (DAG)**. This page explains every component of that graph and the key query-level distinctions you need to know — `transaction` vs `transactions` grouping and `finalAddress` vs `sender`/`receiver` filtering. + ## Different Components of the Money Flow Graph Taking the Money Flow as a DAG Multigraph (directed acyclic multi graph) @@ -293,3 +298,13 @@ query ($network: EthereumNetwork!, $outboundDepth: Int!, $limit: Int!, $currency "dateFormat": "%Y-%m" } ``` + +--- + +## Next Steps + +- [Coinpath Overview](./Overview) — what Coinpath is and why it matters. +- **Fund Tracking by chain type:** [EVM](./Fund%20Tracking/EVM_Chains) | [UTXO](./Fund%20Tracking/UTXO_Chains) | [Ledger-based](./Fund%20Tracking/Ledger_Based_Chains) +- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) +- [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) +- [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) diff --git a/docs/building-queries/Coinpath-Explained/Overview.md b/docs/building-queries/Coinpath-Explained/Overview.md index 59ca9c1..ee0b821 100644 --- a/docs/building-queries/Coinpath-Explained/Overview.md +++ b/docs/building-queries/Coinpath-Explained/Overview.md @@ -1,13 +1,58 @@ --- sidebar_position: 1 +title: "Coinpath Overview — Blockchain Fund Flow Analysis" +description: "Coinpath abstracts blockchain protocol details to provide a unified fund-flow analysis layer. Trace money movement across UTXO, EVM, and ledger-based chains for compliance, forensics, and investigation." +keywords: [Coinpath, fund flow, money flow, blockchain compliance, AML, crypto forensics, transaction tracing, fund tracking, Bitquery] --- - # Overview of Coinpath -In this section we will breakdown in detail how coinpath is implemented to do fund flow analysis. This notion abstracts the blockchain protocol implementation details and focuses on the valuables transfer analysis. +Coinpath is Bitquery's proprietary technology for **tracing the movement of funds** across blockchain networks. It abstracts away protocol-level differences (UTXO models, account balances, payment ledgers) and presents a single, unified money-flow graph that you can query with GraphQL. + + + +## Why Coinpath? + +Raw blockchain data tells you that address A sent tokens to address B in a single transaction. Coinpath goes further: + +- **Multi-hop tracing** — follow funds through 2, 5, or even 10+ intermediate wallets with a single query (`depth` parameter). +- **Directional analysis** — track inbound (where did the money come from?) and outbound (where did it go?) flows independently. +- **Cross-chain coverage** — the same GraphQL schema works for Bitcoin, Ethereum, BSC, Solana, Cardano, Ripple, Stellar, and 20+ other networks. +- **Built-in attribution** — Coinpath uses chain-specific algorithms (LRFS for EVM, proportional I/O for UTXO) to assign amounts to edges in the money-flow graph. + +## Use Cases + +| Area | What Coinpath enables | +|---|---| +| **AML / Compliance** | Trace stolen funds, screen counterparties, generate evidence for regulators. | +| **Hack investigation** | Map where exploited funds moved after an attack (e.g. Upbit hack tracing). | +| **Bundle & sybil detection** | Identify wallets funded by the same source to detect coordinated pump schemes. | +| **Forensic auditing** | Build a complete funding history for any address across multiple hops. | +| **DeFi risk scoring** | Score addresses based on exposure to flagged wallets at any depth. | + +## How Coinpath Works Across Chain Types + +Different blockchains represent value in fundamentally different ways. Coinpath adapts its algorithm for each model: + +| Chain type | Algorithm | Details | +|---|---|---| +| **EVM** (Ethereum, BSC, Polygon, …) | Last-Received First-Spent (LRFS) | Associates incoming balance changes with outgoing ones in receipt order. [Learn more →](./Fund%20Tracking/EVM_Chains) | +| **UTXO** (Bitcoin, Litecoin, Dogecoin, …) | Proportional input-output attribution | Splits transaction amounts across inputs and outputs proportionally. [Learn more →](./Fund%20Tracking/UTXO_Chains) | +| **Ledger-based** (Ripple, Stellar) | Multi-currency path extraction | Handles cross-currency payments and implicit transfers within a single transaction. [Learn more →](./Fund%20Tracking/Ledger_Based_Chains) | + +## What You'll Learn in This Section + +1. **[How to Read a Coinpath Graph](./How_to_read_coinpath_graph)** — understand nodes, edges, levels, and the difference between `transaction` vs `transactions` grouping. +2. **Fund Tracking by Chain Type** + - [EVM Networks](./Fund%20Tracking/EVM_Chains) — LRFS method, worked example, Ethereum query. + - [UTXO Networks](./Fund%20Tracking/UTXO_Chains) — proportional attribution, Bitcoin query. + - [Ledger-Based Networks](./Fund%20Tracking/Ledger_Based_Chains) — multi-currency complexities. +## Quick Start -To view example queries, start [here](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +Jump straight into example queries: - \ No newline at end of file +- [Coinpath Money Flow API — full query cookbook](/docs/Examples/coinpath/money-flow-api) +- [Bitcoin Coinpath API examples](/docs/Examples/bitcoin/Bitcoin-Coinpath-API) +- [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) +- [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) From 32db7b26208ca3bcb51059cca897277cd54f9671 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 21:53:36 +0530 Subject: [PATCH 02/14] Full V1 docs SEO: metadata, keywords, and cross-links for 370+ pages - Added front matter title, description, keywords to all pages missing SEO - Added meta blocks (title, description, keywords, robots, OG, Twitter) - Added Related Resources cross-links using production URLs across all pages - Schema: all 24 chain overviews + ~250 detail pages (bitcoin, ethereum, polygon, BSC, tron, ripple, solana, avalanche, and 16 more chains) - Examples: 65 example pages across bitcoin, ethereum, solana, tron, cosmos, etc. - Core: intro, graphql-ide (10 pages), building-queries (3), query-features (16) - Use-Cases (5), API-Blog (1), Examples overview - Build verified: yarn build passes cleanly Made-with: Cursor --- docs/API-Blog/dogecoin-wallet-auditing.md | 29 ++++++++++++ .../Beacon Chain Examples/eth2_examples.md | 27 ++++++++++- docs/Examples/Dogecoin/get-latest-price.md | 29 ++++++++++++ docs/Examples/Dogecoin/inflow-outflow.md | 29 ++++++++++++ docs/Examples/Input_Output/IO_examples.md | 29 ++++++++++++ docs/Examples/Solana/address-api.md | 29 ++++++++++++ docs/Examples/Solana/instructions.md | 29 ++++++++++++ docs/Examples/Solana/transactions-api.md | 29 ++++++++++++ docs/Examples/Solana/transfers.md | 40 +++++++++++------ docs/Examples/Staking/stake_examples.md | 29 ++++++++++++ docs/Examples/Transactions/Trace_API.md | 29 ++++++++++++ .../Examples/Transactions/input-output-api.md | 29 ++++++++++++ docs/Examples/Transactions/transaction-api.md | 29 ++++++++++++ docs/Examples/Transfers/transfer-api.md | 26 +++++++++++ .../blockchain-active-addresses-api.md | 30 ++++++++++++- .../Blockchain-Address-API-Examples.md | 24 ++++++++++ docs/Examples/address/specific-queries.md | 26 +++++++++++ .../addressStats/address-stats-api.md | 30 ++++++++++++- docs/Examples/algorand/address.md | 31 ++++++++++++- docs/Examples/algorand/arguments.md | 29 ++++++++++++ docs/Examples/algorand/blocks.md | 31 ++++++++++++- docs/Examples/algorand/coinpath.md | 29 ++++++++++++ docs/Examples/bitcoin/Bitcoin-Blocks-API.md | 29 ++++++++++++ docs/Examples/bitcoin/Bitcoin-Coinpath-API.md | 35 +++++++++++---- ...-OmniTransactions-and-OmniTransfers API.md | 29 ++++++++++++ .../bitcoin/Bitcoin-Transaction-API.md | 29 ++++++++++++ docs/Examples/bitcoin/bitcoin-address-api.md | 35 +++++++++++---- docs/Examples/bitcoin/bitcoin-fee-api.md | 29 ++++++++++++ docs/Examples/bitcoin/index.md | 36 +++++++++++---- docs/Examples/cosmos/address.md | 31 ++++++++++++- docs/Examples/cosmos/attributes.md | 31 ++++++++++++- docs/Examples/cosmos/blocks.md | 31 ++++++++++++- docs/Examples/cosmos/coinpath.md | 31 ++++++++++++- docs/Examples/cosmos/messages.md | 29 ++++++++++++ docs/Examples/cosmos/transactions.md | 29 ++++++++++++ docs/Examples/cosmos/transfers.md | 29 ++++++++++++ docs/Examples/cross-chain/cross-chain-api.md | 29 ++++++++++++ docs/Examples/dexTrades/dex-pool-api.md | 29 ++++++++++++ .../dexTrades/dex-trading-data-api.md | 26 +++++++++++ docs/Examples/dexTrades/ohlc.md | 29 ++++++++++++ docs/Examples/filecoin/messages.md | 29 ++++++++++++ docs/Examples/hedera/hedera-address.md | 29 ++++++++++++ docs/Examples/hedera/hedera-io.md | 30 +++++++++++++ docs/Examples/hedera/hedera-messages.md | 30 +++++++++++++ docs/Examples/hedera/hedera-transactions.md | 30 +++++++++++++ docs/Examples/overview.md | 28 +++++++++++- docs/Examples/ripple/nft_token_offers.md | 29 ++++++++++++ .../smart-contract-calls-api.md | 29 ++++++++++++ .../smartcontractEvents/Non_EVM_events.md | 29 ++++++++++++ .../smart-contract-events-api.md | 29 ++++++++++++ docs/Examples/stellar/stellar-address-api.md | 31 ++++++++++++- docs/Examples/stellar/stellar-effects-api.md | 29 ++++++++++++ .../stellar/stellar-liquiditypool-api.md | 29 ++++++++++++ docs/Examples/stellar/stellar-payments-api.md | 29 ++++++++++++ .../stellar/stellar-tradeeffects-api.md | 45 +++++++++++-------- .../stellar/stellar-transactions-api.md | 29 ++++++++++++ docs/Examples/tokens/token-api.md | 30 ++++++++++++- docs/Examples/tron/address.md | 31 ++++++++++++- docs/Examples/tron/arguments.md | 32 ++++++++++++- docs/Examples/tron/blocks.md | 30 +++++++++++++ docs/Examples/tron/coinpath.md | 30 +++++++++++++ docs/Examples/tron/contracts.md | 29 ++++++++++++ docs/Examples/tron/dexTrades.md | 30 +++++++++++++ docs/Examples/tron/smartContractCalls.md | 30 +++++++++++++ docs/Examples/tron/smartContractEvents.md | 30 +++++++++++++ docs/Examples/tron/transaction.md | 31 ++++++++++++- docs/Examples/tron/transfers.md | 29 ++++++++++++ docs/Schema/Avalanche/address.md | 12 ++++- docs/Schema/Avalanche/arguments.md | 12 ++++- docs/Schema/Avalanche/blocks.md | 10 +++++ docs/Schema/Avalanche/calls.md | 10 +++++ docs/Schema/Avalanche/coinpath.md | 10 +++++ docs/Schema/Avalanche/overview.md | 28 +++++++++++- docs/Schema/Avalanche/transactions.md | 12 ++++- docs/Schema/Avalanche/transfers.md | 12 ++++- docs/Schema/Cronos/activeaddresses.md | 29 ++++++++++++ docs/Schema/Cronos/address.md | 29 ++++++++++++ docs/Schema/Cronos/addresstats.md | 29 ++++++++++++ docs/Schema/Cronos/arguments.md | 29 ++++++++++++ docs/Schema/Cronos/blocks.md | 28 ++++++++++++ docs/Schema/Cronos/coinpath.md | 29 +++++++++++- docs/Schema/Cronos/dextrades.md | 30 ++++++++++++- docs/Schema/Cronos/overview.md | 26 +++++++++++ docs/Schema/Cronos/references.md | 30 ++++++++++++- docs/Schema/Cronos/smartcontractcalls.md | 30 ++++++++++++- docs/Schema/Cronos/smartcontractevents.md | 28 ++++++++++++ docs/Schema/Cronos/transactions.md | 31 ++++++++++++- docs/Schema/Cronos/transfers.md | 31 ++++++++++++- docs/Schema/Dash/addressstats.md | 10 +++++ docs/Schema/Dash/blocks.md | 10 +++++ docs/Schema/Dash/coinpath.md | 10 +++++ docs/Schema/Dash/inputs.md | 12 ++++- docs/Schema/Dash/omnitransactions.md | 10 +++++ docs/Schema/Dash/omnitransfers.md | 10 +++++ docs/Schema/Dash/outputs.md | 10 +++++ docs/Schema/Dash/overview.md | 28 +++++++++++- docs/Schema/Dash/transactions.md | 10 +++++ docs/Schema/Dogecoin/addressstats.md | 10 +++++ docs/Schema/Dogecoin/blocks.md | 10 +++++ docs/Schema/Dogecoin/coinpath.md | 10 +++++ docs/Schema/Dogecoin/inputs.md | 12 ++++- docs/Schema/Dogecoin/omnitransactions.md | 10 +++++ docs/Schema/Dogecoin/outputs.md | 10 +++++ docs/Schema/Dogecoin/overview.md | 29 +++++++++++- docs/Schema/Dogecoin/transactions.md | 10 +++++ docs/Schema/Polygon/activeaddresses.md | 12 ++++- docs/Schema/Polygon/address.md | 12 ++++- docs/Schema/Polygon/addresstats.md | 12 ++++- docs/Schema/Polygon/arguments.md | 12 ++++- docs/Schema/Polygon/balance.md | 12 ++++- docs/Schema/Polygon/blocks.md | 11 ++++- docs/Schema/Polygon/coinpath.md | 12 ++++- docs/Schema/Polygon/dextrades.md | 12 ++++- docs/Schema/Polygon/overview.md | 30 ++++++++----- docs/Schema/Polygon/references.md | 30 ++++++++++++- docs/Schema/Polygon/smartcontractcalls.md | 12 ++++- docs/Schema/Polygon/smartcontractevents.md | 10 +++++ docs/Schema/Polygon/transactions.md | 12 ++++- docs/Schema/Polygon/transfers.md | 17 +++++-- docs/Schema/algorand/address.md | 31 ++++++++++++- docs/Schema/algorand/arguments.md | 30 ++++++++++++- docs/Schema/algorand/blocks.md | 31 ++++++++++++- docs/Schema/algorand/coinpath.md | 29 +++++++++++- docs/Schema/algorand/overview.md | 26 +++++++++++ docs/Schema/algorand/smartContractCalls.md | 29 ++++++++++++ docs/Schema/algorand/transactions.md | 31 ++++++++++++- docs/Schema/algorand/transfers.md | 29 ++++++++++++ .../binance_smart_chain/activeaddresses.md | 10 +++++ docs/Schema/binance_smart_chain/address.md | 10 +++++ .../Schema/binance_smart_chain/addresstats.md | 10 +++++ docs/Schema/binance_smart_chain/arguments.md | 10 +++++ docs/Schema/binance_smart_chain/blocks.md | 10 +++++ docs/Schema/binance_smart_chain/coinpath.md | 10 +++++ docs/Schema/binance_smart_chain/dextrades.md | 10 +++++ docs/Schema/binance_smart_chain/overview.md | 26 +++++++++++ docs/Schema/binance_smart_chain/references.md | 30 ++++++++++++- .../binance_smart_chain/smartcontractcalls.md | 10 +++++ .../smartcontractevents.md | 10 +++++ .../binance_smart_chain/transactions.md | 12 ++++- docs/Schema/binance_smart_chain/transfers.md | 12 ++++- docs/Schema/bitcoin/addressstats.md | 9 ++++ docs/Schema/bitcoin/blocks.md | 9 ++++ docs/Schema/bitcoin/coinpath.md | 9 ++++ docs/Schema/bitcoin/inputs.md | 9 ++++ docs/Schema/bitcoin/omnitransactions.md | 9 ++++ docs/Schema/bitcoin/omnitransfers.md | 9 ++++ docs/Schema/bitcoin/outputs.md | 9 ++++ docs/Schema/bitcoin/overview.md | 29 +++++++++++- docs/Schema/bitcoin/transactions.md | 9 ++++ docs/Schema/cardano/address.md | 31 ++++++++++++- docs/Schema/cardano/addressstats.md | 29 ++++++++++++ docs/Schema/cardano/blocks.md | 31 ++++++++++++- docs/Schema/cardano/coinpath.md | 30 ++++++++++++- docs/Schema/cardano/inputsOutputs.md | 31 ++++++++++++- docs/Schema/cardano/mints.md | 30 ++++++++++++- docs/Schema/cardano/overview.md | 27 ++++++++++- docs/Schema/cardano/transactions.md | 29 ++++++++++++ docs/Schema/celo/activeaddresses.md | 29 ++++++++++++ docs/Schema/celo/address.md | 29 ++++++++++++ docs/Schema/celo/addresstats.md | 29 ++++++++++++ docs/Schema/celo/arguments.md | 29 ++++++++++++ docs/Schema/celo/blocks.md | 29 ++++++++++++ docs/Schema/celo/coinpath.md | 29 +++++++++++- docs/Schema/celo/dextrades.md | 30 ++++++++++++- docs/Schema/celo/overview.md | 26 +++++++++++ docs/Schema/celo/references.md | 30 ++++++++++++- docs/Schema/celo/smartcontractcalls.md | 30 ++++++++++++- docs/Schema/celo/smartcontractevents.md | 28 ++++++++++++ docs/Schema/celo/transactions.md | 31 ++++++++++++- docs/Schema/celo/transfers.md | 31 ++++++++++++- docs/Schema/conflux/activeaddress.md | 29 ++++++++++++ docs/Schema/conflux/address.md | 29 ++++++++++++ docs/Schema/conflux/arguments.md | 29 ++++++++++++ docs/Schema/conflux/blocks.md | 29 ++++++++++++ docs/Schema/conflux/coinpath.md | 28 ++++++++++++ docs/Schema/conflux/overview.md | 27 ++++++++++- docs/Schema/conflux/smartcontractcalls.md | 29 ++++++++++++ docs/Schema/conflux/smartcontractevents.md | 29 ++++++++++++ docs/Schema/conflux/transactions.md | 29 ++++++++++++ docs/Schema/conflux/transfers.md | 29 ++++++++++++ docs/Schema/cosmos/address.md | 29 ++++++++++++ docs/Schema/cosmos/attributes.md | 29 ++++++++++++ docs/Schema/cosmos/blocks.md | 29 ++++++++++++ docs/Schema/cosmos/coinpath.md | 28 ++++++++++++ docs/Schema/cosmos/messages.md | 29 ++++++++++++ docs/Schema/cosmos/overview.md | 26 +++++++++++ docs/Schema/cosmos/transactions.md | 29 ++++++++++++ docs/Schema/cosmos/transfer.md | 29 ++++++++++++ docs/Schema/elrond/address.md | 31 ++++++++++++- docs/Schema/elrond/blocks.md | 29 ++++++++++++ docs/Schema/elrond/blockvalidators.md | 29 ++++++++++++ docs/Schema/elrond/callresults.md | 29 ++++++++++++ docs/Schema/elrond/miniblocks.md | 29 ++++++++++++ docs/Schema/elrond/notarizedblocks.md | 29 ++++++++++++ docs/Schema/elrond/operations.md | 29 ++++++++++++ docs/Schema/elrond/overview.md | 27 ++++++++++- docs/Schema/elrond/transactions.md | 29 ++++++++++++ docs/Schema/elrond/transfers.md | 29 ++++++++++++ docs/Schema/eos/addressstats.md | 29 ++++++++++++ docs/Schema/eos/blocks.md | 29 ++++++++++++ docs/Schema/eos/coinpath.md | 28 ++++++++++++ docs/Schema/eos/overview.md | 27 ++++++++++- docs/Schema/eos/proposers.md | 29 ++++++++++++ docs/Schema/eos/smartcontractcalls.md | 29 ++++++++++++ docs/Schema/eos/transactions.md | 29 ++++++++++++ docs/Schema/eos/transfers.md | 29 ++++++++++++ docs/Schema/ethereum/activeaddresses.md | 9 ++++ docs/Schema/ethereum/address.md | 9 ++++ docs/Schema/ethereum/addresstats.md | 9 ++++ docs/Schema/ethereum/arguments.md | 11 ++++- docs/Schema/ethereum/blocks.md | 9 ++++ docs/Schema/ethereum/coinpath.md | 11 ++++- docs/Schema/ethereum/dextrades.md | 10 ++++- docs/Schema/ethereum/overview.md | 28 +++++++++++- docs/Schema/ethereum/references.md | 11 ++++- docs/Schema/ethereum/smartcontractcalls.md | 11 ++++- docs/Schema/ethereum/smartcontractevents.md | 9 ++++ docs/Schema/ethereum/transactions.md | 9 ++++ docs/Schema/ethereum/transfers.md | 11 ++++- docs/Schema/ethereum2/attestations.md | 10 +++++ docs/Schema/ethereum2/attesterSlashings.md | 12 ++++- docs/Schema/ethereum2/blocks.md | 10 +++++ docs/Schema/ethereum2/deposits.md | 12 ++++- docs/Schema/ethereum2/overview.md | 28 +++++++++++- docs/Schema/ethereum2/proposerSlashings.md | 12 ++++- docs/Schema/ethereum2/validatorUpdates.md | 10 +++-- docs/Schema/ethereum2/voluntaryExits.md | 12 ++++- docs/Schema/filecoin/address.md | 31 ++++++++++++- docs/Schema/filecoin/arguments.md | 28 ++++++++++++ docs/Schema/filecoin/blocks.md | 31 ++++++++++++- docs/Schema/filecoin/calls.md | 31 ++++++++++++- docs/Schema/filecoin/messages.md | 31 ++++++++++++- docs/Schema/filecoin/overview.md | 28 +++++++++++- docs/Schema/filecoin/transfers.md | 31 ++++++++++++- docs/Schema/flow/address.md | 29 ++++++++++++ docs/Schema/flow/arguments.md | 31 ++++++++++++- docs/Schema/flow/blockSeals.md | 29 ++++++++++++ docs/Schema/flow/blocks.md | 29 ++++++++++++ docs/Schema/flow/coinpath.md | 28 ++++++++++++ docs/Schema/flow/collections.md | 29 ++++++++++++ docs/Schema/flow/eventFields.md | 29 ++++++++++++ docs/Schema/flow/events.md | 29 ++++++++++++ docs/Schema/flow/inputs.md | 29 ++++++++++++ docs/Schema/flow/outputs.md | 29 ++++++++++++ docs/Schema/flow/overview.md | 24 ++++++++++ docs/Schema/flow/transactionAuthorizers.md | 29 ++++++++++++ .../flow/transactionEnvelopeSignatures.md | 29 ++++++++++++ .../flow/transactionPayloadSignatures.md | 29 ++++++++++++ docs/Schema/flow/transactions.md | 29 ++++++++++++ docs/Schema/harmony/arguments.md | 29 ++++++++++++ docs/Schema/harmony/blocks.md | 29 ++++++++++++ docs/Schema/harmony/smartContractCalls.md | 29 ++++++++++++ docs/Schema/harmony/smartContractEvents.md | 29 ++++++++++++ docs/Schema/harmony/stakingTransactions.md | 29 ++++++++++++ docs/Schema/harmony/transactions.md | 29 ++++++++++++ docs/Schema/harmony/transfers.md | 29 ++++++++++++ docs/Schema/hedera/address.md | 31 ++++++++++++- docs/Schema/hedera/arguments.md | 31 ++++++++++++- docs/Schema/hedera/calls.md | 29 ++++++++++++ docs/Schema/hedera/coinpath.md | 28 ++++++++++++ docs/Schema/hedera/inputs.md | 29 ++++++++++++ docs/Schema/hedera/messages.md | 29 ++++++++++++ docs/Schema/hedera/outputs.md | 29 ++++++++++++ docs/Schema/hedera/overview.md | 26 +++++++++++ docs/Schema/hedera/transactions.md | 31 ++++++++++++- docs/Schema/ripple/accountRoots.md | 12 ++++- docs/Schema/ripple/address.md | 10 +++++ docs/Schema/ripple/addressStats.md | 12 ++++- docs/Schema/ripple/balances.md | 10 +++++ docs/Schema/ripple/blocks.md | 12 ++++- docs/Schema/ripple/checks.md | 10 +++++ docs/Schema/ripple/coinpath.md | 10 +++++ docs/Schema/ripple/escrows.md | 10 +++++ docs/Schema/ripple/nftokenOffers.md | 10 +++++ docs/Schema/ripple/offers.md | 10 +++++ docs/Schema/ripple/overview.md | 32 ++++++++++++- docs/Schema/ripple/payments.md | 10 +++++ docs/Schema/ripple/rippleStates.md | 10 +++++ docs/Schema/ripple/transactions.md | 10 +++++ docs/Schema/ripple/transfers.md | 10 +++++ docs/Schema/solana/address.md | 28 ++++++++++++ docs/Schema/solana/blockRewards.md | 31 ++++++++++++- docs/Schema/solana/blocks.md | 31 ++++++++++++- docs/Schema/solana/coinpath.md | 30 ++++++++++++- docs/Schema/solana/instructionAccounts.md | 31 ++++++++++++- docs/Schema/solana/instructions.md | 28 ++++++++++++ docs/Schema/solana/overview.md | 28 +++++++++++- docs/Schema/solana/transactions.md | 31 ++++++++++++- docs/Schema/solana/transfers.md | 31 ++++++++++++- docs/Schema/stellar/address.md | 29 ++++++++++++ docs/Schema/stellar/addressStats.md | 28 ++++++++++++ docs/Schema/stellar/balanceEffects.md | 29 ++++++++++++ docs/Schema/stellar/blocks.md | 29 ++++++++++++ .../Schema/stellar/claimableBalanceEffects.md | 29 ++++++++++++ docs/Schema/stellar/coinpath.md | 28 ++++++++++++ docs/Schema/stellar/effectArguments.md | 31 ++++++++++++- docs/Schema/stellar/effects.md | 29 ++++++++++++ docs/Schema/stellar/liquidityPoolEffects.md | 29 ++++++++++++ .../stellar/liquidityPoolTradeEffects.md | 29 ++++++++++++ docs/Schema/stellar/operations.md | 29 ++++++++++++ docs/Schema/stellar/overview.md | 32 ++++++++++++- docs/Schema/stellar/payments.md | 29 ++++++++++++ docs/Schema/stellar/tradeEffects.md | 29 ++++++++++++ docs/Schema/stellar/transactions.md | 29 ++++++++++++ docs/Schema/stellar/transfers.md | 29 ++++++++++++ docs/Schema/tezos/address.md | 31 ++++++++++++- docs/Schema/tezos/arguments.md | 29 ++++++++++++ docs/Schema/tezos/balanceUpdates.md | 29 ++++++++++++ docs/Schema/tezos/blocks.md | 28 ++++++++++++ docs/Schema/tezos/coinpath.md | 28 ++++++++++++ docs/Schema/tezos/operations.md | 29 ++++++++++++ docs/Schema/tezos/transactions.md | 29 ++++++++++++ docs/Schema/tezos/transfers.md | 31 ++++++++++++- docs/Schema/tron/address.md | 10 +++++ docs/Schema/tron/arguments.md | 10 +++++ docs/Schema/tron/blocks.md | 10 +++++ docs/Schema/tron/coinpath.md | 10 +++++ docs/Schema/tron/contracts.md | 10 +++++ docs/Schema/tron/dexTrades.md | 10 +++++ docs/Schema/tron/overview.md | 28 +++++++++++- docs/Schema/tron/smartContractCalls.md | 10 +++++ docs/Schema/tron/smartContractEvents.md | 10 +++++ docs/Schema/tron/transactions.md | 10 +++++ docs/Schema/tron/transfers.md | 12 ++++- docs/Schema/velas/activeaddresses.md | 29 ++++++++++++ docs/Schema/velas/address.md | 29 ++++++++++++ docs/Schema/velas/addresstats.md | 29 ++++++++++++ docs/Schema/velas/arguments.md | 29 ++++++++++++ docs/Schema/velas/blocks.md | 28 ++++++++++++ docs/Schema/velas/coinpath.md | 29 +++++++++++- docs/Schema/velas/dextrades.md | 30 ++++++++++++- docs/Schema/velas/overview.md | 26 +++++++++++ docs/Schema/velas/references.md | 30 ++++++++++++- docs/Schema/velas/smartcontractcalls.md | 30 ++++++++++++- docs/Schema/velas/smartcontractevents.md | 28 ++++++++++++ docs/Schema/velas/transactions.md | 31 ++++++++++++- docs/Schema/velas/transfers.md | 31 ++++++++++++- docs/Use-Cases/crypto-ml-price-prediction.md | 27 ++++++++++- docs/Use-Cases/react-example.md | 27 ++++++++++- docs/Use-Cases/tradeAmount-heatmap.md | 35 +++++++-------- docs/Use-Cases/tradingview.md | 26 +++++++++++ docs/Use-Cases/wordpress-wpgetapi.md | 27 ++++++++++- docs/building-queries/FAQ.md | 29 ++++++++++++ .../basic-structure-of-a-query.md | 28 +++++++++++- docs/building-queries/network-selection.md | 26 +++++++++++ docs/graphql-ide/account.md | 35 ++++++++++++++- docs/graphql-ide/apikey.md | 33 ++++++++++++++ docs/graphql-ide/errors.md | 38 ++++++++++++++++ docs/graphql-ide/how-to-start.md | 33 ++++++++++++++ docs/graphql-ide/ide.md | 34 ++++++++++++++ docs/graphql-ide/points.md | 33 ++++++++++++++ docs/graphql-ide/query-builder.md | 33 ++++++++++++++ docs/graphql-ide/supported-blockchains.md | 33 ++++++++++++++ .../graphql-ide/use-it-in-your-application.md | 33 ++++++++++++++ docs/graphql-ide/v1-and-v2.md | 39 +++++++++++++++- docs/intro.md | 34 ++++++++++++++ docs/query-features/Metrics.md | 28 +++++++++++- .../query-features/aggregation/aggregation.md | 27 ++++++++++- docs/query-features/aggregation/count.md | 26 +++++++++++ docs/query-features/aggregation/sum.md | 28 +++++++++++- docs/query-features/aliases.md | 28 +++++++++++- .../query-features/arguments/EVM_arguments.md | 29 +++++++++++- .../arguments/Other_Chains_arguments.md | 28 +++++++++++- docs/query-features/arguments/argument.md | 27 ++++++++++- docs/query-features/expressions/overview.md | 26 +++++++++++ docs/query-features/filtering/fields.md | 26 +++++++++++ docs/query-features/filtering/limits.md | 26 +++++++++++ docs/query-features/filtering/options.md | 28 +++++++++++- docs/query-features/filtering/sorting.md | 25 +++++++++++ docs/query-features/fragments/overview.md | 25 +++++++++++ docs/query-features/search/search.md | 32 ++++++++++++- docs/query-features/utilities/utilities.md | 30 +++++++++++++ 372 files changed, 8904 insertions(+), 221 deletions(-) diff --git a/docs/API-Blog/dogecoin-wallet-auditing.md b/docs/API-Blog/dogecoin-wallet-auditing.md index dfccda8..e7d1f9c 100644 --- a/docs/API-Blog/dogecoin-wallet-auditing.md +++ b/docs/API-Blog/dogecoin-wallet-auditing.md @@ -1,3 +1,24 @@ +--- +title: "Dogecoin Wallet Auditing with Bitquery API" +description: "Audit Dogecoin wallets for reporting, compliance, and forensics using Bitquery APIs: balances, transactions, and money-flow visualization." +keywords: [Dogecoin, wallet audit, Bitquery API, blockchain, forensics, transactions] +--- + + + + + + + + + + + + + + + + # How to Audit a Dogecoin Wallet Dogecoin, originally created as a meme cryptocurrency, has grown to be a significant digital asset with a vibrant community. With the increasing adoption of Dogecoin in transactions and investments, there is a rising need to audit Dogecoin wallets for various purposes, including financial reporting, compliance, and forensic investigations. In this blog, we will explore who needs Dogecoin wallet data, the types of data required, and how to audit Dogecoin wallets using Bitquery APIs. @@ -62,3 +83,11 @@ A forensic accountant might use Bitquery to track Dogecoin transactions across m Auditing a Dogecoin wallet requires a thorough understanding of blockchain data and the right tools to analyze it. Certified Accountants, external auditors, forensic accountants, and regulatory bodies all have a stake in ensuring the integrity of Dogecoin wallets. By leveraging tools like Bitquery, auditors can efficiently access and analyze the necessary data to perform accurate and comprehensive audits. Understanding the complexities of Dogecoin transactions and balances is key to a successful audit, ensuring transparency and trust in the growing world of cryptocurrency. + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Blockchain API examples — overview](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Examples/Beacon Chain Examples/eth2_examples.md b/docs/Examples/Beacon Chain Examples/eth2_examples.md index a8f7979..49230d8 100644 --- a/docs/Examples/Beacon Chain Examples/eth2_examples.md +++ b/docs/Examples/Beacon Chain Examples/eth2_examples.md @@ -1,7 +1,24 @@ --- +title: "Ethereum 2 / Beacon Chain API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Ethereum 2 and Beacon Chain data. Get validators, attestations, slots, and network stats." +keywords: [Ethereum 2 API examples, Beacon Chain GraphQL queries, Bitquery] sidebar_position: 1 --- + + + + + + + + + + + + + + # ETH2 Examples @@ -154,4 +171,12 @@ query ($network: Ethereum2Network!, $dateFormat: String!, $index: Int!, $from: I "till": null, "dateFormat": "%Y-%m-%d" } -``` \ No newline at end of file +``` + +## Related Resources + +- [Ethereum 2 schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/Dogecoin/get-latest-price.md b/docs/Examples/Dogecoin/get-latest-price.md index fbdfa8f..e8550d6 100644 --- a/docs/Examples/Dogecoin/get-latest-price.md +++ b/docs/Examples/Dogecoin/get-latest-price.md @@ -1,3 +1,24 @@ +--- +title: "Dogecoin Price API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Dogecoin USD price from on-chain data. Get latest price and block context." +keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Get Latest Price of Doge Coin in USD Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/dogecoin-price-in-use_1) query, we can get the latest price of Doge Coin in `USD`. @@ -21,3 +42,11 @@ query MyQuery { } } ``` + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Dogecoin inflow/outflow example](https://docs.bitquery.io/v1/docs/Examples/Dogecoin/inflow-outflow) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Dogecoin/inflow-outflow.md b/docs/Examples/Dogecoin/inflow-outflow.md index 872b559..fd072d9 100644 --- a/docs/Examples/Dogecoin/inflow-outflow.md +++ b/docs/Examples/Dogecoin/inflow-outflow.md @@ -1,3 +1,24 @@ +--- +title: "Dogecoin Transfers API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Dogecoin transfers and address flows. Get inbound and outbound transfer paths." +keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Tranfers of an Address on DogeCoin Network Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/zFB1y4MP5B) query, we can get the transfers of Doge Coin to a particular address. @@ -80,3 +101,11 @@ query ( "dateFormat": "%Y-%m" } ``` + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Dogecoin latest price example](https://docs.bitquery.io/v1/docs/Examples/Dogecoin/get-latest-price) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Input_Output/IO_examples.md b/docs/Examples/Input_Output/IO_examples.md index 69cc124..bcb0f66 100644 --- a/docs/Examples/Input_Output/IO_examples.md +++ b/docs/Examples/Input_Output/IO_examples.md @@ -1,3 +1,24 @@ +--- +title: "Inputs & Outputs API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for chain inputs and outputs. Get spend volume, currencies, and Flow token metrics." +keywords: [inputs outputs API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Inputs and Outputs ## Getting Spend Volume of a Token @@ -40,3 +61,11 @@ query MyQuery { ``` +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [UTXO input/output examples](https://docs.bitquery.io/v1/docs/Examples/Transactions/input-output-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/Solana/address-api.md b/docs/Examples/Solana/address-api.md index 0ae4e5e..d6f4a9f 100644 --- a/docs/Examples/Solana/address-api.md +++ b/docs/Examples/Solana/address-api.md @@ -1,3 +1,24 @@ +--- +title: "Solana Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Solana addresses. Get balances, annotations, and multi-address lookups." +keywords: [Solana API examples, Solana GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Solana Address API ## Latest Balance of an address @@ -33,3 +54,11 @@ query MyQuery { } } ``` + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Solana transfers examples](https://docs.bitquery.io/v1/docs/Examples/Solana/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Solana/instructions.md b/docs/Examples/Solana/instructions.md index d9a1ffc..11a25b4 100644 --- a/docs/Examples/Solana/instructions.md +++ b/docs/Examples/Solana/instructions.md @@ -1,3 +1,24 @@ +--- +title: "Solana Instructions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Solana instructions. Get program instructions, actions, logs, and transaction context." +keywords: [Solana API examples, Solana GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Solana Instructions Data ## Recent Solana Instructions @@ -164,3 +185,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Solana transactions examples](https://docs.bitquery.io/v1/docs/Examples/Solana/transactions-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Solana/transactions-api.md b/docs/Examples/Solana/transactions-api.md index c47223c..c40e7af 100644 --- a/docs/Examples/Solana/transactions-api.md +++ b/docs/Examples/Solana/transactions-api.md @@ -1,3 +1,24 @@ +--- +title: "Solana Transactions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Solana transactions. Get transactions by time range, fees, instructions, and block context." +keywords: [Solana API examples, Solana GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Solana Transactions API ## Transactions in a specific timeperiod @@ -66,3 +87,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Solana transfers examples](https://docs.bitquery.io/v1/docs/Examples/Solana/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Solana/transfers.md b/docs/Examples/Solana/transfers.md index e30ed3c..a63c411 100644 --- a/docs/Examples/Solana/transfers.md +++ b/docs/Examples/Solana/transfers.md @@ -1,20 +1,24 @@ --- -title: Solana Historical Transfers API Documentation -description: Comprehensive guide to Solana token transfers, SPL transfers, and wallet transaction monitoring using Bitquery's GraphQL API. -keywords: - - Solana transfers API - - Solana token transfers - - SPL token transfers - - Solana wallet transfers - - Solana transaction monitoring - - Solana transfer history - - Solana balance tracking - - Solana token holders - - Solana transfer analytics - - Solana transfer data - - Solana transfer queries +title: "Solana Transfers API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Solana transfer data. Get SPL and SOL transfers, wallet activity, and token movements." +keywords: [Solana API examples, Solana GraphQL queries, Bitquery] --- + + + + + + + + + + + + + + + # Solana Historical Transfers API The Solana Historical Transfers API provides comprehensive access to token transfer data on the Solana blockchain, including SPL token transfers, SOL transfers, and detailed transaction information. This API enables real-time monitoring and historical analysis of all transfer activities across the Solana network. @@ -823,3 +827,11 @@ query MyQuery { } } ``` + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Solana address API examples](https://docs.bitquery.io/v1/docs/Examples/Solana/address-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Staking/stake_examples.md b/docs/Examples/Staking/stake_examples.md index ea54d9e..6c65251 100644 --- a/docs/Examples/Staking/stake_examples.md +++ b/docs/Examples/Staking/stake_examples.md @@ -1,3 +1,24 @@ +--- +title: "Staking API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for staking data. Get Cardano stake rewards and distribution history." +keywords: [staking API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Staking Data Examples ## Get Staking Data for a Stake Address on Cardano @@ -75,3 +96,11 @@ You can access the query [here](https://ide.bitquery.io/staking-rewards-on-solan ``` + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Transactions/Trace_API.md b/docs/Examples/Transactions/Trace_API.md index 375da1d..1c3a512 100644 --- a/docs/Examples/Transactions/Trace_API.md +++ b/docs/Examples/Transactions/Trace_API.md @@ -1,3 +1,24 @@ +--- +title: "Ethereum Trace API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for EVM transaction traces. Inspect internal calls, gas, and execution trees." +keywords: [Ethereum API examples, trace GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Ethereum Trace API ## What is Ethereum Trace? @@ -53,3 +74,11 @@ The collect node has two child nodes, transfer and transfer. These two child nod The unwrapWETH9 node has two child nodes, balanceOf and withdraw. These two child nodes represent two separate calls to the balanceOf and withdraw functions in a different smart contract. You can also visualize it through [bloxy](https://bloxy.info/tx/0xd3c3e2164ac91c1d70abcce1bc06ef5107367596303e8925041ef4ebcfb39c43#) graph. I hope you found this blog on blockchain trace informative. If you have any questions, please feel free to leave a comment below. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Smart contract calls examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractCalls/smart-contract-calls-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Transactions/input-output-api.md b/docs/Examples/Transactions/input-output-api.md index 9fe9e4a..5452bd0 100644 --- a/docs/Examples/Transactions/input-output-api.md +++ b/docs/Examples/Transactions/input-output-api.md @@ -1,3 +1,24 @@ +--- +title: "UTXO Input Output API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for UTXO inputs and outputs on Bitcoin-family chains. Get scripts, values, and transaction links." +keywords: [UTXO API examples, Bitcoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # UTXO Input output API @@ -81,3 +102,11 @@ To check all inputs and outputs of a Bitcoin transaction, you can use the follow } ``` + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Input/Output examples folder](https://docs.bitquery.io/v1/docs/Examples/Input_Output/IO_examples) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Transactions/transaction-api.md b/docs/Examples/Transactions/transaction-api.md index 39f23af..75b62b9 100644 --- a/docs/Examples/Transactions/transaction-api.md +++ b/docs/Examples/Transactions/transaction-api.md @@ -1,3 +1,24 @@ +--- +title: "Multi-Chain Transaction API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for transactions on Bitcoin, Ethereum, and other networks. Get hashes, senders, receivers, and aggregates." +keywords: [transaction API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transaction API To get transactions from different blockchains, you can use our Transaction API. Let's see some examples. @@ -281,3 +302,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/Transfers/transfer-api.md b/docs/Examples/Transfers/transfer-api.md index b94487f..be4a407 100644 --- a/docs/Examples/Transfers/transfer-api.md +++ b/docs/Examples/Transfers/transfer-api.md @@ -1,7 +1,25 @@ --- +title: "Transfer API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for token and native transfers on EVM chains. Filter by address, contract, and time." +keywords: [transfer API examples, GraphQL queries, Bitquery] sidebar_position: 1 --- + + + + + + + + + + + + + + + # Transfer API Transfer API is available for all blockchains that have smart contract capabilities, especially EVMs. This api helps you get token (native or non-native) transfers. Let's see a few examples. @@ -515,3 +533,11 @@ query MyQuery { ## Detailed NFT Transfers NFT transfers are much better supported on our V2 APIs (Streaming APIs). Therefore please check [streaming APIs](https://bitquery.io/products/streaming). + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Transaction API examples](https://docs.bitquery.io/v1/docs/Examples/Transactions/transaction-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md index 4bf5fef..c806c5c 100644 --- a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md +++ b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md @@ -1,3 +1,23 @@ +--- +title: "Active Addresses API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for active addresses by chain or token. Count unique addresses over time." +keywords: [active addresses API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + # Active address API @@ -37,4 +57,12 @@ You can also get active addresses for specific currencies. In the following exam } } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Address stats examples](https://docs.bitquery.io/v1/docs/Examples/addressStats/address-stats-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/address/Blockchain-Address-API-Examples.md b/docs/Examples/address/Blockchain-Address-API-Examples.md index 701dc53..900a4e3 100644 --- a/docs/Examples/address/Blockchain-Address-API-Examples.md +++ b/docs/Examples/address/Blockchain-Address-API-Examples.md @@ -1,7 +1,25 @@ --- +title: "Blockchain Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for addresses across chains. Get transactions, balances, transfers, and coinpath." +keywords: [address API examples, GraphQL queries, Bitquery] sidebar_position: 1 --- + + + + + + + + + + + + + + + # Address API Our APIs can provide all sorts of details for any address on the blockchain. Let's see some examples. @@ -396,7 +414,13 @@ https://ide.bitquery.io/Destination-of-funds-for-an-address } ``` +## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cross-chain examples](https://docs.bitquery.io/v1/docs/Examples/cross-chain/cross-chain-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/address/specific-queries.md b/docs/Examples/address/specific-queries.md index 75b38c5..c1b211a 100644 --- a/docs/Examples/address/specific-queries.md +++ b/docs/Examples/address/specific-queries.md @@ -1,7 +1,25 @@ --- +title: "Address & Balance Query Examples — Bitquery GraphQL" +description: "Example GraphQL queries for address balances on EVM networks. Get native and token balances for Polygon and more." +keywords: [address API examples, GraphQL queries, Bitquery] sidebar_position: 2 --- + + + + + + + + + + + + + + + # Specific Queries on Address and Balances ## Get Native and Token Balance for a Matic Address @@ -40,3 +58,11 @@ query MyQuery { ``` Please note that the fields `value` and `balance` field values are of type `Float` not string. + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain address API examples](https://docs.bitquery.io/v1/docs/Examples/address/Blockchain-Address-API-Examples) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/addressStats/address-stats-api.md b/docs/Examples/addressStats/address-stats-api.md index 6b19867..fad2817 100644 --- a/docs/Examples/addressStats/address-stats-api.md +++ b/docs/Examples/addressStats/address-stats-api.md @@ -1,3 +1,23 @@ +--- +title: "Address Stats API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for EVM address statistics. Get balance, send/receive amounts, and transaction counts." +keywords: [address stats API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + # Address Stats API @@ -36,4 +56,12 @@ The Address Stats API provides comprehensive statistical data for a specific Eth } ``` -Please note that all amounts (`balance`, `receiveAmount`, `sendAmount`, and `feeAmount`) are returned as strings. \ No newline at end of file +Please note that all amounts (`balance`, `receiveAmount`, `sendAmount`, and `feeAmount`) are returned as strings. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain address API examples](https://docs.bitquery.io/v1/docs/Examples/address/Blockchain-Address-API-Examples) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/algorand/address.md b/docs/Examples/algorand/address.md index c211a02..86d7e7a 100644 --- a/docs/Examples/algorand/address.md +++ b/docs/Examples/algorand/address.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Algorand addresses. Get balances, assets, and smart contract bytecode." +keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Algorand Address API Our Algorand Address API provides all details regarding any address on Algorand Blockchain. If given address is a smart contract, API also provides details of that smart contract too. Below are some examples of `address` API: @@ -57,4 +78,12 @@ Replace addresses in the array with the actual Algorand addresses you want to qu ``` -Replace `SMART_CONTRACT_ADDRESS` with the actual Algorand address of the smart contract you want to query. This will return the bytecode, source code, and the address of the specified smart contract on the Algorand blockchain. \ No newline at end of file +Replace `SMART_CONTRACT_ADDRESS` with the actual Algorand address of the smart contract you want to query. This will return the bytecode, source code, and the address of the specified smart contract on the Algorand blockchain. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Algorand coinpath examples](https://docs.bitquery.io/v1/docs/Examples/algorand/coinpath) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/algorand/arguments.md b/docs/Examples/algorand/arguments.md index 69a15b1..142ecde 100644 --- a/docs/Examples/algorand/arguments.md +++ b/docs/Examples/algorand/arguments.md @@ -1,4 +1,33 @@ +--- +title: "Algorand Arguments API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Algorand smart contract arguments on calls and events." +keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Algorand Arguments API Our Algorand Arguments API provides all the details regarding all the arguments of smart contract calls and events. +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Algorand address examples](https://docs.bitquery.io/v1/docs/Examples/algorand/address) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/algorand/blocks.md b/docs/Examples/algorand/blocks.md index 4fa6a1e..807142b 100644 --- a/docs/Examples/algorand/blocks.md +++ b/docs/Examples/algorand/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Blocks API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Algorand blocks. Get proposers, rewards, and block metadata." +keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Algorand Blocks API Pur Alogrand Blocks API provides all details regarding blocks generated on Algorand Blockchain. Below are some examples of `blocks` API: @@ -44,4 +65,12 @@ Replace `PROPOSER_ADDRESS_HERE` with the actual Algorand address of the proposer } ``` -Replace `PROPOSER_ADDRESS_HERE` with the actual Algorand address of the proposer you want to query. This query will return the total sum of rewards for all blocks produced by the specified proposer address from the Algorand blockchain. \ No newline at end of file +Replace `PROPOSER_ADDRESS_HERE` with the actual Algorand address of the proposer you want to query. This query will return the total sum of rewards for all blocks produced by the specified proposer address from the Algorand blockchain. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Algorand address examples](https://docs.bitquery.io/v1/docs/Examples/algorand/address) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/algorand/coinpath.md b/docs/Examples/algorand/coinpath.md index a1bfa6c..3a6bc0f 100644 --- a/docs/Examples/algorand/coinpath.md +++ b/docs/Examples/algorand/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Coinpath API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Algorand coinpath. Trace senders, receivers, and transaction counts." +keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Algorand Coinpath API Our Algorand Coinpath API provides detailed information about money flow of addresses on the Algorand Blockchain. @@ -53,3 +74,11 @@ Replace `SENDER_ADDRESS_HERE` with the actual Algorand address of the sender you ``` Replace BWSNMG43TUYEOHE76J6KDWIY6MU4U6JFJYGAYCZA2RF5IS3XPO3P3G4FEI with the actual Algorand address of the receiver you want to query. This query will return the count of coinpath transactions received by the specified Algorand address after the date "2023-08-01" from the Algorand blockchain. It provides the total number of coinpath transactions received by the specified receiver address within the specified timeframe. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath money flow examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md index a28e45b..d9ec4fa 100644 --- a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md @@ -1,3 +1,24 @@ +--- +title: "Bitcoin Blocks API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin block data. Get recent blocks, height, difficulty, transaction counts, and timestamps." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Blocks API Our Bitcoin Blocks API provides all the information related to blocks produced on Bitcoin network. @@ -43,3 +64,11 @@ query { ``` This query fetches details about the 10 most transaction-laden blocks on the Bitcoin blockchain. We can see the difficulty, timestamp and number of transaction in each block. + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md index f4fedcb..b05cb25 100644 --- a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md @@ -1,13 +1,24 @@ --- -title: Bitcoin Coinpath API -description: Track Bitcoin (BTC) fund flows between addresses with GraphQL coinpath queries—depth, direction, and transaction paths on the Bitcoin network. -keywords: - - Bitcoin coinpath - - Bitcoin fund tracing - - BTC transaction path - - Bitcoin GraphQL API +title: "Bitcoin Coinpath API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin coinpath and fund flow data. Track transfers between addresses, depth, direction, and transaction paths." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- + + + + + + + + + + + + + + + # Coinpath API Our Bitcoin Coinpath API provides comprehensive information about money flow of addresses on the **Bitcoin** blockchain. @@ -112,4 +123,12 @@ query ($network: BitcoinNetwork!) { This query explores the relationship between two specific addresses (initialAddress and receiver) within the context of transactions that occurred after October 10, 2023. It retrieves a maximum of 10 transactions initiated from the initial address and received by the specified receiver. -For each transaction, the query provides details like the transferred amount in USD, block height, timestamp, currency information, sender and receiver addresses, transaction hash, and value. By analyzing these transactions, users can gain insights into the flow of funds between the two addresses and understand their financial interactions. \ No newline at end of file +For each transaction, the query provides details like the transferred amount in USD, block height, timestamp, currency information, sender and receiver addresses, transaction hash, and value. By analyzing these transactions, users can gain insights into the flow of funds between the two addresses and understand their financial interactions. + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin address API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin/bitcoin-address-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md b/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md index 221f4ce..4403c90 100644 --- a/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md +++ b/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md @@ -1,3 +1,24 @@ +--- +title: "Bitcoin Omni API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin Omni Layer data. Get Omni transactions and transfers by address." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Bitcoin OmniTransactions and OmniTransfers API ## Get the Latest Omni Transaction on Bitcoin @@ -47,3 +68,11 @@ query ($network: BitcoinNetwork!) { ``` This query provides all the omni transfers from a particular wallet address which is mentioned as “ADDRESS_HERE” and provides the block hash, transfer initiator and transfer receiver for each transfer + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md index c386a61..844e5fb 100644 --- a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md @@ -1,3 +1,24 @@ +--- +title: "Bitcoin Transaction API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin transactions. Get latest txs, fees, inputs, outputs, and daily aggregates." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transaction API ## Get Latest Transaction @@ -77,3 +98,11 @@ query ($network: BitcoinNetwork!) { ``` The query retrieves the count of all transactions sent by the specified Bitcoin address ("ADDRESS_HERE") from the Bitcoin blockchain. + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/bitcoin-address-api.md b/docs/Examples/bitcoin/bitcoin-address-api.md index e612722..a0f1c0a 100644 --- a/docs/Examples/bitcoin/bitcoin-address-api.md +++ b/docs/Examples/bitcoin/bitcoin-address-api.md @@ -1,13 +1,24 @@ --- -title: Bitcoin Address API — balances and UTXO activity -description: Query Bitcoin addresses for balance, inputs, outputs, and USD values using Bitquery GraphQL—address stats and UTXO-based balance derivation. -keywords: - - Bitcoin address API - - BTC balance API - - Bitcoin GraphQL - - UTXO Bitcoin API +title: "Bitcoin Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin address data. Get balances, inputs, outputs, UTXO activity, and USD values." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- + + + + + + + + + + + + + + + # BTC Balance API Our Input/Output APIs provides all the details regarding any address on Bitcoin Blockchain. To get the balance simply get all inputs and outputs and subtract (outputs - inputs). If will give you bitcoin balance. You can also get bitcoin balance in USD as we also getting usd values inputs and outputs. Remember we actually multiple usd value of bitcoin at the time of transaction as we also have historical usd price of bitcoin. @@ -196,4 +207,12 @@ To get inflows and outflow of a bitcoin address, use following API. ``` -Try this API to get inputs and outputs of a bitcoin address here.[https://ide.bitquery.io/Input-and-outputs-of-a-bitcoin-address] \ No newline at end of file +Try this API to get inputs and outputs of a bitcoin address here.[https://ide.bitquery.io/Input-and-outputs-of-a-bitcoin-address] + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/bitcoin/bitcoin-fee-api.md b/docs/Examples/bitcoin/bitcoin-fee-api.md index 243e732..b8c6624 100644 --- a/docs/Examples/bitcoin/bitcoin-fee-api.md +++ b/docs/Examples/bitcoin/bitcoin-fee-api.md @@ -1,3 +1,24 @@ +--- +title: "Bitcoin Fee API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin transaction fees. Get per-tx fees, USD fees, and fee aggregates by account." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Bitcoin Fee API This Bitquery API allows you to query Bitcoin transaction fees using GraphQL. You can retrieve detailed fee information for specific addresses, calculate total fees paid by an account, and convert fee values to USD. The examples below demonstrate how to use the API for common fee-related queries. @@ -62,3 +83,11 @@ query MyQuery { ## Video Tutorial | How to get Bitcoin Transaction Fees data using Bitquery APIs + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/index.md b/docs/Examples/bitcoin/index.md index cbc60e2..5d921d6 100644 --- a/docs/Examples/bitcoin/index.md +++ b/docs/Examples/bitcoin/index.md @@ -1,15 +1,25 @@ --- -title: Bitcoin API Documentation -description: Collection of Bitcoin APIs, Streams +title: "Bitcoin API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Bitcoin blockchain data. Get blocks, addresses, coinpath, fees, Omni, and transactions." +keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] slug: /examples/Bitcoin/ -keywords: - - Bitcoin API - - Bitcoin RPC - - Bitcoin blockchain API - - Bitcoin GraphQL API - - BTC API --- + + + + + + + + + + + + + + + # Bitcoin API Documentation This section contains Bitcoin API/Streams examples and guides, organized into categories for easier navigation. This is not exhaustive; we will add more examples as users request different scenarios. Also available in real-time via [Bitquery Kafka Streams](https://docs.bitquery.io/docs/streams/protobuf/chains/Bitcoin-protobuf/). Please contact sales for trial credentials. @@ -40,4 +50,12 @@ This section contains Bitcoin API/Streams examples and guides, organized into ca ## Transactions -- [Transaction API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-transaction-api) \ No newline at end of file +- [Transaction API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-transaction-api) + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/cosmos/address.md b/docs/Examples/cosmos/address.md index 5cbad8e..11f9ff2 100644 --- a/docs/Examples/cosmos/address.md +++ b/docs/Examples/cosmos/address.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos addresses. Get balances, transfers, and signer activity." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Cosmos Address API Our Cosmos Address API provides all the details regarding any address on Cosmos Blockchain. @@ -103,4 +124,12 @@ To get the same data for other currencies use following query. } } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos transfers examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/cosmos/attributes.md b/docs/Examples/cosmos/attributes.md index 93908f5..de607c6 100644 --- a/docs/Examples/cosmos/attributes.md +++ b/docs/Examples/cosmos/attributes.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Event Attributes API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos event attributes. Filter by event type and time ranges." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Attributes API Our Cosmos Attribtues API provides all the details regarding event attributes from Cosmos network. @@ -87,4 +108,12 @@ The query provides information about attribute names, block height, block timest } ``` -The query retrieves a count of unique occurrences of `proposal_vote` event attributes from the Cosmos blockchain, specifically those that occurred after August 8, 2023. The query uses the `count` function with the argument `uniq: times` to calculate the total number of times the `proposal_vote` event attributes appeared within the specified timeframe. \ No newline at end of file +The query retrieves a count of unique occurrences of `proposal_vote` event attributes from the Cosmos blockchain, specifically those that occurred after August 8, 2023. The query uses the `count` function with the argument `uniq: times` to calculate the total number of times the `proposal_vote` event attributes appeared within the specified timeframe. + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos messages examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/messages) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/cosmos/blocks.md b/docs/Examples/cosmos/blocks.md index 5645e92..a21f433 100644 --- a/docs/Examples/cosmos/blocks.md +++ b/docs/Examples/cosmos/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Blocks API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos blocks. Get heights, proposers, timestamps, and block counts." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Blocks API Our Cosmos Blocks API provides all the information related to blocks produced on Cosmos network. @@ -68,4 +89,12 @@ This query fetches details about the 10 most recent blocks on the Cosmos blockch } ``` -This query counts the number of blocks proposed by the address `13EE3F05F20C6AD8FD27CBEF33DD61D5F99ECF6F` on the Cosmos blockchain after the date "2023-08-07". It provides the total count of unique blocks that were proposed by the specified address within the specified timeframe. \ No newline at end of file +This query counts the number of blocks proposed by the address `13EE3F05F20C6AD8FD27CBEF33DD61D5F99ECF6F` on the Cosmos blockchain after the date "2023-08-07". It provides the total count of unique blocks that were proposed by the specified address within the specified timeframe. + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos transactions examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/transactions) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/cosmos/coinpath.md b/docs/Examples/cosmos/coinpath.md index af7d04a..dc321e1 100644 --- a/docs/Examples/cosmos/coinpath.md +++ b/docs/Examples/cosmos/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Coinpath API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos coinpath flows. Trace funds between addresses with depth and amounts." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Coinpath API Our Cosmos Coinpath API provides comprehensive information about money flow of addresses on the Cosmos blockchain. @@ -118,4 +139,12 @@ For each transaction, the query provides details like the transferred amount in } ``` -This query retrieves 10 latest transactions initiated from the initial address and received by the specified receiver, where the minimum transaction amount is set to 200. \ No newline at end of file +This query retrieves 10 latest transactions initiated from the initial address and received by the specified receiver, where the minimum transaction amount is set to 200. + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Staking examples](https://docs.bitquery.io/v1/docs/Examples/Staking/stake_examples) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/cosmos/messages.md b/docs/Examples/cosmos/messages.md index 62baf6d..4d81269 100644 --- a/docs/Examples/cosmos/messages.md +++ b/docs/Examples/cosmos/messages.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Messages API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos messages. Get message types by block and message counts." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Messages API Our Cosmos Messages API provides all the information related to messages generated on Cosmos Blockchain. @@ -73,3 +94,11 @@ This query retrieves messages from the Cosmos blockchain where transactions sign ``` This query retrieves the count of unique types of messages present in the block with a block height of 16494924 from the Cosmos blockchain. It provides information about the variety of message types contained within that specific block, helping to understand the diversity of actions or transactions taking place in that block. + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos transactions examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/transactions) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/cosmos/transactions.md b/docs/Examples/cosmos/transactions.md index 3ca2166..f9e3696 100644 --- a/docs/Examples/cosmos/transactions.md +++ b/docs/Examples/cosmos/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Transactions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos transactions. Get fees, gas, signers, and raw transaction data." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transactions API Our Cosmos Transactions API provides information related to transactions created on Cosmos Blockchain. @@ -69,4 +90,12 @@ This query retrieves transaction details based on a specific transaction hash. I This query retrieves transactions from a specific date, filtered by a particular signer's address. It retrieves information including the block's height and timestamp of each transaction, transaction fee, details about the fee currency including its name and address, gas used, transaction index, raw transaction data, signer's address, and transaction type. +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos transfers examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/cosmos/transfers.md b/docs/Examples/cosmos/transfers.md index 73c0acf..fabe74e 100644 --- a/docs/Examples/cosmos/transfers.md +++ b/docs/Examples/cosmos/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Transfers API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Cosmos transfers. Get transfers by signer, currency, value, and time." +keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transfers API Our Cosmos Transfers API provides all the information about token transfers happened on Cosmos Blockchain. @@ -79,3 +100,11 @@ This query fetches the latest 10 transfers of a specific currency, "Atom," on th For each transfer, it retrieves details such as the block's height, timestamp, currency address and name, receiver's and sender's addresses, transaction hash, transfer type, and the transferred value. +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos address examples](https://docs.bitquery.io/v1/docs/Examples/cosmos/address) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/cross-chain/cross-chain-api.md b/docs/Examples/cross-chain/cross-chain-api.md index a6a4be8..6fd8f8a 100644 --- a/docs/Examples/cross-chain/cross-chain-api.md +++ b/docs/Examples/cross-chain/cross-chain-api.md @@ -1,3 +1,24 @@ +--- +title: "Cross-Chain API Examples — Bitquery GraphQL" +description: "Example GraphQL queries spanning multiple blockchains. Get balances, transfers, trades, and token analytics in one request." +keywords: [cross-chain API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Cross-Chain API In this section we see how to use Bitquery APIs to get information across multiple chains in one go. @@ -709,3 +730,11 @@ query ($from: ISO8601DateTime, $till: ISO8601DateTime) { } ``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Address API examples](https://docs.bitquery.io/v1/docs/Examples/address/Blockchain-Address-API-Examples) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/dexTrades/dex-pool-api.md b/docs/Examples/dexTrades/dex-pool-api.md index ac2e6a6..12ba86a 100644 --- a/docs/Examples/dexTrades/dex-pool-api.md +++ b/docs/Examples/dexTrades/dex-pool-api.md @@ -1,3 +1,24 @@ +--- +title: "DEX Pools API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for DEX liquidity pools. Get pair creation, reserves, and pool metadata on EVM chains." +keywords: [DEX API examples, DEX GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Pools API In this section, we will look at some examples regarding DEX Pools data. @@ -63,3 +84,11 @@ To get the latest price, you can use our DEXTrades API. Here's an [example](http Once you have both values, you can multiply and get the FDV. +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [DEX trading data examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/dexTrades/dex-trading-data-api.md b/docs/Examples/dexTrades/dex-trading-data-api.md index cf6be60..cbbb75e 100644 --- a/docs/Examples/dexTrades/dex-trading-data-api.md +++ b/docs/Examples/dexTrades/dex-trading-data-api.md @@ -1,7 +1,25 @@ --- +title: "DEX Trading Data API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for DEX trades across EVM chains. Get swaps, liquidity, prices, and DEX analytics." +keywords: [DEX API examples, DEX GraphQL queries, Bitquery] sidebar_position: 1 --- + + + + + + + + + + + + + + + # DEX Trading Data APIs Our DEX trading APIs provides DEX data for 100s of DEXs from [40+ blockchains](https://app-status.bitquery.io/). Let's see some of example of getting DEX data. @@ -873,3 +891,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [DEX OHLC examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/ohlc) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/dexTrades/ohlc.md b/docs/Examples/dexTrades/ohlc.md index 0b1203a..c23407e 100644 --- a/docs/Examples/dexTrades/ohlc.md +++ b/docs/Examples/dexTrades/ohlc.md @@ -1,3 +1,24 @@ +--- +title: "DEX OHLC API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for DEX OHLC candle data. Get open, high, low, close, and trade counts for pairs." +keywords: [DEX API examples, DEX GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # OHLC API Using our APIs, you can also get [OHLC](https://en.wikipedia.org/wiki/Open-high-low-close_chart) data. @@ -90,3 +111,11 @@ In this example, we are getting OHLC prices by aggregating price data at run tim } } ``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [DEX trading data examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/filecoin/messages.md b/docs/Examples/filecoin/messages.md index 072f1e2..e8eb230 100644 --- a/docs/Examples/filecoin/messages.md +++ b/docs/Examples/filecoin/messages.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Messages API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Filecoin messages and storage deals. Track publish, faults, and on-chain actors." +keywords: [Filecoin API examples, Filecoin GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Filecoin Storage & Deal Data Examples In this section we will see some example queries that track different stages in a storae deal flow on Filecoin. For further details on Storage deals on Filecoin, refer to their [official documentation](https://docs.filecoin.io/storage-providers/filecoin-deals/storage-deals). @@ -165,3 +186,11 @@ query MyQuery { ``` (Run query here: [DeclareFaults](https://ide.bitquery.io/Filecoin-DeclareFaults-Message)) + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/hedera/hedera-address.md b/docs/Examples/hedera/hedera-address.md index 38275d3..c66f6bc 100644 --- a/docs/Examples/hedera/hedera-address.md +++ b/docs/Examples/hedera/hedera-address.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Hedera accounts. Get latest HBAR balances and account metadata." +keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Hedera Address API In this section we will see how to get information on wallets on Hedera. @@ -18,3 +39,11 @@ You can run the query [here](https://ide.bitquery.io/hedera-balance) } ``` + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Hedera transactions examples](https://docs.bitquery.io/v1/docs/Examples/hedera/hedera-transactions) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/hedera/hedera-io.md b/docs/Examples/hedera/hedera-io.md index 06f9601..e1fba67 100644 --- a/docs/Examples/hedera/hedera-io.md +++ b/docs/Examples/hedera/hedera-io.md @@ -1,5 +1,27 @@ +--- +title: "Hedera Inputs & Outputs API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Hedera transfers and account balances. Get inputs, outputs, and token movements." +keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Hedera Inputs & Outputs API + In this section we will see some examples on tracing funds from/to an hedera address. ## Most Transfered Token @@ -118,3 +140,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Hedera transactions examples](https://docs.bitquery.io/v1/docs/Examples/hedera/hedera-transactions) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/hedera/hedera-messages.md b/docs/Examples/hedera/hedera-messages.md index 5d3d48e..ed28d0e 100644 --- a/docs/Examples/hedera/hedera-messages.md +++ b/docs/Examples/hedera/hedera-messages.md @@ -1,5 +1,27 @@ +--- +title: "Hedera Messages API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Hedera network messages. Get memos, node accounts, and timestamps." +keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Hedera Messages API + In this section we will see how to get information on messages on Hedera. ## Latest Messages @@ -38,3 +60,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Hedera inputs/outputs examples](https://docs.bitquery.io/v1/docs/Examples/hedera/hedera-io) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/hedera/hedera-transactions.md b/docs/Examples/hedera/hedera-transactions.md index 136a0bb..7f3519f 100644 --- a/docs/Examples/hedera/hedera-transactions.md +++ b/docs/Examples/hedera/hedera-transactions.md @@ -1,5 +1,27 @@ +--- +title: "Hedera Transactions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Hedera consensus transactions. Get fees, timestamps, and transaction types." +keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Hedera Transactions API + In this section we will see how to get information on transactions on Hedera. ## Latest Transactions @@ -148,3 +170,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Hedera address examples](https://docs.bitquery.io/v1/docs/Examples/hedera/hedera-address) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/overview.md b/docs/Examples/overview.md index dbfda90..a3c4e78 100644 --- a/docs/Examples/overview.md +++ b/docs/Examples/overview.md @@ -1,7 +1,33 @@ --- +title: "Blockchain API Examples — Bitquery GraphQL Query Library" sidebar_position: 1 +description: "Browse ready-made GraphQL examples for Bitquery APIs—learn what data you can query and how to call each endpoint." +keywords: [Bitquery, GraphQL examples, blockchain API, query library, documentation] --- + + + + + + + + + + + + + + + # Overview -In this section we will see some examples of how to use the different APIs and what data you can get using them. \ No newline at end of file +In this section we will see some examples of how to use the different APIs and what data you can get using them. + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) \ No newline at end of file diff --git a/docs/Examples/ripple/nft_token_offers.md b/docs/Examples/ripple/nft_token_offers.md index 10584f0..d75fdb0 100644 --- a/docs/Examples/ripple/nft_token_offers.md +++ b/docs/Examples/ripple/nft_token_offers.md @@ -1,3 +1,24 @@ +--- +title: "Ripple NFT Token Offers API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for XRPL NFT token offers. Filter by sender, amounts, and operations." +keywords: [Ripple API examples, XRP GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Ripple NFT Token Offers API Ripple NFT Token Offers API provides all details regarding NFT Token offers on Ripple Blockchain. Below are some examples of `nftokenOffers` API: @@ -53,3 +74,11 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date "network": "ripple" } ``` + +## Related Resources + +- [Ripple schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Blockchain API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md index 4cef3d3..4aa06b9 100644 --- a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md +++ b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md @@ -1,3 +1,24 @@ +--- +title: "Smart Contract Calls API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for EVM smart contract calls. Get methods, arguments, call depth, and callers." +keywords: [smart contract API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Smart contract call API Our Smart contract call API allows you access to parsed smart contract calls and arguments for all the blockchains we support. @@ -366,3 +387,11 @@ query ($network: EthereumNetwork!, $address: String!, $limit: Int!, $offset: Int ``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Smart contract events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/smartcontractEvents/Non_EVM_events.md b/docs/Examples/smartcontractEvents/Non_EVM_events.md index 7e1221b..097f84b 100644 --- a/docs/Examples/smartcontractEvents/Non_EVM_events.md +++ b/docs/Examples/smartcontractEvents/Non_EVM_events.md @@ -1,3 +1,24 @@ +--- +title: "Non-EVM Smart Contract Events API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for events on non-EVM chains like Flow. Get mint, burn, and custom event data." +keywords: [smart contract API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Events on Non-EVM Chains Our Smart contract event API allows you access parsed smart contract events and arguments for all the blockchains we support. In this section let's focus on examples for chain other than ones on EVM. @@ -50,3 +71,11 @@ query MyQuery { ``` + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [EVM smart contract events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/smartcontractEvents/smart-contract-events-api.md b/docs/Examples/smartcontractEvents/smart-contract-events-api.md index 6a941f7..0d34e31 100644 --- a/docs/Examples/smartcontractEvents/smart-contract-events-api.md +++ b/docs/Examples/smartcontractEvents/smart-contract-events-api.md @@ -1,3 +1,24 @@ +--- +title: "Smart Contract Events API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for EVM smart contract events. Get logs, topics, arguments, and transaction hashes." +keywords: [smart contract API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Smart contract event API Our Smart contract event API allows you access parsed smart contract events and arguments for all the blockchains we support. @@ -238,3 +259,11 @@ Let's see how to do argument filtering using our V1 API. ``` Our v1 APIs support Argument Filtering, however we would rather suggest using V2 APIs for this. They are much more powerful in arguments, allowing argument aggregation and filtering. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Non-EVM events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/Non_EVM_events) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/stellar/stellar-address-api.md b/docs/Examples/stellar/stellar-address-api.md index 8e9f446..d9f300b 100644 --- a/docs/Examples/stellar/stellar-address-api.md +++ b/docs/Examples/stellar/stellar-address-api.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar addresses. Get wallet balances, assets, issuers, and asset codes." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Stellar Address API This API allows you to retrieve detailed information about Stellar wallet addresses, including their balances and token holdings. @@ -23,4 +44,12 @@ query MyQuery { } ``` -You can run the query [here](https://ide.bitquery.io/latest-balance-of-stellar-wallet) \ No newline at end of file +You can run the query [here](https://ide.bitquery.io/latest-balance-of-stellar-wallet) + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar payments examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-payments-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/stellar/stellar-effects-api.md b/docs/Examples/stellar/stellar-effects-api.md index ed2f666..032d8f1 100644 --- a/docs/Examples/stellar/stellar-effects-api.md +++ b/docs/Examples/stellar/stellar-effects-api.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Effects API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar ledger effects. Get state changes, operations, and transaction links." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Stellar Effects API All changes on the ledger are recorded as effects including changes after transactions, trades and so on. In this section we will see how to use Bitquery API to get effects information. @@ -68,3 +89,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar liquidity pool examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-liquiditypool-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/stellar/stellar-liquiditypool-api.md b/docs/Examples/stellar/stellar-liquiditypool-api.md index 7522fbf..e86cd3b 100644 --- a/docs/Examples/stellar/stellar-liquiditypool-api.md +++ b/docs/Examples/stellar/stellar-liquiditypool-api.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Liquidity Pools API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar liquidity pool effects. Get pool operations, transactions, and currencies." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Stellar Liquidity Pools API This API allows you to access and analyze effects from Stellar's liquidity pools. Effects are specific changes that occur within the ledger due to operations performed on the liquidity pools. @@ -75,3 +96,11 @@ query MyQuery { ``` + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar effects examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-effects-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/stellar/stellar-payments-api.md b/docs/Examples/stellar/stellar-payments-api.md index ee9b502..8aa23e7 100644 --- a/docs/Examples/stellar/stellar-payments-api.md +++ b/docs/Examples/stellar/stellar-payments-api.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Payments API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar payments. Get amounts, currencies, issuers, paths, and counterparties." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Stellar Payments API This API enables you to access and analyze payment transactions on the Stellar network, providing detailed information about each payment, including amounts, currencies, issuers, timestamps, and paths. @@ -74,3 +95,11 @@ The path field contains an array of assets involved in the payment path. Each as ] ``` + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar trades examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-tradeeffects-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/stellar/stellar-tradeeffects-api.md b/docs/Examples/stellar/stellar-tradeeffects-api.md index 5b8894e..078aced 100644 --- a/docs/Examples/stellar/stellar-tradeeffects-api.md +++ b/docs/Examples/stellar/stellar-tradeeffects-api.md @@ -1,26 +1,25 @@ --- -title: Stellar Trades API -description: Access comprehensive Stellar Trade API with Effects and Price +title: "Stellar Trades API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar DEX trades and trade effects. Get prices, sellers, buyers, and assets." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] slug: /blockchain/Stellar/trade-effects-api -keywords: - - Stellar Trade Effects API - - Stellar DEX API - - Stellar trading API - - Stellar blockchain API - - Stellar GraphQL API - - Stellar trade data - - Stellar token swaps - - Stellar DEX trades - - Stellar trading analytics - - Stellar API documentation - - Stellar blockchain data API - - Stellar asset trading - - Stellar orderbook API - - Stellar liquidity pools - - free stellar api - - stellar data api --- + + + + + + + + + + + + + + + # Stellar Trades API @@ -142,3 +141,11 @@ query MyQuery { } ``` +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar payments examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-payments-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/stellar/stellar-transactions-api.md b/docs/Examples/stellar/stellar-transactions-api.md index 68bd162..83eeff8 100644 --- a/docs/Examples/stellar/stellar-transactions-api.md +++ b/docs/Examples/stellar/stellar-transactions-api.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Transactions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Stellar transactions. Get fees, hashes, senders, operation counts, and timestamps." +keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Stellar Transactions API This API enables you to access and analyze transactions on the Stellar network, providing detailed information about each transaction, including the fee, hash, sender, and timestamp. @@ -64,3 +85,11 @@ query MyQuery { } ``` + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar payments examples](https://docs.bitquery.io/v1/docs/Examples/stellar/stellar-payments-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/tokens/token-api.md b/docs/Examples/tokens/token-api.md index 4ace2e5..e75f349 100644 --- a/docs/Examples/tokens/token-api.md +++ b/docs/Examples/tokens/token-api.md @@ -1,3 +1,23 @@ +--- +title: "Token API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for token prices, holders, supply, and DEX trades. Works across supported EVM chains." +keywords: [token API examples, GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + # Token API Bitquery's flexible GraphQL APIs will help you get all sorts of token related data. We will show example of USDT on Ethereum but you can actually use same APIs to get data for any token on all chains supported by Bitquery. @@ -664,4 +684,12 @@ You can also track token approvals permissions using `Approval` event. } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [DEX trading data examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/tron/address.md b/docs/Examples/tron/address.md index c9c4d5b..b4cb1a8 100644 --- a/docs/Examples/tron/address.md +++ b/docs/Examples/tron/address.md @@ -1,3 +1,24 @@ +--- +title: "Tron Address API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron addresses. Get balance, rewards, and smart contract details for an address." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Address API Our Tron Address API provides all details regarding any address on Tron Blockchain. If given address is a smart contract API also details of that smart contract too. @@ -76,4 +97,12 @@ Replace `ADDRESS_HERE` with the Tron address you want to query. This query will } ``` -Replace `ADDRESS_HERE` with the Tron address you want to query. This query will fetch basic details of the smart contract, such as contract type and protocol type. If the contract is an ERC-20 token, it will also return additional information like decimals, name, symbol, and token type. \ No newline at end of file +Replace `ADDRESS_HERE` with the Tron address you want to query. This query will fetch basic details of the smart contract, such as contract type and protocol type. If the contract is an ERC-20 token, it will also return additional information like decimals, name, symbol, and token type. + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron transfers examples](https://docs.bitquery.io/v1/docs/Examples/tron/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/tron/arguments.md b/docs/Examples/tron/arguments.md index 1f17dd8..17a20ba 100644 --- a/docs/Examples/tron/arguments.md +++ b/docs/Examples/tron/arguments.md @@ -1,5 +1,27 @@ +--- +title: "Tron Smart Contract Arguments API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron smart contract call arguments. Filter by method, block, and transaction index." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Arguments API + Our Ton Arguments API provides all details regarding smart contract or event arguments on Tron Blockchain. ## Get Arguments For Latest Smart Contract Calls and Events @@ -108,4 +130,12 @@ This query will return the arguments where name of event is `Transfer`. } ``` -This query will return data of arguments for `Transfer` events happened after block height of 53392720. \ No newline at end of file +This query will return data of arguments for `Transfer` events happened after block height of 53392720. + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron smart contract calls examples](https://docs.bitquery.io/v1/docs/Examples/tron/smartContractCalls) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/tron/blocks.md b/docs/Examples/tron/blocks.md index e261441..da05476 100644 --- a/docs/Examples/tron/blocks.md +++ b/docs/Examples/tron/blocks.md @@ -1,5 +1,27 @@ +--- +title: "Tron Blocks API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron blocks. Get recent blocks, witnesses, timestamps, and parent hashes." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Blocks API + Our Tron API provides all details regarding blocks from Tron Blockchain. ## Get Transaction Trie Root of Block @@ -82,3 +104,11 @@ This query filter block data by parent block hash of that block. This query allows us to filter block by it's witness address. +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron transactions examples](https://docs.bitquery.io/v1/docs/Examples/tron/transaction) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/tron/coinpath.md b/docs/Examples/tron/coinpath.md index 2a6715d..eec8797 100644 --- a/docs/Examples/tron/coinpath.md +++ b/docs/Examples/tron/coinpath.md @@ -1,5 +1,27 @@ +--- +title: "Tron Coinpath API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron coinpath and fund flows. Trace sender, receiver, depth, and amounts." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Coinpath API + Our Tron Coinpath API provides comprehensive information about money flow of addresses on the Tron blockchain. ## Get Money Flow of Particular Address @@ -89,3 +111,11 @@ This query allows you to retrieve the money flow details originating from a part ``` This query allows you to retrieve the money flow details where the receiver is a particular address (TTd9qHyjqiUkfTxe3gotbuTMpjU8LEbpkN) for the Tron currency (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t) after July 31, 2023. The results are ordered in descending order based on block timestamps and are limited to the top 5 entries. +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath money flow examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/tron/contracts.md b/docs/Examples/tron/contracts.md index 95dee3a..f14602c 100644 --- a/docs/Examples/tron/contracts.md +++ b/docs/Examples/tron/contracts.md @@ -1,2 +1,31 @@ +--- +title: "Tron Contracts API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron smart contracts and on-chain contract data via Bitquery GraphQL." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Contracts API +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron smart contract calls examples](https://docs.bitquery.io/v1/docs/Examples/tron/smartContractCalls) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/tron/dexTrades.md b/docs/Examples/tron/dexTrades.md index 1d3bfab..92c50f4 100644 --- a/docs/Examples/tron/dexTrades.md +++ b/docs/Examples/tron/dexTrades.md @@ -1,5 +1,27 @@ +--- +title: "Tron DEX Trades API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron DEX trades. Get pairs, base/quote currencies, smart contracts, and trade counts." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # DEX Trade API + Our Tron DEX Trade API provides comprehensive information about DEX Trades from Tron blockchain. ## Get USDT Trade from Tron blockchain @@ -93,3 +115,11 @@ This query retrieves the latest 10 decentralized exchange (DEX) trades on the Tr This query retrieves the latest 10 decentralized exchange (DEX) trades on the Tron network for the base currency "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" and provides the base currency symbol, name, and address, quote currency symbol, name, and address, smart contract address, and the trade count for each unique smart contract address involved in the trades. +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [DEX trades examples (folder)](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Examples/tron/smartContractCalls.md b/docs/Examples/tron/smartContractCalls.md index 4c07478..9b3d1ba 100644 --- a/docs/Examples/tron/smartContractCalls.md +++ b/docs/Examples/tron/smartContractCalls.md @@ -1,5 +1,27 @@ +--- +title: "Tron Smart Contract Calls API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron smart contract calls. Filter by method, contract, energy usage, and arguments." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Smart Contract Calls API + Our Tron Smart Contract Calls API provides detailed information about smart contract calls executed on the Tron Blockchain. ## Get List of Latest Smart Contract Calls @@ -127,3 +149,11 @@ This query retrieves the latest 10 smart contract calls on the Tron network that ``` This query retrieves the latest 10 smart contract calls on the Tron network that occurred after July 31, 2023, specifically for the smart contract "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" and the method "Transfer". It provides details such as call amount, arguments, block height and timestamp, energy usage, net usage for the specified method, smart contract address, method name and signature, and transaction hash. + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron smart contract events examples](https://docs.bitquery.io/v1/docs/Examples/tron/smartContractEvents) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/tron/smartContractEvents.md b/docs/Examples/tron/smartContractEvents.md index bd5c5d2..5a60090 100644 --- a/docs/Examples/tron/smartContractEvents.md +++ b/docs/Examples/tron/smartContractEvents.md @@ -1,5 +1,27 @@ +--- +title: "Tron Smart Contract Events API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron smart contract events. Filter by contract, event name, block, and logs." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Smart Contract Events API + Our Tron Smart Contract Events API provides detailed information about smart contract events executed made on Tron Blockchain. ## Get List of Latest Smart Contract Events @@ -123,3 +145,11 @@ This query retrieves the latest 10 smart contract events on the Tron network tha ``` The query retrieves the latest 10 smart contract events on the Tron network that occurred after July 31, 2023, for the smart contract "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" and can include events with names "Transfer", "Approval", and any other event names specified in the in clause. It provides details such as event arguments, block height and timestamp, smart contract address, event name and signature, and transaction hash. + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron smart contract calls examples](https://docs.bitquery.io/v1/docs/Examples/tron/smartContractCalls) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/tron/transaction.md b/docs/Examples/tron/transaction.md index 0ee044f..163123e 100644 --- a/docs/Examples/tron/transaction.md +++ b/docs/Examples/tron/transaction.md @@ -1,3 +1,24 @@ +--- +title: "Tron Transactions API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron transactions. Get transactions by block, height, fees, energy, and counts." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transaction API Our Tron Transaction API provides detailed information about transactions from Tron Blockchain. @@ -36,4 +57,12 @@ This query retrieves details of a specific Tron blockchain transaction at height } ``` -This query retrieves the count of transactions that occurred at a specific block height (53420256) on the Tron blockchain. \ No newline at end of file +This query retrieves the count of transactions that occurred at a specific block height (53420256) on the Tron blockchain. + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron transfers examples](https://docs.bitquery.io/v1/docs/Examples/tron/transfers) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/tron/transfers.md b/docs/Examples/tron/transfers.md index 9ff35f2..acd003f 100644 --- a/docs/Examples/tron/transfers.md +++ b/docs/Examples/tron/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Tron Transfers API Examples — Bitquery GraphQL" +description: "Example GraphQL queries for Tron token transfers. Get latest transfers, TRC-20 flows, and inflow/outflow totals." +keywords: [Tron API examples, Tron GraphQL queries, Bitquery] +--- + + + + + + + + + + + + + + + + # Transfer API Our Tron Transfers API rpovides detailed information about token transfers made on the Tron blockchain. @@ -129,3 +150,11 @@ query MyQuery { } } ``` + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron address examples](https://docs.bitquery.io/v1/docs/Examples/tron/address) +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Avalanche/address.md b/docs/Schema/Avalanche/address.md index 5505ace..465e0e1 100644 --- a/docs/Schema/Avalanche/address.md +++ b/docs/Schema/Avalanche/address.md @@ -1,5 +1,6 @@ --- title: "Avalanche Address API" +description: "Look up Avalanche address balances and activity." --- @@ -115,4 +116,13 @@ query ($network: EthereumNetwork!) { `reward`: The reward that the miner received for mining the block. -`reward_usd`: The reward that the miner received for mining the block in USD. \ No newline at end of file +`reward_usd`: The reward that the miner received for mining the block in USD. + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/arguments.md b/docs/Schema/Avalanche/arguments.md index 47eaf6f..a716b60 100644 --- a/docs/Schema/Avalanche/arguments.md +++ b/docs/Schema/Avalanche/arguments.md @@ -1,5 +1,6 @@ --- title: "Avalanche Arguments API" +description: "Query smart contract call and event arguments on Avalanche." --- @@ -80,4 +81,13 @@ The following are available fields for the `arguments`: - `smartContractSignature`: returns signature of contract method or event - `success`: - `transaction`: returns transaction information -- `value`: returns value of method or event argument \ No newline at end of file +- `value`: returns value of method or event argument + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/blocks.md b/docs/Schema/Avalanche/blocks.md index 26c539e..f1fa1f9 100644 --- a/docs/Schema/Avalanche/blocks.md +++ b/docs/Schema/Avalanche/blocks.md @@ -1,5 +1,6 @@ --- title: "Avalanche Blocks API" +description: "Query Avalanche C-Chain blocks, gas, rewards, and transaction counts." --- @@ -104,3 +105,12 @@ query ($network: EthereumNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Da `blame`: The blame score of the block. `totalDifficulty`: The total difficulty of the block + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/calls.md b/docs/Schema/Avalanche/calls.md index 923470e..c693a3b 100644 --- a/docs/Schema/Avalanche/calls.md +++ b/docs/Schema/Avalanche/calls.md @@ -1,5 +1,6 @@ --- title: "Avalanche Calls API" +description: "Query smart contract calls on Avalanche." --- @@ -113,3 +114,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not - `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/coinpath.md b/docs/Schema/Avalanche/coinpath.md index 1e6358e..5dfc858 100644 --- a/docs/Schema/Avalanche/coinpath.md +++ b/docs/Schema/Avalanche/coinpath.md @@ -1,5 +1,6 @@ --- title: "Avalanche Coinpath API" +description: "Trace fund flows on Avalanche with coinpath." --- @@ -152,3 +153,12 @@ The following are available fields for the `coinpath`: - `sender`: returns information about the sender. - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/overview.md b/docs/Schema/Avalanche/overview.md index 84210ec..460562c 100644 --- a/docs/Schema/Avalanche/overview.md +++ b/docs/Schema/Avalanche/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Avalanche API — Blockchain Data Schema | Bitquery" +description: "Access Avalanche blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Avalanche API, Avalanche GraphQL, Avalanche blockchain data, Bitquery] --- + + + + + + + + + + + + + + + Avalanche is an open-source platform for building dApps that uses its own consensus protocol (Avalanche Consensus). Bitquery offers a Avalanche C-Chain [explorer](https://explorer.bitquery.io/avalanche) to view Avalanche data easily. @@ -20,4 +38,12 @@ __typename Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/Avalanche/transactions.md b/docs/Schema/Avalanche/transactions.md index 903ae97..bdba6b6 100644 --- a/docs/Schema/Avalanche/transactions.md +++ b/docs/Schema/Avalanche/transactions.md @@ -1,5 +1,6 @@ --- title: "Avalanche Transactions API" +description: "Query Avalanche transactions and attributes." --- @@ -176,4 +177,13 @@ query ($network: EthereumNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim `to`: The address of the recipient of the transaction. -`txType`: The type of the transaction \ No newline at end of file +`txType`: The type of the transaction + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Avalanche/transfers.md b/docs/Schema/Avalanche/transfers.md index 676caae..31eec13 100644 --- a/docs/Schema/Avalanche/transfers.md +++ b/docs/Schema/Avalanche/transfers.md @@ -1,5 +1,6 @@ --- title: "Avalanche Transfers API" +description: "Query AVAX and token transfers on Avalanche." --- @@ -154,4 +155,13 @@ query ($network: EthereumNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim `success`: Whether the transfer was successful. -`entityId`: The ID of the transfer. \ No newline at end of file +`entityId`: The ID of the transfer. + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) +- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Cronos/activeaddresses.md b/docs/Schema/Cronos/activeaddresses.md index 71c2e9d..2d035f3 100644 --- a/docs/Schema/Cronos/activeaddresses.md +++ b/docs/Schema/Cronos/activeaddresses.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Active Addresses API" +description: "Query Cronos active addresses data using Bitquery GraphQL API. Get active address counts and time-bucketed activity." +keywords: ["Cronos API", "Cronos Active Addresses", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the cronos blockchain. @@ -40,3 +61,11 @@ The following are available fields for the `activeAddresses`: - `address`: returns the address and its annotation. - `count`: returns the aggregate count of active addresses. - `countBigInt`: returns the aggregate count of active addresses in `BigInt` format. + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/address.md b/docs/Schema/Cronos/address.md index 2cab2e4..6337384 100644 --- a/docs/Schema/Cronos/address.md +++ b/docs/Schema/Cronos/address.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Address API" +description: "Query Cronos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Cronos API", "Cronos Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` allows us to retrieve information about a specific address. @@ -48,3 +69,11 @@ The following are available fields for the address: - `balance`: Returns the current balance of the address. - `balances`: Returns the balance history of the address. - `smartContract`: Returns details if the address is that of a smart contract. + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/addresstats.md b/docs/Schema/Cronos/addresstats.md index 73f6f21..786f6a3 100644 --- a/docs/Schema/Cronos/addresstats.md +++ b/docs/Schema/Cronos/addresstats.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Address Stats API" +description: "Query Cronos address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["Cronos API", "Cronos Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. @@ -41,3 +62,11 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/arguments.md b/docs/Schema/Cronos/arguments.md index fdf7e03..1df9049 100644 --- a/docs/Schema/Cronos/arguments.md +++ b/docs/Schema/Cronos/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Arguments API" +description: "Query Cronos GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Cronos API", "Cronos Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. @@ -70,3 +91,11 @@ The following are available fields for the `arguments`: - `success`: - `transaction`: returns transaction information - `value`: returns value of method or event argument + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/blocks.md b/docs/Schema/Cronos/blocks.md index 7233e96..2dc3e07 100644 --- a/docs/Schema/Cronos/blocks.md +++ b/docs/Schema/Cronos/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Blocks API" +description: "Query Cronos blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Cronos API", "Cronos Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The `blocks` field allows us to retrieve information about the blocks from the cronos blockchain. @@ -68,3 +89,10 @@ Blocks data can be filtered using following arguments: - `totalDifficulty`: returns the total difficulty. - `transactionCount`: returns the number of transactions included in the block. +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/coinpath.md b/docs/Schema/Cronos/coinpath.md index 0b950ff..aea02c0 100644 --- a/docs/Schema/Cronos/coinpath.md +++ b/docs/Schema/Cronos/coinpath.md @@ -1,3 +1,23 @@ +--- +title: "Cronos Coinpath API" +description: "Query Cronos coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Cronos API", "Cronos Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Coinpath @@ -35,4 +55,11 @@ The following are available fields for the `coinpath`: - `receiver`: returns information about the receiver. - `sender`: returns information about the sender. - `transaction`: returns transaction details. -- `transactions`: returns attributes of transactions. \ No newline at end of file +- `transactions`: returns attributes of transactions. + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/dextrades.md b/docs/Schema/Cronos/dextrades.md index 28b3638..2384e3e 100644 --- a/docs/Schema/Cronos/dextrades.md +++ b/docs/Schema/Cronos/dextrades.md @@ -1,3 +1,24 @@ +--- +title: "Cronos DEX Trades API" +description: "Query Cronos DEX trades data using Bitquery GraphQL API. Get DEX swaps, pools, amounts, and trader addresses." +keywords: ["Cronos API", "Cronos DEX Trades", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. @@ -127,4 +148,11 @@ The following are available fields for the `dexTrades`: - `tradeAmount`: returns the trade amount in the base currency. - `tradeIndex`: returns the index of the trade in the transaction. - `transaction`: returns information about the transaction in which the trade was executed. - \ No newline at end of file + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/overview.md b/docs/Schema/Cronos/overview.md index 40df2ae..021753d 100644 --- a/docs/Schema/Cronos/overview.md +++ b/docs/Schema/Cronos/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Cronos API — Blockchain Data Schema | Bitquery" +description: "Access Cronos blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Cronos API, Cronos GraphQL, Cronos blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery Cronos API offers access to indexed data from the cronos blockchain via GraphQL API for developers. @@ -19,3 +37,11 @@ query { ``` Let's dive in and explore the cronos data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/Cronos/references.md b/docs/Schema/Cronos/references.md index 24a6444..7037a21 100644 --- a/docs/Schema/Cronos/references.md +++ b/docs/Schema/Cronos/references.md @@ -1,3 +1,23 @@ +--- +title: "Cronos References API" +description: "Query Cronos schema references data using Bitquery GraphQL API. Get reference data and lookup tables for this network schema." +keywords: ["Cronos API", "Cronos References", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # References @@ -44,4 +64,12 @@ References can be filtered using following arguments: - `smartContract`: - `smartContractSignature`: - `success`: -- `transaction`: \ No newline at end of file +- `transaction`: + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/smartcontractcalls.md b/docs/Schema/Cronos/smartcontractcalls.md index 5451eee..6870a2f 100644 --- a/docs/Schema/Cronos/smartcontractcalls.md +++ b/docs/Schema/Cronos/smartcontractcalls.md @@ -1,3 +1,23 @@ +--- +title: "Cronos Smart Contract Calls API" +description: "Query Cronos smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Cronos API", "Cronos Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Calls @@ -82,4 +102,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContract`: returns details of smart contract - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not -- `transaction`: returns details of the transaction in which smart contract call was executed \ No newline at end of file +- `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/smartcontractevents.md b/docs/Schema/Cronos/smartcontractevents.md index e7d91cc..2b34dba 100644 --- a/docs/Schema/Cronos/smartcontractevents.md +++ b/docs/Schema/Cronos/smartcontractevents.md @@ -1,3 +1,23 @@ +--- +title: "Cronos Smart Contract Events API" +description: "Query Cronos smart contract events data using Bitquery GraphQL API. Get contract events, logs, topics, and decoded payloads." +keywords: ["Cronos API", "Cronos Smart Contract Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Events @@ -69,3 +89,11 @@ Smart Contract Events can be filtered using following arguments: - `smartContract`: returns details of smart contract on which event happened - `smartContractEvent`: returns details about smart contract event like name, signature, and signature hash - `transaction`: returns details about transaction which emitted smart contract event + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/transactions.md b/docs/Schema/Cronos/transactions.md index 75a5283..3700055 100644 --- a/docs/Schema/Cronos/transactions.md +++ b/docs/Schema/Cronos/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Transactions API" +description: "Query Cronos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Cronos API", "Cronos Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions Bitquery `transactions` API allows you to retrieve all the blockchain transactions from cronos Blockchain. @@ -110,4 +131,12 @@ Transactions can be filtered using following arguments: - `sender`: returns address of sender of a particular transaction - `success`: returns if transaction is success or not - `to`: returns address to which of a particular transaction was sent -- `txType`: returns transaction type \ No newline at end of file +- `txType`: returns transaction type + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Cronos/transfers.md b/docs/Schema/Cronos/transfers.md index 0c1b56f..253aa68 100644 --- a/docs/Schema/Cronos/transfers.md +++ b/docs/Schema/Cronos/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Cronos Transfers API" +description: "Query Cronos transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Cronos API", "Cronos Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers Bitquery `transfers` API allows you to retrieve currency or token transfers from cronos Blockchain. @@ -111,4 +132,12 @@ Data retrieved using `transfers` can be filtered using following arguments: - `receiver`: returns receiver of a particular transfer - `sender`: returns sender of a particular transfer - `success`: returns boolean value for success of a particular transfer -- `transaction`: returns details of transaction in which a particular transfer \ No newline at end of file +- `transaction`: returns details of transaction in which a particular transfer + +## Related Resources + +- [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cronos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/Cronos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/Dash/addressstats.md b/docs/Schema/Dash/addressstats.md index 5a947fe..3d89415 100644 --- a/docs/Schema/Dash/addressstats.md +++ b/docs/Schema/Dash/addressstats.md @@ -1,5 +1,6 @@ --- title: Dash Address Stats API +description: "Query address statistics and history on Dash." --- @@ -56,3 +57,12 @@ Here is an example that demonstrates how to retrieve statistics about a specific - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/blocks.md b/docs/Schema/Dash/blocks.md index ad6b111..98cefdc 100644 --- a/docs/Schema/Dash/blocks.md +++ b/docs/Schema/Dash/blocks.md @@ -1,5 +1,6 @@ --- title: Dash Blocks API +description: "Query Dash blocks, difficulty, and transaction counts." --- @@ -87,3 +88,12 @@ The following fields are available for the `blocks`: - `minimum`: returns maximum of selected measurable fields of Dash blocks - `timestamp`: returns block timestamp - `transactionCount`: returns number of transactions in block + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/coinpath.md b/docs/Schema/Dash/coinpath.md index be6f494..c280b22 100644 --- a/docs/Schema/Dash/coinpath.md +++ b/docs/Schema/Dash/coinpath.md @@ -1,5 +1,6 @@ --- title: Dash Coinpath API +description: "Track fund flows up to any depth on Dash with coinpath." --- @@ -55,3 +56,12 @@ The following are available fields for the `coinpath`: - `sender`: returns information about the sender. - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/inputs.md b/docs/Schema/Dash/inputs.md index 245cc7e..4d24e96 100644 --- a/docs/Schema/Dash/inputs.md +++ b/docs/Schema/Dash/inputs.md @@ -1,5 +1,6 @@ --- title: Dash Inputs API +description: "Query transaction inputs and fund flow on Dash." --- @@ -94,4 +95,13 @@ The following are available fields for the `inputs`: - `outputTransaction`: returns output transaction for this input - `transaction`: returns information about transaction of this input - `value`: returns input value -- `valueDecimal`: returns input value as decimal +- `valueDecimal`: returns input value as decimal + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/omnitransactions.md b/docs/Schema/Dash/omnitransactions.md index a967909..93f4799 100644 --- a/docs/Schema/Dash/omnitransactions.md +++ b/docs/Schema/Dash/omnitransactions.md @@ -1,5 +1,6 @@ --- title: Dash OmniTransactions API +description: "Query Omni layer transactions on Dash." --- @@ -95,3 +96,12 @@ The following are available fields for the `omniTransactions`: - `typeInt`: returns type as Int - `valid`: - `version`: returns version + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/omnitransfers.md b/docs/Schema/Dash/omnitransfers.md index 3355952..04d01b6 100644 --- a/docs/Schema/Dash/omnitransfers.md +++ b/docs/Schema/Dash/omnitransfers.md @@ -1,5 +1,6 @@ --- title: Dash OmniTransfers API +description: "Query Omni layer transfers on Dash." --- @@ -106,3 +107,12 @@ Omni Transfers can be filtered using the following arguments: - `type`: returns type of transfer - `typeInt`: returns type as Int - `value`: returns value + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/outputs.md b/docs/Schema/Dash/outputs.md index ddba1d5..bad1e91 100644 --- a/docs/Schema/Dash/outputs.md +++ b/docs/Schema/Dash/outputs.md @@ -1,5 +1,6 @@ --- title: Dash Outputs API +description: "Query transaction outputs and fund flow on Dash." --- @@ -102,3 +103,12 @@ The following are available fields for the `outputs`: - `transaction`: returns transaction ID Hash - `value`: returns output value - `valueDecimal`: returns output as decimal + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dash/overview.md b/docs/Schema/Dash/overview.md index 52a1f96..163d8e0 100644 --- a/docs/Schema/Dash/overview.md +++ b/docs/Schema/Dash/overview.md @@ -1,6 +1,25 @@ --- sidebar_position: 1 +title: "Dash API — Blockchain Data Schema | Bitquery" +description: "Access Dash blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Dash API, Dash GraphQL, Dash blockchain data, Bitquery] --- + + + + + + + + + + + + + + + + # Dash API Overview Bitquery API offers access to indexed data from the Dash blockchain through the Dash schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -17,4 +36,11 @@ query { } ``` -Let's dive in and explore the Dash data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the Dash data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/Schema/Dash/transactions.md b/docs/Schema/Dash/transactions.md index fcbf7c4..6ba7168 100644 --- a/docs/Schema/Dash/transactions.md +++ b/docs/Schema/Dash/transactions.md @@ -1,5 +1,6 @@ --- title: Dash Transactions API +description: "Query Dash transactions, fees, inputs, and outputs." --- @@ -119,3 +120,12 @@ The following are available fields for the `transactions`: - `txversion`: returns version of transaction - `txVsize`: returns vsize of transaction - `txWeight`: returns transaction weight + +## Related Resources + +- [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/addressstats.md b/docs/Schema/Dogecoin/addressstats.md index 631f8fa..07dc2d6 100644 --- a/docs/Schema/Dogecoin/addressstats.md +++ b/docs/Schema/Dogecoin/addressstats.md @@ -1,5 +1,6 @@ --- title: Dogecoin Address Stats API +description: "Query address statistics and history on Dogecoin." --- @@ -56,3 +57,12 @@ Here is an example that demonstrates how to retrieve statistics about a specific - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/blocks.md b/docs/Schema/Dogecoin/blocks.md index 1a248bc..bcd2449 100644 --- a/docs/Schema/Dogecoin/blocks.md +++ b/docs/Schema/Dogecoin/blocks.md @@ -1,5 +1,6 @@ --- title: Dogecoin Blocks API +description: "Query Dogecoin blocks, difficulty, and transaction counts." --- @@ -87,3 +88,12 @@ The following fields are available for the `blocks`: - `minimum`: returns maximum of selected measurable fields of Dogecoin Blocks - `timestamp`: returns block timestamp - `transactionCount`: returns number of transactions in block + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/coinpath.md b/docs/Schema/Dogecoin/coinpath.md index 33187d2..c73fade 100644 --- a/docs/Schema/Dogecoin/coinpath.md +++ b/docs/Schema/Dogecoin/coinpath.md @@ -1,5 +1,6 @@ --- title: Dash Coinpath API +description: "Track fund flows up to any depth on Dogecoin with coinpath." --- @@ -55,3 +56,12 @@ The following are available fields for the `coinpath`: - `sender`: returns information about the sender. - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/inputs.md b/docs/Schema/Dogecoin/inputs.md index f7c8bb3..1a71468 100644 --- a/docs/Schema/Dogecoin/inputs.md +++ b/docs/Schema/Dogecoin/inputs.md @@ -1,5 +1,6 @@ --- title: Dogecoin Inputs API +description: "Query transaction inputs and fund flow on Dogecoin." --- @@ -94,4 +95,13 @@ The following are available fields for the `inputs`: - `outputTransaction`: returns output transaction for this input - `transaction`: returns information about transaction of this input - `value`: returns input value -- `valueDecimal`: returns input value as decimal +- `valueDecimal`: returns input value as decimal + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/omnitransactions.md b/docs/Schema/Dogecoin/omnitransactions.md index 26a0fee..c4474cc 100644 --- a/docs/Schema/Dogecoin/omnitransactions.md +++ b/docs/Schema/Dogecoin/omnitransactions.md @@ -1,5 +1,6 @@ --- title: Dogecoin OmniTransactions API +description: "Query Omni layer transactions on Dogecoin." --- @@ -95,3 +96,12 @@ The following are available fields for the `omniTransactions`: - `typeInt`: returns type as Int - `valid`: - `version`: returns version + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/outputs.md b/docs/Schema/Dogecoin/outputs.md index 705bd15..6f69b53 100644 --- a/docs/Schema/Dogecoin/outputs.md +++ b/docs/Schema/Dogecoin/outputs.md @@ -1,5 +1,6 @@ --- title: Dogecoin Outputs API +description: "Query transaction outputs and fund flow on Dogecoin." --- @@ -102,3 +103,12 @@ The following are available fields for the `outputs`: - `transaction`: returns transaction ID Hash - `value`: returns output value - `valueDecimal`: returns output as decimal + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Dogecoin/overview.md b/docs/Schema/Dogecoin/overview.md index eae53d2..91b5125 100644 --- a/docs/Schema/Dogecoin/overview.md +++ b/docs/Schema/Dogecoin/overview.md @@ -1,6 +1,25 @@ --- sidebar_position: 1 +title: "Dogecoin API — Blockchain Data Schema | Bitquery" +description: "Access Dogecoin blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Dogecoin API, Dogecoin GraphQL, Dogecoin blockchain data, Bitquery] --- + + + + + + + + + + + + + + + + # Dogecoin API Overview Bitquery API offers access to indexed data from the Dogecoin blockchain through the Dogecoin schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -17,4 +36,12 @@ query { } ``` -Let's dive in and explore the Dogecoin data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the Dogecoin data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/Schema/Dogecoin/transactions.md b/docs/Schema/Dogecoin/transactions.md index b4f9602..2380688 100644 --- a/docs/Schema/Dogecoin/transactions.md +++ b/docs/Schema/Dogecoin/transactions.md @@ -1,5 +1,6 @@ --- title: Dogecoin Transactions API +description: "Query Dogecoin transactions, fees, inputs, and outputs." --- @@ -119,3 +120,12 @@ The following are available fields for the `transactions`: - `txversion`: returns version of transaction - `txVsize`: returns vsize of transaction - `txWeight`: returns transaction weight + +## Related Resources + +- [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) +- [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) +- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/activeaddresses.md b/docs/Schema/Polygon/activeaddresses.md index 7670409..743e024 100644 --- a/docs/Schema/Polygon/activeaddresses.md +++ b/docs/Schema/Polygon/activeaddresses.md @@ -1,5 +1,6 @@ --- title: Polygon Active Addresses API +description: "Get active addresses on Polygon (Matic), including metrics for tokens and NFTs." --- @@ -71,4 +72,13 @@ The following are available fields for the `activeAddresses`: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/address.md b/docs/Schema/Polygon/address.md index 930637d..3416db7 100644 --- a/docs/Schema/Polygon/address.md +++ b/docs/Schema/Polygon/address.md @@ -1,5 +1,6 @@ --- title: Polygon Token, Smart contract Details API +description: "Get Polygon token and smart contract details for addresses, including supply and contract attributes." --- @@ -80,4 +81,13 @@ The following are available fields for the address: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/addresstats.md b/docs/Schema/Polygon/addresstats.md index d01b96f..8e724a4 100644 --- a/docs/Schema/Polygon/addresstats.md +++ b/docs/Schema/Polygon/addresstats.md @@ -1,5 +1,6 @@ --- title: Polygon Address Balance and Activity Summary +description: "Get Polygon (Matic) token supply and activity summaries. Retrieve smart contract property details." --- @@ -71,4 +72,13 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/arguments.md b/docs/Schema/Polygon/arguments.md index 80f03cb..e8359f5 100644 --- a/docs/Schema/Polygon/arguments.md +++ b/docs/Schema/Polygon/arguments.md @@ -1,5 +1,6 @@ --- title: Polygon Argument API +description: "Decode Polygon smart contract event and call arguments with filtering and aggregation in real time or historically." --- @@ -112,4 +113,13 @@ The following are available fields for the `arguments`: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/balance.md b/docs/Schema/Polygon/balance.md index 51b02c5..d8d612f 100644 --- a/docs/Schema/Polygon/balance.md +++ b/docs/Schema/Polygon/balance.md @@ -1,5 +1,6 @@ --- title: Polygon Address Balance API +description: "Get balance or balance history for any address or smart contract on the Polygon blockchain." --- @@ -68,4 +69,13 @@ The following are available fields for the address: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/blocks.md b/docs/Schema/Polygon/blocks.md index eeed6e5..cf1aac5 100644 --- a/docs/Schema/Polygon/blocks.md +++ b/docs/Schema/Polygon/blocks.md @@ -1,5 +1,6 @@ --- title: Polygon Blocks API +description: "Get latest or historical blocks on Polygon (Matic). Retrieve transactions, fees, miner details, and more." --- @@ -100,4 +101,12 @@ Blocks data can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Polygon/coinpath.md b/docs/Schema/Polygon/coinpath.md index 6954aaf..0632848 100644 --- a/docs/Schema/Polygon/coinpath.md +++ b/docs/Schema/Polygon/coinpath.md @@ -1,5 +1,6 @@ --- title: Polygon Coinpath® API +description: "Trace tokens on Polygon and learn about sources, destinations, and parties involved in transactions." --- @@ -148,4 +149,13 @@ The following are available fields for the `coinpath`: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/dextrades.md b/docs/Schema/Polygon/dextrades.md index 6f9e11f..55543fc 100644 --- a/docs/Schema/Polygon/dextrades.md +++ b/docs/Schema/Polygon/dextrades.md @@ -1,5 +1,6 @@ --- title: Polygon DEX Trade API +description: "Get real-time and historical DEX trades, price, and OHLC data on Polygon DEXs such as QuickSwap, SushiSwap, and Uniswap." --- @@ -162,4 +163,13 @@ The following are available fields for the `dexTrades`: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/overview.md b/docs/Schema/Polygon/overview.md index efee269..5695b59 100644 --- a/docs/Schema/Polygon/overview.md +++ b/docs/Schema/Polygon/overview.md @@ -1,26 +1,24 @@ --- sidebar_position: 1 -title: Polygon API Overview +title: "Polygon API — Blockchain Data Schema | Bitquery" +description: "Access Polygon blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Polygon API, Polygon GraphQL, Polygon blockchain data, Bitquery] --- - - - + + + - - - - - - + + - - + + @@ -50,3 +48,11 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T Let's dive in and explore the Polygon API in following chapters. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/Polygon/references.md b/docs/Schema/Polygon/references.md index b01ce3c..c379e7d 100644 --- a/docs/Schema/Polygon/references.md +++ b/docs/Schema/Polygon/references.md @@ -1,3 +1,22 @@ +--- +title: "Polygon References API" +description: "Filter and query reference fields linked to Polygon smart contract arguments, calls, and events." +--- + + + + + + + + + + + + + + + # References @@ -52,4 +71,13 @@ References can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/smartcontractcalls.md b/docs/Schema/Polygon/smartcontractcalls.md index 35f0df2..1fd044f 100644 --- a/docs/Schema/Polygon/smartcontractcalls.md +++ b/docs/Schema/Polygon/smartcontractcalls.md @@ -1,5 +1,6 @@ --- title: Polygon Smart Contract Call API +description: "Get decoded smart contract call details with arguments from the Polygon blockchain." --- @@ -116,4 +117,13 @@ Smart Contract Calls can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/smartcontractevents.md b/docs/Schema/Polygon/smartcontractevents.md index a05da86..aecbe73 100644 --- a/docs/Schema/Polygon/smartcontractevents.md +++ b/docs/Schema/Polygon/smartcontractevents.md @@ -1,5 +1,6 @@ --- title: Polygon Smart Contract Events API +description: "Get decoded real-time and historical Polygon smart contract events with decoded argument details." --- @@ -103,3 +104,12 @@ Smart Contract Events can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. ::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/transactions.md b/docs/Schema/Polygon/transactions.md index a15f988..428554d 100644 --- a/docs/Schema/Polygon/transactions.md +++ b/docs/Schema/Polygon/transactions.md @@ -1,5 +1,6 @@ --- title: Polygon Transaction API +description: "Get real-time and historical Polygon (Matic) blockchain transaction details with fee information." --- @@ -146,4 +147,13 @@ Transactions can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/Polygon/transfers.md b/docs/Schema/Polygon/transfers.md index 326d36e..46b1e56 100644 --- a/docs/Schema/Polygon/transfers.md +++ b/docs/Schema/Polygon/transfers.md @@ -1,10 +1,10 @@ --- title: Polygon Token Transfer API -description: Get real time and historical Token Transfer details for tokens on the Polygon blockchain using our Transfer API, including transfers for individual addresses. +description: "Get real-time and historical token transfer details for Polygon (Matic), including transfers for individual addresses." keywords: [polygon api, polygon python api, polygon transfers, polygon transactions, polygon nft api, polygon scan api, polygon matic api, polygon api docs, polygon crypto api, polygon blockchain api,matic network api] --- - + ## Transfers @@ -146,4 +146,13 @@ Data retrieved using `transfers` can be filtered using following arguments: Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/algorand/address.md b/docs/Schema/algorand/address.md index 9ef0d05..07e4fe3 100644 --- a/docs/Schema/algorand/address.md +++ b/docs/Schema/algorand/address.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Address API" +description: "Query Algorand address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Algorand API", "Algorand Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` field allows us to fetch information about a specific address or a list of addresses from the Algorand blockchain. @@ -37,4 +58,12 @@ The following are available fields for the `address`: - `rewards`: returns the current reward for the address. - `round`: returns the current round. - `smartContract`: returns information about a smart contract if it exists at the address. -- `status`: returns the current status of the address. \ No newline at end of file +- `status`: returns the current status of the address. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/arguments.md b/docs/Schema/algorand/arguments.md index 44ffaca..4fd8bad 100644 --- a/docs/Schema/algorand/arguments.md +++ b/docs/Schema/algorand/arguments.md @@ -1,3 +1,23 @@ +--- +title: "Algorand Arguments API" +description: "Query Algorand GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Algorand API", "Algorand Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Arguments @@ -77,4 +97,12 @@ The following are available fields for the `arguments`: - `transaction`: returns information of transaction where call happened - `txSender`: returns information of transaction sender - `txType`: returns transaction type in which transfer happened -- `value`: returns value of argument \ No newline at end of file +- `value`: returns value of argument + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/blocks.md b/docs/Schema/algorand/blocks.md index a1ac30e..de01eca 100644 --- a/docs/Schema/algorand/blocks.md +++ b/docs/Schema/algorand/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Blocks API" +description: "Query Algorand blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Algorand API", "Algorand Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The `blocks` field allows us to retrieve details about blocks from Algorand blockchain. @@ -76,4 +97,12 @@ Blocks can be filtered using the following arguments: - `timestamp`: returns timestamp of the block - `txnRoot`: returns transaction root - `upgradeApprove`: returns number of vote for the current proposal -- `upgradePropose`: returns proposed upgrade \ No newline at end of file +- `upgradePropose`: returns proposed upgrade + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/coinpath.md b/docs/Schema/algorand/coinpath.md index 622bde6..3744d2f 100644 --- a/docs/Schema/algorand/coinpath.md +++ b/docs/Schema/algorand/coinpath.md @@ -1,3 +1,23 @@ +--- +title: "Algorand Coinpath API" +description: "Query Algorand coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Algorand API", "Algorand Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Coinpath @@ -35,4 +55,11 @@ The following are available fields for the `coinpath`: - `receiver`: returns information about the receiver. - `sender`: returns information about the sender. - `transaction`: returns transaction details. -- `transactions`: returns attributes of transactions. \ No newline at end of file +- `transactions`: returns attributes of transactions. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/overview.md b/docs/Schema/algorand/overview.md index 49796c8..491b60e 100644 --- a/docs/Schema/algorand/overview.md +++ b/docs/Schema/algorand/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Algorand API — Blockchain Data Schema | Bitquery" +description: "Access Algorand blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Algorand API, Algorand GraphQL, Algorand blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery API offers access to indexed data from the Algorand blockchain. @@ -19,3 +37,11 @@ to fetch data from Algorand blockchain, you need to provide the `network` argume You can also fetch data from Algorand Betanet (`algorand_betanet`). Let's dive in and explore the Algorand data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Algorand API examples](https://docs.bitquery.io/v1/docs/Examples/algorand) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/algorand/smartContractCalls.md b/docs/Schema/algorand/smartContractCalls.md index d4a8fc6..0499c10 100644 --- a/docs/Schema/algorand/smartContractCalls.md +++ b/docs/Schema/algorand/smartContractCalls.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Smart Contract Calls API" +description: "Query Algorand smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Algorand API", "Algorand Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Smart Contract Calls The `smartContractCalls` field allows you to retrieve smart contract calls made to any smart contract on Algorand blockchain. @@ -52,3 +73,11 @@ Here's an exmaple that demonstrates how to use `smartContractCalls` query: - `transaction`: returns information of transaction where call was executed - `txSender`: returns information of transaction sender - `txType`: returns transaction type in which transfer happened + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/transactions.md b/docs/Schema/algorand/transactions.md index 557ffc4..ba0b5c3 100644 --- a/docs/Schema/algorand/transactions.md +++ b/docs/Schema/algorand/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Transactions API" +description: "Query Algorand transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Algorand API", "Algorand Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Algorand Transactions API can be used to get information about transactions, such as the sender, the recipient, the amount, the fee, and the timestamp. Here are the fields in the schema. @@ -108,4 +129,12 @@ group: A filter that groups the results by a specific field. `poolerror`: The pool error associated with the transaction. -`subtype`: The subtype of the transaction. \ No newline at end of file +`subtype`: The subtype of the transaction. + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/algorand/transfers.md b/docs/Schema/algorand/transfers.md index 3ca328b..ec86a66 100644 --- a/docs/Schema/algorand/transfers.md +++ b/docs/Schema/algorand/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Algorand Transfers API" +description: "Query Algorand transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Algorand API", "Algorand Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The `transfers` field allows us to fetch details about token transfers from the Algorand blockchain. @@ -79,3 +100,11 @@ Transfer data can be filtered using the following arguments - `sender`: returns address and annotation for sender of the transfer - `transaction`: returns details of transaction in which transfer occurred - `transferType`: returns transfer type + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Algorand Coinpath API](https://docs.bitquery.io/v1/docs/Schema/algorand/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/binance_smart_chain/activeaddresses.md b/docs/Schema/binance_smart_chain/activeaddresses.md index db5c63e..ac7a23d 100644 --- a/docs/Schema/binance_smart_chain/activeaddresses.md +++ b/docs/Schema/binance_smart_chain/activeaddresses.md @@ -1,5 +1,6 @@ --- title: BNB Active Addresses API +description: "Query active addresses and counts on BNB Smart Chain." --- @@ -63,3 +64,12 @@ The following are available fields for the `activeAddresses`: - `address`: returns the address and its annotation. - `count`: returns the aggregate count of active addresses. - `countBigInt`: returns the aggregate count of active addresses in `BigInt` format. + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/address.md b/docs/Schema/binance_smart_chain/address.md index cd22155..69630d2 100644 --- a/docs/Schema/binance_smart_chain/address.md +++ b/docs/Schema/binance_smart_chain/address.md @@ -1,5 +1,6 @@ --- title: BNB Address API +description: "Look up address balances, annotations, and smart contract details on BNB Smart Chain." --- @@ -69,3 +70,12 @@ The following are available fields for the address: - `balance`: Returns the current balance of the address. - `balances`: Returns the balance history of the address. - `smartContract`: Returns details if the address is that of a smart contract. + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/addresstats.md b/docs/Schema/binance_smart_chain/addresstats.md index 05b6e4d..0d0c22f 100644 --- a/docs/Schema/binance_smart_chain/addresstats.md +++ b/docs/Schema/binance_smart_chain/addresstats.md @@ -1,5 +1,6 @@ --- title: BNB Address Stats API +description: "Get address balance history and aggregate statistics on BNB Smart Chain." --- @@ -63,3 +64,12 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/arguments.md b/docs/Schema/binance_smart_chain/arguments.md index a8fd170..f2d4614 100644 --- a/docs/Schema/binance_smart_chain/arguments.md +++ b/docs/Schema/binance_smart_chain/arguments.md @@ -1,5 +1,6 @@ --- title: BNB Arguments API +description: "Query event and call arguments for BNB Smart Chain smart contracts." --- @@ -92,3 +93,12 @@ The following are available fields for the `arguments`: - `success`: - `transaction`: returns transaction information - `value`: returns value of method or event argument + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/blocks.md b/docs/Schema/binance_smart_chain/blocks.md index 65ae839..81339c6 100644 --- a/docs/Schema/binance_smart_chain/blocks.md +++ b/docs/Schema/binance_smart_chain/blocks.md @@ -1,5 +1,6 @@ --- title: BNB Blocks API +description: "Query BNB Smart Chain blocks, including transactions, fees, and miner details." --- @@ -91,3 +92,12 @@ Blocks data can be filtered using following arguments: - `transactionCountBigInt`: - `uncleCount`: - `uncleCountBigInt`: + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/coinpath.md b/docs/Schema/binance_smart_chain/coinpath.md index 0f4e851..2a80f6e 100644 --- a/docs/Schema/binance_smart_chain/coinpath.md +++ b/docs/Schema/binance_smart_chain/coinpath.md @@ -1,5 +1,6 @@ --- title: BNB Coinpath API +description: "Track fund flows up to any depth on BNB Smart Chain with coinpath." --- @@ -56,3 +57,12 @@ The following are available fields for the `coinpath`: - `sender`: returns information about the sender. - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/dextrades.md b/docs/Schema/binance_smart_chain/dextrades.md index 48e0dc3..1fb709e 100644 --- a/docs/Schema/binance_smart_chain/dextrades.md +++ b/docs/Schema/binance_smart_chain/dextrades.md @@ -1,5 +1,6 @@ --- title: BNB DEX Trades API +description: "Query DEX trades, liquidity pools, and pairs on BNB Smart Chain." --- @@ -148,3 +149,12 @@ The following are available fields for the `dexTrades`: - `tradeAmount`: returns the trade amount in the base currency. - `tradeIndex`: returns the index of the trade in the transaction. - `transaction`: returns information about the transaction in which the trade was executed. + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/overview.md b/docs/Schema/binance_smart_chain/overview.md index 572eac4..d728b9e 100644 --- a/docs/Schema/binance_smart_chain/overview.md +++ b/docs/Schema/binance_smart_chain/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "BNB Smart Chain API — Blockchain Data Schema | Bitquery" +description: "Access BNB Smart Chain blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [BNB Smart Chain API, BNB Smart Chain GraphQL, BNB Smart Chain blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # BNB API Overview Bitquery API offers access to indexed data from the BNB blockchain via GraphQL API for developers. @@ -19,3 +37,11 @@ query { ``` Let's dive in and explore the BNB data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/binance_smart_chain/references.md b/docs/Schema/binance_smart_chain/references.md index 24a6444..dfcd096 100644 --- a/docs/Schema/binance_smart_chain/references.md +++ b/docs/Schema/binance_smart_chain/references.md @@ -1,3 +1,22 @@ +--- +title: "BNB Smart Chain References API" +description: "Filter and query reference fields linked to BNB Smart Chain smart contract arguments, calls, and events." +--- + + + + + + + + + + + + + + + # References @@ -44,4 +63,13 @@ References can be filtered using following arguments: - `smartContract`: - `smartContractSignature`: - `success`: -- `transaction`: \ No newline at end of file +- `transaction`: + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/smartcontractcalls.md b/docs/Schema/binance_smart_chain/smartcontractcalls.md index 5d0e15d..9bbb3d1 100644 --- a/docs/Schema/binance_smart_chain/smartcontractcalls.md +++ b/docs/Schema/binance_smart_chain/smartcontractcalls.md @@ -1,5 +1,6 @@ --- title: BNB Smart Contract Calls API +description: "Query decoded smart contract calls and calldata on BNB Smart Chain." --- @@ -103,3 +104,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not - `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/smartcontractevents.md b/docs/Schema/binance_smart_chain/smartcontractevents.md index a1354be..830f556 100644 --- a/docs/Schema/binance_smart_chain/smartcontractevents.md +++ b/docs/Schema/binance_smart_chain/smartcontractevents.md @@ -1,5 +1,6 @@ --- title: BNB Smart Contract Events API +description: "Query decoded smart contract events and arguments on BNB Smart Chain." --- @@ -84,3 +85,12 @@ Smart Contract Events can be filtered using following arguments: - `smartContract`: returns details of smart contract on which event happened - `smartContractEvent`: returns details about smart contract event like name, signature, and signature hash - `transaction`: returns details about transaction which emitted smart contract event + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/transactions.md b/docs/Schema/binance_smart_chain/transactions.md index 1a57bd5..eb7de69 100644 --- a/docs/Schema/binance_smart_chain/transactions.md +++ b/docs/Schema/binance_smart_chain/transactions.md @@ -1,5 +1,6 @@ --- title: BNB Transactions API +description: "Query BNB Smart Chain transactions, senders, fees, and success status." --- @@ -131,4 +132,13 @@ Transactions can be filtered using following arguments: - `sender`: returns address of sender of a particular transaction - `success`: returns if transaction is success or not - `to`: returns address to which of a particular transaction was sent -- `txType`: returns transaction type \ No newline at end of file +- `txType`: returns transaction type + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/binance_smart_chain/transfers.md b/docs/Schema/binance_smart_chain/transfers.md index d3201cb..423f863 100644 --- a/docs/Schema/binance_smart_chain/transfers.md +++ b/docs/Schema/binance_smart_chain/transfers.md @@ -1,5 +1,6 @@ --- title: BNB Transfers API +description: "Query token and native transfers on BNB Smart Chain with filtering and sorting." --- @@ -132,4 +133,13 @@ Data retrieved using `transfers` can be filtered using following arguments: - `receiver`: returns receiver of a particular transfer - `sender`: returns sender of a particular transfer - `success`: returns boolean value for success of a particular transfer -- `transaction`: returns details of transaction in which a particular transfer \ No newline at end of file +- `transaction`: returns details of transaction in which a particular transfer + +## Related Resources + +- [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/bitcoin/addressstats.md b/docs/Schema/bitcoin/addressstats.md index 18f5304..6d4b27b 100644 --- a/docs/Schema/bitcoin/addressstats.md +++ b/docs/Schema/bitcoin/addressstats.md @@ -1,5 +1,6 @@ --- title: Bitcoin Address Stats API +description: "Get address balance and history on the Bitcoin blockchain. Also, get address balance and history for tokens on the Bitcoin blockchain." --- @@ -55,3 +56,11 @@ Here is an example that demonstrates how to retrieve statistics about a specific - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/blocks.md b/docs/Schema/bitcoin/blocks.md index a17cea4..dcd428f 100644 --- a/docs/Schema/bitcoin/blocks.md +++ b/docs/Schema/bitcoin/blocks.md @@ -1,5 +1,6 @@ --- title: Bitcoin Blocks API +description: "Get information on blocks on the Bitcoin blockchain. Also, get information on blocks for tokens on the Bitcoin blockchain." --- @@ -87,3 +88,11 @@ The following fields are available for the `blocks`: - `minimum`: returns maximum of selected measurable fields of Bitcoin Blocks - `timestamp`: returns block timestamp - `transactionCount`: returns number of transactions in block + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/coinpath.md b/docs/Schema/bitcoin/coinpath.md index 22f439a..b10bbeb 100644 --- a/docs/Schema/bitcoin/coinpath.md +++ b/docs/Schema/bitcoin/coinpath.md @@ -1,5 +1,6 @@ --- title: Bitcoin Coinpath API +description: "Track flow of funds up to any depth on the Bitcoin blockchain. Also, get information on blocks for tokens or NFTs on the Bitcoin blockchain." --- @@ -55,3 +56,11 @@ The following are available fields for the `coinpath`: - `sender`: returns information about the sender. - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/inputs.md b/docs/Schema/bitcoin/inputs.md index 270ecd6..dd00a70 100644 --- a/docs/Schema/bitcoin/inputs.md +++ b/docs/Schema/bitcoin/inputs.md @@ -1,5 +1,6 @@ --- title: Bitcoin Inputs API +description: "Get information on wallet inputs and fund flow on the Bitcoin blockchain. Also, get information on blocks for tokens or NFTs on the Bitcoin blockchain." --- @@ -95,3 +96,11 @@ The following are available fields for the `inputs`: - `transaction`: returns information about transaction of this input - `value`: returns input value - `valueDecimal`: returns input value as decimal + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/omnitransactions.md b/docs/Schema/bitcoin/omnitransactions.md index e01ce1a..cafe598 100644 --- a/docs/Schema/bitcoin/omnitransactions.md +++ b/docs/Schema/bitcoin/omnitransactions.md @@ -1,5 +1,6 @@ --- title: Bitcoin OmniTransactions API +description: "Get information on Omni layer transactions and wallets on the Bitcoin blockchain. Also, get information on tokens or NFTs on the Bitcoin blockchain." --- @@ -95,3 +96,11 @@ The following are available fields for the `omniTransactions`: - `typeInt`: returns type as Int - `valid`: - `version`: returns version + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/omnitransfers.md b/docs/Schema/bitcoin/omnitransfers.md index 756326a..9648e2f 100644 --- a/docs/Schema/bitcoin/omnitransfers.md +++ b/docs/Schema/bitcoin/omnitransfers.md @@ -1,5 +1,6 @@ --- title: Bitcoin OmniTransfers API +description: "Get information on Omni layer transfers on the Bitcoin blockchain. Also, get information on tokens or NFTs on the Bitcoin blockchain." --- @@ -106,3 +107,11 @@ Omni Transfers can be filtered using the following arguments: - `type`: returns type of transfer - `typeInt`: returns type as Int - `value`: returns value + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/outputs.md b/docs/Schema/bitcoin/outputs.md index bd1b38f..bc877c7 100644 --- a/docs/Schema/bitcoin/outputs.md +++ b/docs/Schema/bitcoin/outputs.md @@ -1,5 +1,6 @@ --- title: Bitcoin Outputs API +description: "Get information on wallet outputs and fund flow on the Bitcoin blockchain. Also, get information on blocks for tokens or NFTs on the Bitcoin blockchain." --- @@ -102,3 +103,11 @@ The following are available fields for the `outputs`: - `transaction`: returns transaction ID Hash - `value`: returns output value - `valueDecimal`: returns output as decimal + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/overview.md b/docs/Schema/bitcoin/overview.md index dfa0509..7418c1e 100644 --- a/docs/Schema/bitcoin/overview.md +++ b/docs/Schema/bitcoin/overview.md @@ -1,6 +1,25 @@ --- sidebar_position: 1 +title: "Bitcoin API — Blockchain Data Schema | Bitquery" +description: "Access Bitcoin blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Bitcoin API, Bitcoin GraphQL, Bitcoin blockchain data, Bitquery] --- + + + + + + + + + + + + + + + + # Bitcoin API Overview Bitquery API offers access to indexed data from the Bitcoin blockchain through the bitcoin schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -17,4 +36,12 @@ query { } ``` -Let's dive in and explore the Bitcoin data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the Bitcoin data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/bitcoin/transactions.md b/docs/Schema/bitcoin/transactions.md index e47a3ba..0d80c8c 100644 --- a/docs/Schema/bitcoin/transactions.md +++ b/docs/Schema/bitcoin/transactions.md @@ -1,5 +1,6 @@ --- title: Bitcoin Transactions API +description: "Get information on transaction details and wallets on the Bitcoin blockchain. Also, get information on blocks for tokens or NFTs on the Bitcoin blockchain." --- @@ -119,3 +120,11 @@ The following are available fields for the `transactions`: - `txversion`: returns version of transaction - `txVsize`: returns vsize of transaction - `txWeight`: returns transaction weight + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/cardano/address.md b/docs/Schema/cardano/address.md index fc284bc..e310a76 100644 --- a/docs/Schema/cardano/address.md +++ b/docs/Schema/cardano/address.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Address API" +description: "Query Cardano address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Cardano API", "Cardano Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The Address API schema returns information about a wallet. The schema includes the following fields: @@ -45,4 +66,12 @@ query MyQuery { `address` The address of the wallet - \ No newline at end of file + + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/addressstats.md b/docs/Schema/cardano/addressstats.md index 42ec874..d61c1ca 100644 --- a/docs/Schema/cardano/addressstats.md +++ b/docs/Schema/cardano/addressstats.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Address Stats API" +description: "Query Cardano address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["Cardano API", "Cardano Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # AddressStats The AddressStats API schema returns information about a wallet on its inflows, outflows and activity. The schema includes the following fields: @@ -41,3 +62,11 @@ The address of the wallet Additional options for the query, such as sorting and pagination. + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/blocks.md b/docs/Schema/cardano/blocks.md index 182b946..3cd406b 100644 --- a/docs/Schema/cardano/blocks.md +++ b/docs/Schema/cardano/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Blocks API" +description: "Query Cardano blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Cardano API", "Cardano Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks @@ -79,4 +100,12 @@ The version of the block. The VRF key for the block. - \ No newline at end of file + + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/coinpath.md b/docs/Schema/cardano/coinpath.md index 013bb51..a228dd7 100644 --- a/docs/Schema/cardano/coinpath.md +++ b/docs/Schema/cardano/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Coinpath API" +description: "Query Cardano coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Cardano API", "Cardano Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath Coinpath APIs are a set of money-tracing APIs that help you track funds from one address to another. @@ -58,4 +79,11 @@ query MyQuery { Filtering Coinpath - \ No newline at end of file + + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/inputsOutputs.md b/docs/Schema/cardano/inputsOutputs.md index f6f23f3..402095c 100644 --- a/docs/Schema/cardano/inputsOutputs.md +++ b/docs/Schema/cardano/inputsOutputs.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Inputs and Outputs API" +description: "Query Cardano inputs outputs data using Bitquery GraphQL API. Get transaction inputs, outputs, and UTXO-style movements." +keywords: ["Cardano API", "Cardano Inputs and Outputs", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Inputs and Outputs The Inputs and Outputs API schema returns information about the inputs and outputs of a transaction. The schema includes the following fields: @@ -99,4 +120,12 @@ The index of the output within the transaction. `outputValue` The amount of ADA transferred out of the output. - \ No newline at end of file + + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/mints.md b/docs/Schema/cardano/mints.md index 6c5fdb6..6ac58cb 100644 --- a/docs/Schema/cardano/mints.md +++ b/docs/Schema/cardano/mints.md @@ -1,3 +1,23 @@ +--- +title: "Cardano Mints API" +description: "Query Cardano mints data using Bitquery GraphQL API. Get mint events, policies, assets, and recipients." +keywords: ["Cardano API", "Cardano Mints", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Mints @@ -47,4 +67,12 @@ query MyQuery { `txIndex`: The index of the transaction in the block. `value`: The amount of tokens minted. - \ No newline at end of file + + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cardano/overview.md b/docs/Schema/cardano/overview.md index c83a7e8..5acded7 100644 --- a/docs/Schema/cardano/overview.md +++ b/docs/Schema/cardano/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Cardano API — Blockchain Data Schema | Bitquery" +description: "Access Cardano blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Cardano API, Cardano GraphQL, Cardano blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery provides as [explorer](https://explorer.bitquery.io/cardano) for you to easily view data on Cardano. @@ -21,4 +39,11 @@ to fetch data from Algorand blockchain, you need to provide the `network` argume ``` -Let's dive in and explore the cardano data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the cardano data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/cardano/transactions.md b/docs/Schema/cardano/transactions.md index 2a02459..08fe93e 100644 --- a/docs/Schema/cardano/transactions.md +++ b/docs/Schema/cardano/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Cardano Transactions API" +description: "Query Cardano transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Cardano API", "Cardano Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Transactions API schema returns a list of transactions that occurred on the Cardano blockchain within a specified date range. The schema includes the following fields: @@ -122,3 +143,11 @@ The total amount of ADA withdrawn from the transaction. The address of the input that sent the funds. + +## Related Resources + +- [Cardano schema overview](https://docs.bitquery.io/v1/docs/Schema/cardano/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cardano Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cardano/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/activeaddresses.md b/docs/Schema/celo/activeaddresses.md index b1ac595..dd39555 100644 --- a/docs/Schema/celo/activeaddresses.md +++ b/docs/Schema/celo/activeaddresses.md @@ -1,3 +1,24 @@ +--- +title: "Celo Active Addresses API" +description: "Query Celo active addresses data using Bitquery GraphQL API. Get active address counts and time-bucketed activity." +keywords: ["Celo API", "Celo Active Addresses", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the Celo blockchain. @@ -40,3 +61,11 @@ The following are available fields for the `activeAddresses`: - `address`: returns the address and its annotation. - `count`: returns the aggregate count of active addresses. - `countBigInt`: returns the aggregate count of active addresses in `BigInt` format. + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/address.md b/docs/Schema/celo/address.md index ca50c17..1be6bb6 100644 --- a/docs/Schema/celo/address.md +++ b/docs/Schema/celo/address.md @@ -1,3 +1,24 @@ +--- +title: "Celo Address API" +description: "Query Celo address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Celo API", "Celo Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` allows us to retrieve information about a specific address. @@ -48,3 +69,11 @@ The following are available fields for the address: - `balance`: Returns the current balance of the address. - `balances`: Returns the balance history of the address. - `smartContract`: Returns details if the address is that of a smart contract. + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/addresstats.md b/docs/Schema/celo/addresstats.md index 209fb2e..f93417b 100644 --- a/docs/Schema/celo/addresstats.md +++ b/docs/Schema/celo/addresstats.md @@ -1,3 +1,24 @@ +--- +title: "Celo Address Stats API" +description: "Query Celo address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["Celo API", "Celo Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. @@ -41,3 +62,11 @@ Here is an example that demonstrates how to retrieve statistics about a smart co - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/arguments.md b/docs/Schema/celo/arguments.md index f168676..1b8c483 100644 --- a/docs/Schema/celo/arguments.md +++ b/docs/Schema/celo/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Celo Arguments API" +description: "Query Celo GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Celo API", "Celo Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. @@ -71,3 +92,11 @@ The following are available fields for the `arguments`: - `success`: - `transaction`: returns transaction information - `value`: returns value of method or event argument + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/blocks.md b/docs/Schema/celo/blocks.md index d929520..b96a76a 100644 --- a/docs/Schema/celo/blocks.md +++ b/docs/Schema/celo/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Celo Blocks API" +description: "Query Celo blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Celo API", "Celo Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The `blocks` field allows us to retrieve information about the blocks from the Ethereum blockchain. @@ -70,3 +91,11 @@ Blocks data can be filtered using following arguments: - `transactionCountBigInt`: - `uncleCount`: - `uncleCountBigInt`: + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/coinpath.md b/docs/Schema/celo/coinpath.md index 0b950ff..e310b2d 100644 --- a/docs/Schema/celo/coinpath.md +++ b/docs/Schema/celo/coinpath.md @@ -1,3 +1,23 @@ +--- +title: "Celo Coinpath API" +description: "Query Celo coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Celo API", "Celo Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Coinpath @@ -35,4 +55,11 @@ The following are available fields for the `coinpath`: - `receiver`: returns information about the receiver. - `sender`: returns information about the sender. - `transaction`: returns transaction details. -- `transactions`: returns attributes of transactions. \ No newline at end of file +- `transactions`: returns attributes of transactions. + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/dextrades.md b/docs/Schema/celo/dextrades.md index 109635b..20e9c16 100644 --- a/docs/Schema/celo/dextrades.md +++ b/docs/Schema/celo/dextrades.md @@ -1,3 +1,24 @@ +--- +title: "Celo DEX Trades API" +description: "Query Celo DEX trades data using Bitquery GraphQL API. Get DEX swaps, pools, amounts, and trader addresses." +keywords: ["Celo API", "Celo DEX Trades", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. @@ -127,4 +148,11 @@ The following are available fields for the `dexTrades`: - `tradeAmount`: returns the trade amount in the base currency. - `tradeIndex`: returns the index of the trade in the transaction. - `transaction`: returns information about the transaction in which the trade was executed. - \ No newline at end of file + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/overview.md b/docs/Schema/celo/overview.md index 8ab63f9..b9e0489 100644 --- a/docs/Schema/celo/overview.md +++ b/docs/Schema/celo/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Celo API — Blockchain Data Schema | Bitquery" +description: "Access Celo blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Celo API, Celo GraphQL, Celo blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery API offers access to indexed data from the Celo blockchain to enable blockchain data retrieval via GraphQL API for developers. @@ -21,3 +39,11 @@ query { ``` Let's dive in and explore the Ethereum data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/celo/references.md b/docs/Schema/celo/references.md index 24a6444..144b001 100644 --- a/docs/Schema/celo/references.md +++ b/docs/Schema/celo/references.md @@ -1,3 +1,23 @@ +--- +title: "Celo References API" +description: "Query Celo schema references data using Bitquery GraphQL API. Get reference data and lookup tables for this network schema." +keywords: ["Celo API", "Celo References", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # References @@ -44,4 +64,12 @@ References can be filtered using following arguments: - `smartContract`: - `smartContractSignature`: - `success`: -- `transaction`: \ No newline at end of file +- `transaction`: + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/smartcontractcalls.md b/docs/Schema/celo/smartcontractcalls.md index 0e2365b..ab60701 100644 --- a/docs/Schema/celo/smartcontractcalls.md +++ b/docs/Schema/celo/smartcontractcalls.md @@ -1,3 +1,23 @@ +--- +title: "Celo Smart Contract Calls API" +description: "Query Celo smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Celo API", "Celo Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Calls @@ -82,4 +102,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContract`: returns details of smart contract - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not -- `transaction`: returns details of the transaction in which smart contract call was executed \ No newline at end of file +- `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/smartcontractevents.md b/docs/Schema/celo/smartcontractevents.md index 37164d7..762b93a 100644 --- a/docs/Schema/celo/smartcontractevents.md +++ b/docs/Schema/celo/smartcontractevents.md @@ -1,3 +1,23 @@ +--- +title: "Celo Smart Contract Events API" +description: "Query Celo smart contract events data using Bitquery GraphQL API. Get contract events, logs, topics, and decoded payloads." +keywords: ["Celo API", "Celo Smart Contract Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Events @@ -69,3 +89,11 @@ Smart Contract Events can be filtered using following arguments: - `smartContract`: returns details of smart contract on which event happened - `smartContractEvent`: returns details about smart contract event like name, signature, and signature hash - `transaction`: returns details about transaction which emitted smart contract event + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/transactions.md b/docs/Schema/celo/transactions.md index c89b82e..113f6b9 100644 --- a/docs/Schema/celo/transactions.md +++ b/docs/Schema/celo/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Celo Transactions API" +description: "Query Celo transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Celo API", "Celo Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions Celo `Transactions` API allows you to retrieve all the blockchain transactions from Celo Blockchain. @@ -110,4 +131,12 @@ Transactions can be filtered using following arguments: - `sender`: returns address of sender of a particular transaction - `success`: returns if transaction is success or not - `to`: returns address to which of a particular transaction was sent -- `txType`: returns transaction type \ No newline at end of file +- `txType`: returns transaction type + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/celo/transfers.md b/docs/Schema/celo/transfers.md index 456e1ef..e14d186 100644 --- a/docs/Schema/celo/transfers.md +++ b/docs/Schema/celo/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Celo Transfers API" +description: "Query Celo transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Celo API", "Celo Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers Celo `transfers` API allows you to retrieve currency or token transfers from Celo Blockchain. @@ -111,4 +132,12 @@ Data retrieved using `transfers` can be filtered using following arguments: - `receiver`: returns receiver of a particular transfer - `sender`: returns sender of a particular transfer - `success`: returns boolean value for success of a particular transfer -- `transaction`: returns details of transaction in which a particular transfer \ No newline at end of file +- `transaction`: returns details of transaction in which a particular transfer + +## Related Resources + +- [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Celo Coinpath API](https://docs.bitquery.io/v1/docs/Schema/celo/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/activeaddress.md b/docs/Schema/conflux/activeaddress.md index 2d235f1..e887804 100644 --- a/docs/Schema/conflux/activeaddress.md +++ b/docs/Schema/conflux/activeaddress.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Active Address API" +description: "Query Conflux active address data using Bitquery GraphQL API. Get active address metrics and participation." +keywords: ["Conflux API", "Conflux Active Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Active Address API Conflux Active Address API gives you information on the active addresses on the Conflux chain. The following are the fields on the schema: @@ -33,3 +54,11 @@ The address of the wallet `annotation` Any information about the address + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/address.md b/docs/Schema/conflux/address.md index da45525..c4cf33a 100644 --- a/docs/Schema/conflux/address.md +++ b/docs/Schema/conflux/address.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Address API" +description: "Query Conflux address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Conflux API", "Conflux Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Address API The Address API schema returns information about a wallet. The schema includes the following fields: @@ -31,3 +52,11 @@ The address of the wallet - `address`: returns the address and its annotation (if an annotation is given to that address). - `balance`: returns the current balance of the address. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/arguments.md b/docs/Schema/conflux/arguments.md index 89cf3f4..ce0e145 100644 --- a/docs/Schema/conflux/arguments.md +++ b/docs/Schema/conflux/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Arguments API" +description: "Query Conflux GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Conflux API", "Conflux Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Arguments API Bitquery's Conflux Arguments API gives you information on the arguments passed during on chain updates to functions. Below are the fields in the schema: @@ -82,3 +103,11 @@ The following are available fields for the `arguments`: - `success`: - `transaction`: returns transaction information - `value`: returns value of method or event argument + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/blocks.md b/docs/Schema/conflux/blocks.md index 6cc0041..5ab479b 100644 --- a/docs/Schema/conflux/blocks.md +++ b/docs/Schema/conflux/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Blocks API" +description: "Query Conflux blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Conflux API", "Conflux Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Blocks API Bitquery's Conflux blocks API provides information on blocks in the Conflux chain. Below are the fields in the schema: @@ -67,3 +88,11 @@ query ($network: ConfluxNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime `powerQuality`: The PoW quality of the block. `blame`: The blame score of the block. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/coinpath.md b/docs/Schema/conflux/coinpath.md index bd29f18..87f79c2 100644 --- a/docs/Schema/conflux/coinpath.md +++ b/docs/Schema/conflux/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Coinpath API" +description: "Query Conflux coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Conflux API", "Conflux Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Coinpath API The Conflux Coinpath API allows you to get the money flow for an address on the Conflux blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. @@ -123,3 +144,10 @@ The Conflux Coinpath API allows you to get the money flow for an address on the - **depth** The depth of the coinpath. - **count** The number of transactions in the coinpath. - **block** The block in which the first transaction in the coinpath was included. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/overview.md b/docs/Schema/conflux/overview.md index 85f5e62..f2a6947 100644 --- a/docs/Schema/conflux/overview.md +++ b/docs/Schema/conflux/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Conflux API — Blockchain Data Schema | Bitquery" +description: "Access Conflux blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Conflux API, Conflux GraphQL, Conflux blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery provides APIs to access Conflux data. You can get info on the conflux chain which uses the Tree-Graph consensus, a consensus method with parallel-processing to reach distributed consensus. @@ -10,4 +28,11 @@ Bitquery supports conflux_hydra, conflux_tethys and conflux_oceanus. These APIs provide details on transactions, trades, addresses and so on. The easiest way to start is through the [Conflux Hydra Explorer](https://explorer.bitquery.io/conflux_hydra) -![conflux](/img/ide/conflux.png) \ No newline at end of file +![conflux](/img/ide/conflux.png) + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) diff --git a/docs/Schema/conflux/smartcontractcalls.md b/docs/Schema/conflux/smartcontractcalls.md index f34cfbc..f5b9654 100644 --- a/docs/Schema/conflux/smartcontractcalls.md +++ b/docs/Schema/conflux/smartcontractcalls.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Smart Contract Calls API" +description: "Query Conflux smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Conflux API", "Conflux Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Smart Contract Calls API Bitquery's Conflux Calls API captures information on smart contract calls made on chain . Below are the fields in this schema: @@ -83,3 +104,11 @@ query ($network: ConfluxNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - **callDepth** : The call depth of the call. - **success** : A `true` /`false` value to indicate if the call was successful - **external** : Whether the call was external or internal. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/smartcontractevents.md b/docs/Schema/conflux/smartcontractevents.md index bafd16a..ee64834 100644 --- a/docs/Schema/conflux/smartcontractevents.md +++ b/docs/Schema/conflux/smartcontractevents.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Smart Contract Events API" +description: "Query Conflux smart contract events data using Bitquery GraphQL API. Get contract events, logs, topics, and decoded payloads." +keywords: ["Conflux API", "Conflux Smart Contract Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Smart Contract Events API ``` @@ -73,3 +94,11 @@ Smart contract events can be filtered using the following arguments: - The number of times the event was emitted. - **transaction** - The hash of the transaction that emitted the event. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/transactions.md b/docs/Schema/conflux/transactions.md index f7d2829..94867f6 100644 --- a/docs/Schema/conflux/transactions.md +++ b/docs/Schema/conflux/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Transactions API" +description: "Query Conflux transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Conflux API", "Conflux Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Transactions API ``` @@ -106,3 +127,11 @@ query ($network: ConfluxNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - A annotation field that contains any information about the address - **success** - Whether the transaction was successful. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/conflux/transfers.md b/docs/Schema/conflux/transfers.md index 3277a02..cc94721 100644 --- a/docs/Schema/conflux/transfers.md +++ b/docs/Schema/conflux/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Conflux Transfers API" +description: "Query Conflux transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Conflux API", "Conflux Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Conflux Transfers API Bitquery's conflux transfers API gives you information on the asset transfers on conflux. The following are the fields in the schema: @@ -122,3 +143,11 @@ query ($network: ConfluxNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Dat - The ID of the entity that was transferred, if the transfer is for a token. - **success** - A `true` or `false` value that indicates whether the transfer was successful. + +## Related Resources + +- [Conflux schema overview](https://docs.bitquery.io/v1/docs/Schema/conflux/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Conflux Coinpath API](https://docs.bitquery.io/v1/docs/Schema/conflux/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/address.md b/docs/Schema/cosmos/address.md index 1ae5331..582fdb3 100644 --- a/docs/Schema/cosmos/address.md +++ b/docs/Schema/cosmos/address.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Address API" +description: "Query Cosmos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Cosmos API", "Cosmos Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` field allows us to retrieve basic information about a particular address or list of address like balance, annotation, etc. @@ -31,3 +52,11 @@ Address data can be filtered using following arguments: - `balance`: returns native currency balance of the address - `tokensInfo`: returns token info + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/attributes.md b/docs/Schema/cosmos/attributes.md index 428f4b2..80aa24d 100644 --- a/docs/Schema/cosmos/attributes.md +++ b/docs/Schema/cosmos/attributes.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Attributes API" +description: "Query Cosmos attributes data using Bitquery GraphQL API. Get event and message attributes for filtering and display." +keywords: ["Cosmos API", "Cosmos Attributes", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Attributes The `attributes` field allows us to retrieve information about the attributes from cosmos networks. @@ -74,3 +95,11 @@ Attributes can be filtered using following arguments: - `transaction`: returns transaction info where message is included - `value`: returns value of attribute - `valueIndex`: returns index of attribute + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/blocks.md b/docs/Schema/cosmos/blocks.md index d13e764..61d1817 100644 --- a/docs/Schema/cosmos/blocks.md +++ b/docs/Schema/cosmos/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Blocks API" +description: "Query Cosmos blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Cosmos API", "Cosmos Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The `blocks` field allows us to fetch details about the blocks from Cosmos blockchain. @@ -53,3 +74,11 @@ Blocks data can be filtered using following arguments: - `minimum`: returns minimum for selected measurable field of Cosmos blocks - `proposer`: returns address and annotation (if available) of block proposer - `timestamp`: returns block timestamp + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/coinpath.md b/docs/Schema/cosmos/coinpath.md index 14cb604..039c058 100644 --- a/docs/Schema/cosmos/coinpath.md +++ b/docs/Schema/cosmos/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Coinpath API" +description: "Query Cosmos coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Cosmos API", "Cosmos Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The coinpath API provides detailed information about the money flow using coinpath technology. @@ -29,3 +50,10 @@ The coinpath API provides detailed information about the money flow using coinpa - `receiver`: returns receiver address - `sender`: returns sender address - `transaction`: returns message of transfer happened + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/messages.md b/docs/Schema/cosmos/messages.md index 64d4a6e..7b34ff5 100644 --- a/docs/Schema/cosmos/messages.md +++ b/docs/Schema/cosmos/messages.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Messages API" +description: "Query Cosmos messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +keywords: ["Cosmos API", "Cosmos Messages", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Messages The `messages` field allows us to retrieve detaild information about messages from Cosmos blockchain. @@ -63,3 +84,11 @@ Here is an example that demonstrates retrieving message from Cosmos hub: - `success`: returns success of transaction as boolean - `transaction`: returns transaction formation where message is included - `type`: returns type of message + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/overview.md b/docs/Schema/cosmos/overview.md index 76bd4a2..dfbe973 100644 --- a/docs/Schema/cosmos/overview.md +++ b/docs/Schema/cosmos/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Cosmos API — Blockchain Data Schema | Bitquery" +description: "Access Cosmos blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Cosmos API, Cosmos GraphQL, Cosmos blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery empowers developers by offering comprehensive access to indexed data from the Cosmos blockchain through our user-friendly and efficient GraphQL API. @@ -25,3 +43,11 @@ Bitquery supports following networks: - `crypto_mainnet`: Crypto.org mainnet Let's dive in and explore the Cosmos data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Cosmos API examples](https://docs.bitquery.io/v1/docs/Examples/cosmos) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/cosmos/transactions.md b/docs/Schema/cosmos/transactions.md index afe6b3c..879565d 100644 --- a/docs/Schema/cosmos/transactions.md +++ b/docs/Schema/cosmos/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Transactions API" +description: "Query Cosmos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Cosmos API", "Cosmos Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transaction The Transactions API returns information about transactions on Cosmos network. @@ -114,3 +135,11 @@ Here is an example that demonstrates how to fetch 10 latest transactions: - `success`: returns success of the transaction as boolean - `type`: returns type of transaction + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/cosmos/transfer.md b/docs/Schema/cosmos/transfer.md index 6ad8f0c..d62ebb1 100644 --- a/docs/Schema/cosmos/transfer.md +++ b/docs/Schema/cosmos/transfer.md @@ -1,3 +1,24 @@ +--- +title: "Cosmos Transfer API" +description: "Query Cosmos transfer data using Bitquery GraphQL API. Get transfers, denoms, senders, receivers, and transaction context." +keywords: ["Cosmos API", "Cosmos Transfer", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The Transfers API returns information about token transfers on Cosmos network. @@ -120,3 +141,11 @@ Here's an example that demostrates how to fetch 10 latest transfers: - `value`: returns value of the transfer - `valueDecimal`: returns value as decimal + +## Related Resources + +- [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cosmos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/cosmos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/address.md b/docs/Schema/elrond/address.md index 47085f6..1bd6cea 100644 --- a/docs/Schema/elrond/address.md +++ b/docs/Schema/elrond/address.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Address API" +description: "Query Elrond address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Elrond API", "Elrond Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Transaction API Below are the fields in the schema: @@ -8,4 +29,12 @@ Below are the fields in the schema: ```
-## Fields \ No newline at end of file +## Fields + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/blocks.md b/docs/Schema/elrond/blocks.md index be19367..5d5303a 100644 --- a/docs/Schema/elrond/blocks.md +++ b/docs/Schema/elrond/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Blocks API" +description: "Query Elrond blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Elrond API", "Elrond Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Blocks API The MultiversX Blocks API allows you to query information about blocks on the MultiversX blockchain. You can use this API to get information about the block hash, height, timestamp, and other details.Below are the fields in the schema: @@ -50,3 +71,11 @@ query ($network: ElrondNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) - `previousBlockHash`: The hash of the previous block. - `publicKeyBitmap`: The public key bitmap of the block. - `proposer`: The address of the block proposer. + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/blockvalidators.md b/docs/Schema/elrond/blockvalidators.md index 4ae68db..d0b9947 100644 --- a/docs/Schema/elrond/blockvalidators.md +++ b/docs/Schema/elrond/blockvalidators.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Block Validators API" +description: "Query Elrond validators data using Bitquery GraphQL API. Get validators associated with blocks and consensus roles." +keywords: ["Elrond API", "Elrond Block Validators", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Block Validators API The MultiversX Block Validators API allows you to query information about the validators of a block on the MultiversX blockchain. A validator is a node that has been elected to participate in the consensus process and produce blocks. The API can be used to get information about the validators of a block, including their addresses, shards, and public key bitmaps. @@ -63,3 +84,11 @@ query ($network: ElrondNetwork!, $limit: Int!, $offset: Int!, $blockHash: String - `sizeTxs`: The total size of the transactions in the block. - `transactionCount`: The number of transactions in the block. - `publicKeyBitmap`: The public key bitmap of the block. + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/callresults.md b/docs/Schema/elrond/callresults.md index 2be9e63..aeb65c4 100644 --- a/docs/Schema/elrond/callresults.md +++ b/docs/Schema/elrond/callresults.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Call Results API" +description: "Query Elrond call results data using Bitquery GraphQL API. Get smart contract call results and return data." +keywords: ["Elrond API", "Elrond Call Results", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX CallResults API The MultiversX CallResults API allows you to query information about call results on the MultiversX blockchain. A call result is a record of a function call that was made to a smart contract. The API can be used to get information about the sender, receiver, value, type, and other details of a call result. @@ -119,3 +140,11 @@ query ($network: ElrondNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date - **data:** The data that was passed to the call result. - **dataOperation:** The data operation that was performed by the call result. - **transaction:** The transaction that the call result belongs to + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/miniblocks.md b/docs/Schema/elrond/miniblocks.md index 0d918f3..63c5217 100644 --- a/docs/Schema/elrond/miniblocks.md +++ b/docs/Schema/elrond/miniblocks.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Miniblocks API" +description: "Query Elrond miniblocks data using Bitquery GraphQL API. Get miniblock headers, shards, and ordering." +keywords: ["Elrond API", "Elrond Miniblocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Miniblocks API MultiversX uses a concept called mini-blocks to handle cross-shard transactions. A mini-block is a small block that contains only cross-shard transactions. These mini-blocks are then aggregated into regular blocks, which are mined on each shard. @@ -77,3 +98,11 @@ query ($network: ElrondNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime `receiverShard`: The shard that received the mini-block. `type`: The type of the mini-block, for example `TxBlock` `senderBlock`: The block that sent the mini-block. + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/notarizedblocks.md b/docs/Schema/elrond/notarizedblocks.md index 688cccb..2bf7f60 100644 --- a/docs/Schema/elrond/notarizedblocks.md +++ b/docs/Schema/elrond/notarizedblocks.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Notarized Blocks API" +description: "Query Elrond notarized blocks data using Bitquery GraphQL API. Get notarized block records and consensus metadata." +keywords: ["Elrond API", "Elrond Notarized Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Notarized Blocks API The MultiversX Notarized Blocks API allows you to query information about notarized blocks on the MultiversX blockchain. A notarized block is a block that has been verified by a set of validators. The API can be used to get information about notarized blocks, including their hashes, epochs, heights, and public key bitmaps. @@ -60,3 +81,11 @@ query ($network: ElrondNetwork!, $limit: Int!, $offset: Int!, $blockHash: String - `publicKeyBitmap`: The public key bitmap of the block. - `shard`: The shard where the block was mined. - `sizeTxs`: The total size of the transactions in the block + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/operations.md b/docs/Schema/elrond/operations.md index ede75c2..871c5c6 100644 --- a/docs/Schema/elrond/operations.md +++ b/docs/Schema/elrond/operations.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Operations API" +description: "Query Elrond operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +keywords: ["Elrond API", "Elrond Operations", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Operations API The MultiversX Operations API allows you to query information about operations on the MultiversX blockchain. You can use this API to get information about the sender, receiver, type, action, and other details of an operation. @@ -90,3 +111,11 @@ query ($network: ElrondNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - `receiverBlockHash`: The hash of the block that received the miniblock. - `receiverShard`: The shard where the block that received the miniblock resides. - `type`: The type of the miniblock. + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/overview.md b/docs/Schema/elrond/overview.md index 4eb758b..8c52d69 100644 --- a/docs/Schema/elrond/overview.md +++ b/docs/Schema/elrond/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Elrond API — Blockchain Data Schema | Bitquery" +description: "Access Elrond blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Elrond API, Elrond GraphQL, Elrond blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview MultiversX API offers access to indexed data from the MultiversX network including shards, block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as shard information, transaction details, events, token transfers, and other relevant information. @@ -17,4 +35,11 @@ query MyQuery { ``` -Let's dive in and explore the elrond data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the elrond data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/elrond/transactions.md b/docs/Schema/elrond/transactions.md index 9247e77..593af9d 100644 --- a/docs/Schema/elrond/transactions.md +++ b/docs/Schema/elrond/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Transactions API" +description: "Query Elrond transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Elrond API", "Elrond Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Transaction API he MultiversX Transactions API allows you to query information about transactions on the MultiversX blockchain. You can use this API to get information about the sender, receiver, amount, currency, and other details of a transaction. @@ -110,3 +131,11 @@ query ($network: ElrondNetwork!,$from: ISO8601DateTime, $till: ISO8601DateTime) - **action:** The type of action performed by the transaction. This includes the following fields: - `description`: A description of the action indicating for example if it was a Transfer - `category`: The category of the action for example `esdtNft` + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/elrond/transfers.md b/docs/Schema/elrond/transfers.md index acc2cab..0abf038 100644 --- a/docs/Schema/elrond/transfers.md +++ b/docs/Schema/elrond/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Elrond Transfers API" +description: "Query Elrond transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Elrond API", "Elrond Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # MultiversX Transfers API The MultiversX Transfers API gets information about the sender, receiver, amount, currency, and other details related to transfers on the network. Below are the fields in the schema: @@ -90,3 +111,11 @@ query ($network: ElrondNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date - `signature`: The signature of the transfer. This is used to verify the authenticity of the transfer. - `status`: The status of the transfer. - **action:** The type of action performed by the transfer, e.g `fee` transfer . + +## Related Resources + +- [Elrond schema overview](https://docs.bitquery.io/v1/docs/Schema/elrond/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Elrond Coinpath API](https://docs.bitquery.io/v1/docs/Schema/elrond/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/addressstats.md b/docs/Schema/eos/addressstats.md index c94c359..e969d5a 100644 --- a/docs/Schema/eos/addressstats.md +++ b/docs/Schema/eos/addressstats.md @@ -1,3 +1,24 @@ +--- +title: "EOS Address Stats API" +description: "Query EOS address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["EOS API", "EOS Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Address Stats API ``` @@ -70,3 +91,11 @@ Address data can be filtered using following arguments: - **sendToCount** : The number of accounts that the account has sent tokens to. - **sendToCurrencies** : The currencies that the account has sent tokens in. - **sendTxCount** : The number of transactions that the account has sent tokens in. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/blocks.md b/docs/Schema/eos/blocks.md index 5ffb5c7..d6ab0f6 100644 --- a/docs/Schema/eos/blocks.md +++ b/docs/Schema/eos/blocks.md @@ -1,3 +1,24 @@ +--- +title: "EOS Blocks API" +description: "Query EOS blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["EOS API", "EOS Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Blocks API Bitquery's EOS blocks API provides information on blocks in the EOS chain. Below are the fields in the schema: @@ -55,3 +76,11 @@ query ($from: ISO8601DateTime, $till: ISO8601DateTime) { - **producer** : The producer who created the block. - **address** : The producer's EOS account address. - **annotation** : The producer's annotation for the block. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/coinpath.md b/docs/Schema/eos/coinpath.md index a0989ea..2fec986 100644 --- a/docs/Schema/eos/coinpath.md +++ b/docs/Schema/eos/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "EOS Coinpath API" +description: "Query EOS coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["EOS API", "EOS Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Coinpath The EOS Coinpath API allows you to get the money flow for an address on the EOS blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. @@ -180,3 +201,10 @@ query ($address: String!, $currency: String!, $from: ISO8601DateTime, $till: ISO - **depth** The depth of the coinpath. - **count** The number of transactions in the coinpath. - **block** The block in which the first transaction in the coinpath was included. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/overview.md b/docs/Schema/eos/overview.md index 0889104..f7cd9be 100644 --- a/docs/Schema/eos/overview.md +++ b/docs/Schema/eos/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "EOS API — Blockchain Data Schema | Bitquery" +description: "Access EOS blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [EOS API, EOS GraphQL, EOS blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview EOS is a open-source blockchain network focused on building high-performance blockchain platforms on top of the network. @@ -9,4 +27,11 @@ Bitquery's EOS API provides you data on proposers, smart contract calls, transac You also have an [EOS Explorer](https://explorer.bitquery.io/eos) for easy access to EOS data. -![EOS Explorer](/img/ide/EOS.png) \ No newline at end of file +![EOS Explorer](/img/ide/EOS.png) + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/eos/proposers.md b/docs/Schema/eos/proposers.md index 3d5ddbb..4a6671a 100644 --- a/docs/Schema/eos/proposers.md +++ b/docs/Schema/eos/proposers.md @@ -1,3 +1,24 @@ +--- +title: "EOS Proposers API" +description: "Query EOS proposers data using Bitquery GraphQL API. Get block proposers and producer metadata." +keywords: ["EOS API", "EOS Proposers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Producers API ``` @@ -59,3 +80,11 @@ query ( $from: ISO8601DateTime, $till: ISO8601DateTime) { - **timestamp** : The timestamp of the block. - **hash** : The hash of the block. - **height** : The block number. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/smartcontractcalls.md b/docs/Schema/eos/smartcontractcalls.md index 22f0628..68fa697 100644 --- a/docs/Schema/eos/smartcontractcalls.md +++ b/docs/Schema/eos/smartcontractcalls.md @@ -1,3 +1,24 @@ +--- +title: "EOS Smart Contract Calls API" +description: "Query EOS smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["EOS API", "EOS Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Smart Contract Calls API According to the official documentation, EOS smart contracts include definition for @@ -102,3 +123,11 @@ query ( $date: ISO8601DateTime) { - **permissions** : Whether the permissions were `active` or` inactive` Permissions for an account are used to authorize actions and transactions to other accounts. - **receivers** : The receivers of the call. - **scheduled** : `true` or `false` value as to whether the call was scheduled or not. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/transactions.md b/docs/Schema/eos/transactions.md index f4bf96f..7e60880 100644 --- a/docs/Schema/eos/transactions.md +++ b/docs/Schema/eos/transactions.md @@ -1,3 +1,24 @@ +--- +title: "EOS Transactions API" +description: "Query EOS transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["EOS API", "EOS Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Transactions API Bitquery's EOS Transactions API gives you information on cpuUsageUs, status of transaction and, netUsage details. Below are the fields in the schema: @@ -65,3 +86,11 @@ query ($from: ISO8601DateTime, $till: ISO8601DateTime) { - **netUsageWords** The amount of network resources used by the transaction. - **scheduled** A boolean value indicating whether the transaction was scheduled. - **success** A boolean value indicating whether the transaction was successful. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/eos/transfers.md b/docs/Schema/eos/transfers.md index fb60802..26ff5a6 100644 --- a/docs/Schema/eos/transfers.md +++ b/docs/Schema/eos/transfers.md @@ -1,3 +1,24 @@ +--- +title: "EOS Transfers API" +description: "Query EOS transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["EOS API", "EOS Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # EOS Transfers API Bitquery's EOS transfers API gives you information including sender, receiver, currency details. Below are the fields in the schema: @@ -82,3 +103,11 @@ query ( $date: ISO8601DateTime) { - **amount** : The amount of tokens that were transferred. - **txHash** : The hash of the transaction that made the transfer. - **actors** : The actors involved in the transfer. This includes the sender, receiver, and any other accounts that were involved in the transaction. + +## Related Resources + +- [EOS schema overview](https://docs.bitquery.io/v1/docs/Schema/eos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [EOS Coinpath API](https://docs.bitquery.io/v1/docs/Schema/eos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/ethereum/activeaddresses.md b/docs/Schema/ethereum/activeaddresses.md index 8083d05..91fdc7b 100644 --- a/docs/Schema/ethereum/activeaddresses.md +++ b/docs/Schema/ethereum/activeaddresses.md @@ -1,5 +1,6 @@ --- title: "Ethereum Active Addresses API" +description: "Access historical and current Ethereum active address metrics with Bitquery GraphQL." --- @@ -68,3 +69,11 @@ The following are available fields for the `activeAddresses`: - `address`: returns the address and its annotation. - `count`: returns the aggregate count of active addresses. - `countBigInt`: returns the aggregate count of active addresses in `BigInt` format. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Active addresses examples](https://docs.bitquery.io/v1/docs/Examples/activeAddresses/blockchain-active-addresses-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/address.md b/docs/Schema/ethereum/address.md index 45f75b0..dbf1110 100644 --- a/docs/Schema/ethereum/address.md +++ b/docs/Schema/ethereum/address.md @@ -1,5 +1,6 @@ --- title: "Ethereum Addresses API" +description: "Explore specific address details, balances, and smart contract attributes using Bitquery's Ethereum address query." --- @@ -77,3 +78,11 @@ The following are available fields for the address: - `balance`: Returns the current balance of the address. - `balances`: Returns the balance history of the address. - `smartContract`: Returns details if the address is that of a smart contract. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/addresstats.md b/docs/Schema/ethereum/addresstats.md index a0e685b..56a5737 100644 --- a/docs/Schema/ethereum/addresstats.md +++ b/docs/Schema/ethereum/addresstats.md @@ -1,5 +1,6 @@ --- title: "Ethereum Addresses Stats API" +description: "Explore comprehensive address statistics, including counts, aggregates, and historical data for transfers, balances, fees, and more." --- @@ -69,3 +70,11 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/arguments.md b/docs/Schema/ethereum/arguments.md index d2f2d28..c36d98b 100644 --- a/docs/Schema/ethereum/arguments.md +++ b/docs/Schema/ethereum/arguments.md @@ -1,5 +1,6 @@ --- title: "Ethereum Arguments API" +description: "Query arguments of smart contract calls and events with the arguments API. Filter by type, depth, caller, and more." --- @@ -80,4 +81,12 @@ The following are available fields for the `arguments`: - `smartContractSignature`: returns signature of contract method or event - `success`: - `transaction`: returns transaction information -- `value`: returns value of method or event argument \ No newline at end of file +- `value`: returns value of method or event argument + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Smart contract calls examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractCalls/smart-contract-calls-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/blocks.md b/docs/Schema/ethereum/blocks.md index b4d22a3..1a541a8 100644 --- a/docs/Schema/ethereum/blocks.md +++ b/docs/Schema/ethereum/blocks.md @@ -1,5 +1,6 @@ --- title: "Ethereum Blocks API" +description: "Access Ethereum block data, including gas limits, rewards, and more. Get the latest 10 blocks with the Ethereum Blocks API." --- @@ -98,3 +99,11 @@ Blocks data can be filtered using following arguments: - `transactionCountBigInt`: - `uncleCount`: - `uncleCountBigInt`: + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/coinpath.md b/docs/Schema/ethereum/coinpath.md index 5b6d913..1ddf9af 100644 --- a/docs/Schema/ethereum/coinpath.md +++ b/docs/Schema/ethereum/coinpath.md @@ -1,5 +1,6 @@ --- title: "Ethereum Coinpath API" +description: "Retrieve detailed money flow information using the coinpath API. Filter by currency, date, sender, receiver, and more." --- @@ -62,4 +63,12 @@ The following are available fields for the `coinpath`: - `receiver`: returns information about the receiver. - `sender`: returns information about the sender. - `transaction`: returns transaction details. -- `transactions`: returns attributes of transactions. \ No newline at end of file +- `transactions`: returns attributes of transactions. + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/dextrades.md b/docs/Schema/ethereum/dextrades.md index 9a3b018..025242c 100644 --- a/docs/Schema/ethereum/dextrades.md +++ b/docs/Schema/ethereum/dextrades.md @@ -1,5 +1,6 @@ --- title: "Ethereum DEX API" +description: "Get Ethereum DEX trade data with DEX Trades API. DEX data for 100+ DEX like Uniswap, Sushiswap, Curve, Balancer, and more." --- @@ -155,4 +156,11 @@ The following are available fields for the `dexTrades`: - `tradeAmount`: returns the trade amount in the base currency. - `tradeIndex`: returns the index of the trade in the transaction. - `transaction`: returns information about the transaction in which the trade was executed. - \ No newline at end of file + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX trading examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/overview.md b/docs/Schema/ethereum/overview.md index 03214c1..738bcdd 100644 --- a/docs/Schema/ethereum/overview.md +++ b/docs/Schema/ethereum/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Ethereum API — Blockchain Data Schema | Bitquery" +description: "Access Ethereum blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Ethereum API, Ethereum GraphQL, Ethereum blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery API offers access to indexed data from the Ethereum blockchain through the ethereum schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -23,4 +41,12 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: -Let's dive in and explore the Ethereum data available through Bitquery API. \ No newline at end of file +Let's dive in and explore the Ethereum data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/ethereum/references.md b/docs/Schema/ethereum/references.md index 1bd8540..d996ac9 100644 --- a/docs/Schema/ethereum/references.md +++ b/docs/Schema/ethereum/references.md @@ -1,5 +1,6 @@ --- title: "Ethereum References API" +description: "Filter and query reference fields linked to Ethereum smart contract arguments, calls, and events." --- @@ -71,4 +72,12 @@ References can be filtered using following arguments: - `smartContract`: - `smartContractSignature`: - `success`: -- `transaction`: \ No newline at end of file +- `transaction`: + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Smart contract events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/smartcontractcalls.md b/docs/Schema/ethereum/smartcontractcalls.md index 53d85ef..3daae0d 100644 --- a/docs/Schema/ethereum/smartcontractcalls.md +++ b/docs/Schema/ethereum/smartcontractcalls.md @@ -1,5 +1,6 @@ --- title: "Ethereum Smart Contract Calls API" +description: "Explore Ethereum smart contract call data. Analyze smart contract calls with detailed information." --- @@ -109,4 +110,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContract`: returns details of smart contract - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not -- `transaction`: returns details of the transaction in which smart contract call was executed \ No newline at end of file +- `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/smartcontractevents.md b/docs/Schema/ethereum/smartcontractevents.md index 1c37628..ed9c4d4 100644 --- a/docs/Schema/ethereum/smartcontractevents.md +++ b/docs/Schema/ethereum/smartcontractevents.md @@ -1,5 +1,6 @@ --- title: "Ethereum Smart Contract Events API" +description: "Get Ethereum smart contract event data using the Events API. Explore events in depth with detailed information." --- @@ -96,3 +97,11 @@ Smart Contract Events can be filtered using following arguments: - `smartContract`: returns details of smart contract on which event happened - `smartContractEvent`: returns details about smart contract event like name, signature, and signature hash - `transaction`: returns details about transaction which emitted smart contract event + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/transactions.md b/docs/Schema/ethereum/transactions.md index 0a9e120..17cc452 100644 --- a/docs/Schema/ethereum/transactions.md +++ b/docs/Schema/ethereum/transactions.md @@ -1,5 +1,6 @@ --- title: "Ethereum Transactions API" +description: "Explore Ethereum transactions. Get insights into the Ethereum blockchain. Monitor Ethereum network activity effortlessly." --- @@ -135,3 +136,11 @@ Transactions can be filtered using following arguments: - `success`: returns if transaction is success or not - `to`: returns address to which of a particular transaction was sent - `txType`: returns transaction type + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/transfers.md b/docs/Schema/ethereum/transfers.md index ea0160f..06f0282 100644 --- a/docs/Schema/ethereum/transfers.md +++ b/docs/Schema/ethereum/transfers.md @@ -1,5 +1,6 @@ --- title: "Ethereum Transfers API" +description: "Get Ethereum token transfers with detailed information using the transfers API. Filter, sort, and analyze ERC-20 token flow easily." --- @@ -139,4 +140,12 @@ Data retrieved using `transfers` can be filtered using following arguments: - `receiver`: returns receiver of a particular transfer - `sender`: returns sender of a particular transfer - `success`: returns boolean value for success of a particular transfer -- `transaction`: returns details of transaction in which a particular transfer \ No newline at end of file +- `transaction`: returns details of transaction in which a particular transfer + +## Related Resources + +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum2/attestations.md b/docs/Schema/ethereum2/attestations.md index c747d3d..15af2c1 100644 --- a/docs/Schema/ethereum2/attestations.md +++ b/docs/Schema/ethereum2/attestations.md @@ -1,5 +1,6 @@ --- title: ETH2 Attestations API +description: "Query attestations, aggregation bits, and validators on the Beacon Chain." --- @@ -135,3 +136,12 @@ query ($network: Ethereum2Network!) { `time`: This field contains the time of the block. `attestationEpoch`: This field specifies the epoch number of the attestations that should be returned. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/ethereum2/attesterSlashings.md b/docs/Schema/ethereum2/attesterSlashings.md index d7baba5..c769bcf 100644 --- a/docs/Schema/ethereum2/attesterSlashings.md +++ b/docs/Schema/ethereum2/attesterSlashings.md @@ -1,5 +1,6 @@ --- title: ETH2 Attester Slashings API +description: "Query attester slashing evidence on the Beacon Chain." --- @@ -119,4 +120,13 @@ query ($network: Ethereum2Network!) { `date`: This field contains the date and time of the attester slashing.. -`attestationEpoch`: This field specifies the epoch number of the Attester Slashings that should be returned. \ No newline at end of file +`attestationEpoch`: This field specifies the epoch number of the Attester Slashings that should be returned. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/ethereum2/blocks.md b/docs/Schema/ethereum2/blocks.md index 5be3255..f2f8fe1 100644 --- a/docs/Schema/ethereum2/blocks.md +++ b/docs/Schema/ethereum2/blocks.md @@ -1,5 +1,6 @@ --- title: ETH2 Blocks API +description: "Query Beacon Chain blocks, roots, and consensus data." --- @@ -125,3 +126,12 @@ query ($network: Ethereum2Network!, $dateFormat: String!, $from: ISO8601DateTime `stateRoot`: This field contains the hash of the block's state root. `randaoReveal`: This field contains the RANDAO reveal of the block. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/ethereum2/deposits.md b/docs/Schema/ethereum2/deposits.md index ec208d1..c026e54 100644 --- a/docs/Schema/ethereum2/deposits.md +++ b/docs/Schema/ethereum2/deposits.md @@ -1,5 +1,6 @@ --- title: ETH2 Deposits API +description: "Query validator deposits on the Beacon Chain." --- @@ -115,4 +116,13 @@ query ($network: Ethereum2Network!, $limit: Int!, $offset: Int!) { `depositIndex`: This field contains the index of the deposit in the block. -`height`: This field specifies the height of the block that the deposits should be returned for. \ No newline at end of file +`height`: This field specifies the height of the block that the deposits should be returned for. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/ethereum2/overview.md b/docs/Schema/ethereum2/overview.md index c04a433..e4db73b 100644 --- a/docs/Schema/ethereum2/overview.md +++ b/docs/Schema/ethereum2/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Ethereum Beacon Chain API — Blockchain Data Schema | Bitquery" +description: "Access Ethereum Beacon Chain blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Ethereum Beacon Chain API, Ethereum Beacon Chain GraphQL, Ethereum Beacon Chain blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Ethereum Beacon Chain API Overview Bitquery provides APIs to access Eth2 data. You can get info on the ethereum's staking model. It uses the Proof-of-stake, a consensus method that blockchain networks utilize to reach distributed consensus. @@ -14,4 +32,12 @@ These APIs provide details on validators, their staked amounts, their exits and Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [ETH2 Beacon Chain examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/ethereum2/proposerSlashings.md b/docs/Schema/ethereum2/proposerSlashings.md index 12cd10e..1fb6f53 100644 --- a/docs/Schema/ethereum2/proposerSlashings.md +++ b/docs/Schema/ethereum2/proposerSlashings.md @@ -1,5 +1,6 @@ --- title: ETH2 Proposer Slashings API +description: "Query proposer slashing evidence on the Beacon Chain." --- @@ -141,4 +142,13 @@ query ($network: Ethereum2Network!) { `signature`: The signature of the slashing. -`slot`: The slot of the slashing. \ No newline at end of file +`slot`: The slot of the slashing. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/ethereum2/validatorUpdates.md b/docs/Schema/ethereum2/validatorUpdates.md index 527b23f..df8d454 100644 --- a/docs/Schema/ethereum2/validatorUpdates.md +++ b/docs/Schema/ethereum2/validatorUpdates.md @@ -1,5 +1,6 @@ --- title: ETH2 Validator Updates API +description: "Query validator status updates on the Beacon Chain." --- @@ -161,8 +162,11 @@ query ($network: Ethereum2Network!) { `validatorWithdrawalCredentials`: This field contains the validator's withdrawal credentials. +## Related Resources - - - +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/Schema/ethereum2/voluntaryExits.md b/docs/Schema/ethereum2/voluntaryExits.md index c194a9e..4b968e5 100644 --- a/docs/Schema/ethereum2/voluntaryExits.md +++ b/docs/Schema/ethereum2/voluntaryExits.md @@ -1,5 +1,6 @@ --- title: ETH2 Voluntary Exits API +description: "Query voluntary validator exits on the Beacon Chain." --- @@ -106,4 +107,13 @@ voluntaryExitEpoch: This field specifies the epoch number at which the voluntary `voluntaryExitEpoch`: This field contains the epoch number at which the voluntary exit was submitted. -`height`: This field specifies the height of the block that the voluntary exits should be returned for. \ No newline at end of file +`height`: This field specifies the height of the block that the voluntary exits should be returned for. + +## Related Resources + +- [Beacon Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum2/overview) +- [ETH2 examples](https://docs.bitquery.io/v1/docs/Examples/Beacon%20Chain%20Examples/eth2_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum execution layer schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) + diff --git a/docs/Schema/filecoin/address.md b/docs/Schema/filecoin/address.md index 72243f0..bd5578f 100644 --- a/docs/Schema/filecoin/address.md +++ b/docs/Schema/filecoin/address.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Address API" +description: "Query Filecoin address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Filecoin API", "Filecoin Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The Address API allows you to query information about addresses on the Filecoin blockchain. @@ -27,4 +48,12 @@ query MyQuery { `address`: The address of the actor. `annotation`: The annotation for the address. -`balance`: The balance of the address. \ No newline at end of file +`balance`: The balance of the address. + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/filecoin/arguments.md b/docs/Schema/filecoin/arguments.md index e69de29..dc3a1c5 100644 --- a/docs/Schema/filecoin/arguments.md +++ b/docs/Schema/filecoin/arguments.md @@ -0,0 +1,28 @@ +--- +title: "Filecoin Arguments API" +description: "Query Filecoin GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Filecoin API", "Filecoin Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/filecoin/blocks.md b/docs/Schema/filecoin/blocks.md index 7c00e7f..912a611 100644 --- a/docs/Schema/filecoin/blocks.md +++ b/docs/Schema/filecoin/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Blocks API" +description: "Query Filecoin blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Filecoin API", "Filecoin Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The Filecoin Blocks API allows you to query information about blocks on the Filecoin blockchain. @@ -74,4 +95,12 @@ query ($network: FilecoinNetwork!) { `height`: The height of the block. -`index`: The index of the block in the chain. \ No newline at end of file +`index`: The index of the block in the chain. + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/filecoin/calls.md b/docs/Schema/filecoin/calls.md index 1e4ed83..3185db5 100644 --- a/docs/Schema/filecoin/calls.md +++ b/docs/Schema/filecoin/calls.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Calls API" +description: "Query Filecoin calls data using Bitquery GraphQL API. Get contract or system calls, inputs, and results." +keywords: ["Filecoin API", "Filecoin Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Calls In Filecoin, calls are used to invoke methods on actors and transfer FIL. Bitquery's Calls API provides you the following information: @@ -100,4 +121,12 @@ The `amount` filter allows you to filter calls by the amount of FIL transferred. - `receiver`: The address of the actor that received the call. - `sender`: The address of the actor that made the call. - `success`: Whether the call was successful. -- `hash`: The hash of the message that was called. \ No newline at end of file +- `hash`: The hash of the message that was called. + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/filecoin/messages.md b/docs/Schema/filecoin/messages.md index e5dd66e..a2a131d 100644 --- a/docs/Schema/filecoin/messages.md +++ b/docs/Schema/filecoin/messages.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Messages API" +description: "Query Filecoin messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +keywords: ["Filecoin API", "Filecoin Messages", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Messages According to the [official Filecoin documentation](https://docs.filecoin.io/basics/the-blockchain/blocks-and-tipsets/), @@ -93,4 +114,12 @@ query ($network: FilecoinNetwork!, $dateFormat: String!, $from: ISO8601DateTime, - **receiver:** The address of the receiver of the message. - **signature:** The signature of the message. - **signatureType:** The type of signature used to sign the message. -- **signedHash:** The hash of the message that was signed. \ No newline at end of file +- **signedHash:** The hash of the message that was signed. + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/filecoin/overview.md b/docs/Schema/filecoin/overview.md index 90ca6c7..53d6bb7 100644 --- a/docs/Schema/filecoin/overview.md +++ b/docs/Schema/filecoin/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Filecoin API — Blockchain Data Schema | Bitquery" +description: "Access Filecoin blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Filecoin API, Filecoin GraphQL, Filecoin blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview @@ -15,4 +33,12 @@ Bitquery's filecoin data includes an explorer for easy-viewing and extensive API Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Filecoin API examples](https://docs.bitquery.io/v1/docs/Examples/filecoin) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/filecoin/transfers.md b/docs/Schema/filecoin/transfers.md index 710a9e3..9bea066 100644 --- a/docs/Schema/filecoin/transfers.md +++ b/docs/Schema/filecoin/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Filecoin Transfers API" +description: "Query Filecoin transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Filecoin API", "Filecoin Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The Transfers API allows you to query information about transfers on the Filecoin blockchain. @@ -145,4 +166,12 @@ query ($network: FilecoinNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTim - **method** - The name of the method that was used to perform the transfer. - **transferType** - - The type of transfer. Can be `burn`, `miner`, `reward` and so on. \ No newline at end of file + - The type of transfer. Can be `burn`, `miner`, `reward` and so on. + +## Related Resources + +- [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Filecoin Coinpath API](https://docs.bitquery.io/v1/docs/Schema/filecoin/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/address.md b/docs/Schema/flow/address.md index 936384f..dde9d33 100644 --- a/docs/Schema/flow/address.md +++ b/docs/Schema/flow/address.md @@ -1,3 +1,24 @@ +--- +title: "Flow Address API" +description: "Query Flow address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Flow API", "Flow Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The Flow Address API offers basic information about addresses from the Flow Blockchain. @@ -17,3 +38,11 @@ You can filter addresses using the following fields: - address: provides the address itself - annotation: provides any available annotation - balance: shows the balance of the native token for the given address + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/arguments.md b/docs/Schema/flow/arguments.md index 1cd204f..165f552 100644 --- a/docs/Schema/flow/arguments.md +++ b/docs/Schema/flow/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Flow Arguments API" +description: "Query Flow GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Flow API", "Flow Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The Flow Arguments API provides information about transaction arguments from the flow blockchain which contains the payload and envelope signatures @@ -39,4 +60,12 @@ You can filter Arguments using the following fields: - time: returns time when the transaction was created - value: returns value of argument - valueAsFix: returns value of argument converted to Fixed point number -- valueAsInt: returns value of argument converted to Integer +- valueAsInt: returns value of argument converted to Integer + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/blockSeals.md b/docs/Schema/flow/blockSeals.md index 1c3bb7e..1e3307c 100644 --- a/docs/Schema/flow/blockSeals.md +++ b/docs/Schema/flow/blockSeals.md @@ -1,3 +1,24 @@ +--- +title: "Flow Block Seals API" +description: "Query Flow block seals data using Bitquery GraphQL API. Get block seals, execution nodes, and consensus proofs." +keywords: ["Flow API", "Flow Block Seals", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Block Seals The Flow Block Seals API provides you information about blocks seal from the Flow Blockchain. A block seal is an attestation that execution result of a specific block has been verified and approved by a quorum of verification nodes. @@ -34,3 +55,11 @@ You can filter block seal data using following fields: - resultApprovalSIgnatures: returns BLS signatures of verification nodes on the result approval contents - sealId: returns Id of the block being sealed - time: returns the time block being sealed + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/blocks.md b/docs/Schema/flow/blocks.md index d79a5e3..b9f5b85 100644 --- a/docs/Schema/flow/blocks.md +++ b/docs/Schema/flow/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Flow Blocks API" +description: "Query Flow blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Flow API", "Flow Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The Flow Blocks API provides detailed information about blocks created on the Flow Blockchain. @@ -36,3 +57,11 @@ You can filter the blocks using the following fields: - parentBlockId: returns id/hash of parent block - time: returns time when block was created - transactionsCount: returns transaction count of block + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/coinpath.md b/docs/Schema/flow/coinpath.md index 32ab33c..8efd847 100644 --- a/docs/Schema/flow/coinpath.md +++ b/docs/Schema/flow/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Flow Coinpath API" +description: "Query Flow coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Flow API", "Flow Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The Tezos Coinpath API provides information about money flow from the Flow Blockchain. @@ -35,3 +56,10 @@ You can filter the data using following fields: - receiver: returns address of transfer receiver - sender: returns address of transfer sender - transaction: returns summary of transaction where transfer is included + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/collections.md b/docs/Schema/flow/collections.md index 57d0989..779a8a6 100644 --- a/docs/Schema/flow/collections.md +++ b/docs/Schema/flow/collections.md @@ -1,3 +1,24 @@ +--- +title: "Flow Collections API" +description: "Query Flow collections data using Bitquery GraphQL API. Get NFT collections, IDs, and collection metadata." +keywords: ["Flow API", "Flow Collections", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Collections The Flow Collections API provides information about collections from the Flow Blockchain. A collection is batch of transactions that have been includes in a block. @@ -35,3 +56,11 @@ You can filer the collections data using the following fields: - signatures: returns BLS signatures of the collection nodes guaranteeing the collection - time: returns time the collection was created - transactionsCount: returns count of transactions inside collection + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/eventFields.md b/docs/Schema/flow/eventFields.md index 26883bf..b8d6215 100644 --- a/docs/Schema/flow/eventFields.md +++ b/docs/Schema/flow/eventFields.md @@ -1,3 +1,24 @@ +--- +title: "Flow Event Fields API" +description: "Query Flow event fields data using Bitquery GraphQL API. Get event field definitions and typed values." +keywords: ["Flow API", "Flow Event Fields", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Event Fields The Flow Event Fields API provides information about events from the Flow Blockchain. @@ -46,3 +67,11 @@ You can filter the events fields data using the following fields: - time: returns time when transaction is created - transaction: returns information about transaction - type: returns type of field + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/events.md b/docs/Schema/flow/events.md index 8ea34f3..51837ed 100644 --- a/docs/Schema/flow/events.md +++ b/docs/Schema/flow/events.md @@ -1,3 +1,24 @@ +--- +title: "Flow Events API" +description: "Query Flow events data using Bitquery GraphQL API. Get on-chain events, types, and payloads." +keywords: ["Flow API", "Flow Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Events The Flow Events API provides information about events emiited on the Flow Blockchain. @@ -38,3 +59,11 @@ The Flow Events API provides information about events emiited on the Flow Blockc - time: returns time when transaction was created - transaction: returns details of transaction - type: returns type of event + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/inputs.md b/docs/Schema/flow/inputs.md index 677a3a5..165b712 100644 --- a/docs/Schema/flow/inputs.md +++ b/docs/Schema/flow/inputs.md @@ -1,3 +1,24 @@ +--- +title: "Flow Inputs API" +description: "Query Flow inputs data using Bitquery GraphQL API. Get transaction inputs, authorizers, and signatures context." +keywords: ["Flow API", "Flow Inputs", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Inputs The Flow Inputs API provides information about transaction inputs from the Flow Blockchain. @@ -50,3 +71,11 @@ You can filter the input using the following fields: - transaction: returns information of transaction - transferReason: returns transfer reason like nft_transfer, fungible_token_transfer, fee - type: returns type of input + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/outputs.md b/docs/Schema/flow/outputs.md index 3fddf98..ffb6262 100644 --- a/docs/Schema/flow/outputs.md +++ b/docs/Schema/flow/outputs.md @@ -1,3 +1,24 @@ +--- +title: "Flow Outputs API" +description: "Query Flow outputs data using Bitquery GraphQL API. Get transaction outputs, amounts, and recipients." +keywords: ["Flow API", "Flow Outputs", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Outputs The Flow Outputs API provides information about the transaction outputs from the Flow Blockchain. @@ -50,3 +71,11 @@ You can filter the outputs using the following fields: - transaction: returns information of transaction - transferReason: returns transfer reason like nft_transfer, fungible_token_transfer, fee - type: returns type of output + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/overview.md b/docs/Schema/flow/overview.md index 377b032..ba5134a 100644 --- a/docs/Schema/flow/overview.md +++ b/docs/Schema/flow/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Flow API — Blockchain Data Schema | Bitquery" +description: "Access Flow blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Flow API, Flow GraphQL, Flow blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Flow is a layer 1 blockchain for creating and trading non-fungible tokens (NFTs), decentralized applications (dApps), and games. @@ -14,3 +32,9 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/flow/transactionAuthorizers.md b/docs/Schema/flow/transactionAuthorizers.md index fd98d75..783188f 100644 --- a/docs/Schema/flow/transactionAuthorizers.md +++ b/docs/Schema/flow/transactionAuthorizers.md @@ -1,3 +1,24 @@ +--- +title: "Flow Transaction Authorizers API" +description: "Query Flow authorizers data using Bitquery GraphQL API. Get authorizers and payer roles for transactions." +keywords: ["Flow API", "Flow Transaction Authorizers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transaction Authorizers The Flow Transaction Authorizers API provides information about transaction authorizers from the Flow Blcockhain. @@ -43,3 +64,11 @@ You can filter the transaction authorizer data using following fields: - minimum: returns minimum for selected measurable field of Flow Transaction Authorizer - time: returns time of transaction creation - transaction: returns information about transaction + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/transactionEnvelopeSignatures.md b/docs/Schema/flow/transactionEnvelopeSignatures.md index eb6993e..bf8f74f 100644 --- a/docs/Schema/flow/transactionEnvelopeSignatures.md +++ b/docs/Schema/flow/transactionEnvelopeSignatures.md @@ -1,3 +1,24 @@ +--- +title: "Flow Transaction Envelope Signatures API" +description: "Query Flow signatures data using Bitquery GraphQL API. Get envelope signatures and signing accounts." +keywords: ["Flow API", "Flow Transaction Envelope Signatures", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transaction Envelope Signatures The Flow Transaction Envelope Signatures API provides details about envelope signatures of transaction from the Flow Blockchain. @@ -47,3 +68,11 @@ You can filter the data using following fields: - signature: returns raw signature data - time: returns time the transaction was created - transaction: returns basic information about transaction + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/transactionPayloadSignatures.md b/docs/Schema/flow/transactionPayloadSignatures.md index 2006de8..7b28845 100644 --- a/docs/Schema/flow/transactionPayloadSignatures.md +++ b/docs/Schema/flow/transactionPayloadSignatures.md @@ -1,3 +1,24 @@ +--- +title: "Flow Transaction Payload Signatures API" +description: "Query Flow signatures data using Bitquery GraphQL API. Get payload signatures and signer keys." +keywords: ["Flow API", "Flow Transaction Payload Signatures", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transaction Payload Signatures The Flow Transaction Payload Signatures API provides information about payload signatures of transaction from the Flow Blockchain. @@ -47,3 +68,11 @@ You can filter data using following fields: - signature: returns raw signature data - time: returns time of transaction creation - transaction: returns basic information about transaction + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/flow/transactions.md b/docs/Schema/flow/transactions.md index 1a38f88..4eaeef7 100644 --- a/docs/Schema/flow/transactions.md +++ b/docs/Schema/flow/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Flow Transactions API" +description: "Query Flow transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Flow API", "Flow Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Flow Transaction API provides information about transactions from the Flow Blockchain. @@ -52,3 +73,11 @@ You can filter transaction data using following fields: - script: returns raw script code for the cadence script encoded as UTF-8 bytes - statusCode: returns status code of transaction where 0 is success and 1 is failure - time: returns time the transaction was created + +## Related Resources + +- [Flow schema overview](https://docs.bitquery.io/v1/docs/Schema/flow/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Flow Coinpath API](https://docs.bitquery.io/v1/docs/Schema/flow/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/arguments.md b/docs/Schema/harmony/arguments.md index fa70921..36fec5c 100644 --- a/docs/Schema/harmony/arguments.md +++ b/docs/Schema/harmony/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Arguments API" +description: "Query Harmony GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Harmony API", "Harmony Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The Harmony Arguments API provides information about arguments of smart contract calls and events. @@ -54,3 +75,11 @@ You can filter data using following fields: - time: returns time when transaction was created - toShardId: returns id of shard where transaction was sent - value: returns value of argument + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/blocks.md b/docs/Schema/harmony/blocks.md index b295ea2..3f8e017 100644 --- a/docs/Schema/harmony/blocks.md +++ b/docs/Schema/harmony/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Blocks API" +description: "Query Harmony blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Harmony API", "Harmony Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The Harmony Blocks API provides information about blocks from the Harmony Blockchain. @@ -58,3 +79,11 @@ You can filter data using any of the following fields: - transactionsRoot: returns root of the transaction trie of the block - unclesCount: returns count of uncles hashes - viewId: returns view id + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/smartContractCalls.md b/docs/Schema/harmony/smartContractCalls.md index a096aba..616fcf9 100644 --- a/docs/Schema/harmony/smartContractCalls.md +++ b/docs/Schema/harmony/smartContractCalls.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Smart Contract Calls API" +description: "Query Harmony smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Harmony API", "Harmony Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Smart Contract Calls The Harmony Smart Contract Calls API provides detailed information about smart contract calls made on the Harmony Blockchain. @@ -54,3 +75,11 @@ You can filter smart contract calls data using following fields: - txIndex: returns index of the transaction in the block - txSender: returns sender of the transaction - txTo: returns transaction to address + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/smartContractEvents.md b/docs/Schema/harmony/smartContractEvents.md index 79f41a6..a275f9b 100644 --- a/docs/Schema/harmony/smartContractEvents.md +++ b/docs/Schema/harmony/smartContractEvents.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Smart Contract Events API" +description: "Query Harmony smart contract events data using Bitquery GraphQL API. Get contract events, logs, topics, and decoded payloads." +keywords: ["Harmony API", "Harmony Smart Contract Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Smart Contract Events The Harmony Smart Contract Events API provides information about events emiited from smart contract on the Harmony Blockchain. @@ -45,3 +66,11 @@ You can filter events using following fields: - txHash: returns hash of the transaction - txIndex: returns index of the transaction in the block - txTo: returns transaction to address + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/stakingTransactions.md b/docs/Schema/harmony/stakingTransactions.md index 08bb7d2..16b646f 100644 --- a/docs/Schema/harmony/stakingTransactions.md +++ b/docs/Schema/harmony/stakingTransactions.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Staking Transactions API" +description: "Query Harmony staking data using Bitquery GraphQL API. Get staking delegations, validators, and staking-related transactions." +keywords: ["Harmony API", "Harmony Staking Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Staking Transactions The Harmony Staking Transaction API provides details about staking transactions from the Harmony blockchain. @@ -49,3 +70,11 @@ You can filter staking transactions using following fields: - transactionType: returns type of the transaction - validatorAddress: returns address of the validator - value: returns value transfrred in atto + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/transactions.md b/docs/Schema/harmony/transactions.md index d8ca947..cb503c8 100644 --- a/docs/Schema/harmony/transactions.md +++ b/docs/Schema/harmony/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Transactions API" +description: "Query Harmony transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Harmony API", "Harmony Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Harmony Transactions API provides information about transaction form the Harmony blockchain. @@ -55,3 +76,11 @@ You can filter transactions using the following fields: - transactionHash: returns hash of the transaction - transactionIndex: returns index of transaction in the block - value: returns value transferred in ATTO + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/harmony/transfers.md b/docs/Schema/harmony/transfers.md index 0456aba..827f012 100644 --- a/docs/Schema/harmony/transfers.md +++ b/docs/Schema/harmony/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Harmony Transfers API" +description: "Query Harmony transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Harmony API", "Harmony Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The Harmony Transfers API provides information about token transfers from the Harmony Blockchain. @@ -59,3 +80,11 @@ You can filter transfers using following fields: - txSenderreturns address of the transaction sender - txTo: returns address of transaction receiver - value: returns value transferred in ATTO + +## Related Resources + +- [Harmony schema overview](https://docs.bitquery.io/v1/docs/Schema/harmony/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Harmony Coinpath API](https://docs.bitquery.io/v1/docs/Schema/harmony/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/address.md b/docs/Schema/hedera/address.md index ce4344f..e810178 100644 --- a/docs/Schema/hedera/address.md +++ b/docs/Schema/hedera/address.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Address API" +description: "Query Hedera address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Hedera API", "Hedera Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The Address API provides basic information about addresses on the Hedera Blockchain. It offers information about various aspects, including the balance of the native currency associated with the address, any available annotations, and more. @@ -27,4 +48,12 @@ Use the `address` field to filter by a specific address or a list of addresses, - `address`: provides the address itself - `annotation`: offers any available annotation associated with the address - `balance`: displays the balance of the native currency -- `tokenBalances`: shows balances of all tokens, both fungible and non-fungible \ No newline at end of file +- `tokenBalances`: shows balances of all tokens, both fungible and non-fungible + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/arguments.md b/docs/Schema/hedera/arguments.md index a6942b0..aff092c 100644 --- a/docs/Schema/hedera/arguments.md +++ b/docs/Schema/hedera/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Arguments API" +description: "Query Hedera GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Hedera API", "Hedera Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The Arguments API provides you with information about event arguments. It offers valuable information about various aspects, such as the specific values of event arguments, their corresponding types, and even the transaction where the event originally occurred. @@ -73,4 +94,12 @@ You can filter the retrieved arguments using the following fields: - `transactionHash`: Presents the hash of the transaction. - `transactionValidDurationInSec`: Provides the duration for which this transaction is valid in seconds. - `validStart`: Displays the start timestamp of the valid duration of the transaction. -- `value`: Displays the value of the arguments. \ No newline at end of file +- `value`: Displays the value of the arguments. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/calls.md b/docs/Schema/hedera/calls.md index af9fe97..cbefbd2 100644 --- a/docs/Schema/hedera/calls.md +++ b/docs/Schema/hedera/calls.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Calls API" +description: "Query Hedera calls data using Bitquery GraphQL API. Get contract or system calls, inputs, and results." +keywords: ["Hedera API", "Hedera Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Calls The Calls API provides you with information about calls made on Hedera Blockchain. It offers information about various aspects, such as call inputs, result of the calls, and much more. @@ -66,3 +87,11 @@ You can filter the calls data using the following fields: - `transactionHash`: Presents the hash of the transaction. - `transactionValidDurationInSec`: Provides the duration for which this transaction is valid in seconds. - `validStart`: Displays the start timestamp of the valid duration of the transaction. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/coinpath.md b/docs/Schema/hedera/coinpath.md index 7582ca3..0ab3b94 100644 --- a/docs/Schema/hedera/coinpath.md +++ b/docs/Schema/hedera/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Coinpath API" +description: "Query Hedera coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Hedera API", "Hedera Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The Coinpath API offers information related to the flow of funds on the Hedera Blockchain. @@ -33,3 +54,10 @@ You can filter the information fetched from the API using the following filters: - `receiver`: Provides information about the receiver, including the address and annotation (if available). - `sender`: Provides information about the sender, including the address and annotation (if available). - `transactions`: Returns details about transactions, including the amount, height, hash, and more. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/inputs.md b/docs/Schema/hedera/inputs.md index b13a3fb..d65d9f0 100644 --- a/docs/Schema/hedera/inputs.md +++ b/docs/Schema/hedera/inputs.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Inputs API" +description: "Query Hedera inputs data using Bitquery GraphQL API. Get transaction inputs, authorizers, and signatures context." +keywords: ["Hedera API", "Hedera Inputs", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Inputs The Inputs API provides information about transaction inputs on the Hedera Blockchain. @@ -90,3 +111,11 @@ You can filter your input data using the following filters: - `transactionValidDurationInSec`: Returns the transaction valid duration in seconds. - `transferEntity`: Returns details about the transfer account. - `validStart`: Returns the start timestamp of the valid duration for the transaction. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/messages.md b/docs/Schema/hedera/messages.md index ea51f88..abfcd4c 100644 --- a/docs/Schema/hedera/messages.md +++ b/docs/Schema/hedera/messages.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Messages API" +description: "Query Hedera messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +keywords: ["Hedera API", "Hedera Messages", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Messages The Messages API provides information about blockchain messages on the Hedera Blockchain. @@ -82,3 +103,11 @@ You can filter blockchain messages using the following arguments: - `transactionHash`: Returns the hash of the transaction. - `transactionValidDurationInSec`: Returns the duration of transaction validity in seconds. - `validStart`: Returns the timestamp when the transaction validity starts. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/outputs.md b/docs/Schema/hedera/outputs.md index 8c07b3c..185c552 100644 --- a/docs/Schema/hedera/outputs.md +++ b/docs/Schema/hedera/outputs.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Outputs API" +description: "Query Hedera outputs data using Bitquery GraphQL API. Get transaction outputs, amounts, and recipients." +keywords: ["Hedera API", "Hedera Outputs", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Outputs The Outputs API provides information about transaction outputs on the Hedera Blockchain. @@ -46,3 +67,11 @@ The Outputs API provides information about transaction outputs on the Hedera Blo - `transactionValidDurationInSec`: Returns duration of transaction validity in seconds. - `transferEntity`: Returns details of the transfer account. - `validStart`: Returns the timestamp when the transaction validity starts. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/hedera/overview.md b/docs/Schema/hedera/overview.md index 7e3e8e6..d3f77c3 100644 --- a/docs/Schema/hedera/overview.md +++ b/docs/Schema/hedera/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Hedera API — Blockchain Data Schema | Bitquery" +description: "Access Hedera blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Hedera API, Hedera GraphQL, Hedera blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Our API makes it easy to access different types of data from the Hedera blockchain, like addresses, arguments, calls, and more. @@ -29,3 +47,11 @@ Let's dive in and explore the Hedera data available through Bitquery API. You can also use our user-friendly [explorer](https://explorer.bitquery.io/hedera) to interactively explore Hedera blockchain data. [![Hedera Explorer](/img/hedera-explorer.png)](https://explorer.bitquery.io/hedera) + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Hedera API examples](https://docs.bitquery.io/v1/docs/Examples/hedera) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/hedera/transactions.md b/docs/Schema/hedera/transactions.md index 2c1792f..18e0cf4 100644 --- a/docs/Schema/hedera/transactions.md +++ b/docs/Schema/hedera/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Hedera Transactions API" +description: "Query Hedera transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Hedera API", "Hedera Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Transactions API offers insights into transactions on the Hedera Blockchain. @@ -41,4 +62,12 @@ The Transactions API offers insights into transactions on the Hedera Blockchain. - `transactionHash`: Returns the hash of the transaction. - `transactionType`: Returns the type of the transaction. - `transactionValidDurationInSec`: Returns the duration of the transaction in seconds. -- `validStart`: Returns the timestamp when the transaction validity starts. \ No newline at end of file +- `validStart`: Returns the timestamp when the transaction validity starts. + +## Related Resources + +- [Hedera schema overview](https://docs.bitquery.io/v1/docs/Schema/hedera/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Hedera Coinpath API](https://docs.bitquery.io/v1/docs/Schema/hedera/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/ripple/accountRoots.md b/docs/Schema/ripple/accountRoots.md index b3a61c4..e12b8d8 100644 --- a/docs/Schema/ripple/accountRoots.md +++ b/docs/Schema/ripple/accountRoots.md @@ -1,5 +1,6 @@ --- title: "Ripple Account Roots API" +description: "Query AccountRoot fields for XRP Ledger accounts." --- @@ -86,4 +87,13 @@ query MyQuery { - **domain** - The domain of the account. This is the domain that the account is associated with. - **balance** - - The current balance of the account \ No newline at end of file + - The current balance of the account + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/address.md b/docs/Schema/ripple/address.md index c2837e3..27bff9e 100644 --- a/docs/Schema/ripple/address.md +++ b/docs/Schema/ripple/address.md @@ -1,5 +1,6 @@ --- title: Ripple Address API +description: "Look up address balances and history on the XRP Ledger." --- @@ -102,3 +103,12 @@ query ($address: String!, $network: RippleNetwork!) { - `sendAmount`: The total amount of XRP that has been sent by the wallet. - `lastTransferAt`: The timestamp of the most recent transfer to or from the wallet. - `lastTxAt`: The timestamp of the most recent transaction involving the wallet. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/addressStats.md b/docs/Schema/ripple/addressStats.md index 560c6fe..b49c94e 100644 --- a/docs/Schema/ripple/addressStats.md +++ b/docs/Schema/ripple/addressStats.md @@ -1,5 +1,6 @@ --- title: "Ripple Addresses Stats API" +description: "Query aggregate address statistics on the XRP Ledger." --- @@ -65,4 +66,13 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s -- `address`: Returns statistics for the blockchain address \ No newline at end of file +- `address`: Returns statistics for the blockchain address + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/balances.md b/docs/Schema/ripple/balances.md index c569c50..92bbfa3 100644 --- a/docs/Schema/ripple/balances.md +++ b/docs/Schema/ripple/balances.md @@ -1,5 +1,6 @@ --- title: "Ripple Balances API" +description: "Query account balances and balance history on the XRP Ledger." --- @@ -134,3 +135,12 @@ query ($network: RippleNetwork!, $address: String!, $from: ISO8601DateTime, $til - `balance`: This field specifies the balance of the account after the transaction. - `account`: This field specifies the account that owns the balance. - `flags`: This field specifies the flags of the transaction. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/blocks.md b/docs/Schema/ripple/blocks.md index e265dbf..cb78a2a 100644 --- a/docs/Schema/ripple/blocks.md +++ b/docs/Schema/ripple/blocks.md @@ -1,5 +1,6 @@ --- title: "Ripple Blocks API" +description: "Query validated XRP Ledger ledgers (blocks), timestamps, and transaction counts." --- @@ -54,4 +55,13 @@ query ($network: RippleNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) "till": "2023-08-15T09:31:24.000Z", "dateFormat": "%Y-%m-%d" } -``` \ No newline at end of file +``` + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/checks.md b/docs/Schema/ripple/checks.md index a912035..333d9f4 100644 --- a/docs/Schema/ripple/checks.md +++ b/docs/Schema/ripple/checks.md @@ -1,5 +1,6 @@ --- title: "Ripple Checks API" +description: "Query Checks (deferred payments) on the XRP Ledger." --- @@ -115,3 +116,12 @@ query ($network: RippleNetwork!) { - `send_max_usd`: The maximum amount that can be redeemed from the check in USD. - `currency`: The currency of the check. - `operation`: The type of check that was created. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/coinpath.md b/docs/Schema/ripple/coinpath.md index cbd3716..d11d6ac 100644 --- a/docs/Schema/ripple/coinpath.md +++ b/docs/Schema/ripple/coinpath.md @@ -1,5 +1,6 @@ --- title: Ripple Coinpath API +description: "Track fund flows on the XRP Ledger with coinpath." --- @@ -172,3 +173,12 @@ query ($network: RippleNetwork!, $address: String!, $inboundDepth: Int!, $outbou - `count`: This field specifies the number of transactions that were involved in the flow of funds. - `currencyFrom`: This field specifies the currency that the funds were originally held in, if the funds were converted. - `transaction`: This field specifies the transaction that was used to transfer the funds. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/escrows.md b/docs/Schema/ripple/escrows.md index ebb8574..f592c0f 100644 --- a/docs/Schema/ripple/escrows.md +++ b/docs/Schema/ripple/escrows.md @@ -1,5 +1,6 @@ --- title: Ripple Escrows API +description: "Query escrows, accounts, and amounts on the XRP Ledger." --- @@ -142,3 +143,12 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date - `flags` - The flags for the escrow. - `destinationTag` - The destination tag for the escrow. - `condition` - The condition for the escrow. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/nftokenOffers.md b/docs/Schema/ripple/nftokenOffers.md index 05ed8e9..3aafe42 100644 --- a/docs/Schema/ripple/nftokenOffers.md +++ b/docs/Schema/ripple/nftokenOffers.md @@ -1,5 +1,6 @@ --- title: Ripple NFToken API +description: "Query NFToken offers and taker details on the XRP Ledger." --- @@ -137,3 +138,12 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!) { - `flags`: The flags of the offer. - `bookNode`: The book node of the offer. - `bookDirectory`: The book directory of the offer. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/offers.md b/docs/Schema/ripple/offers.md index e1075d7..69ba301 100644 --- a/docs/Schema/ripple/offers.md +++ b/docs/Schema/ripple/offers.md @@ -1,5 +1,6 @@ --- title: Ripple Offers API +description: "Query decentralized exchange offers on the XRP Ledger." --- @@ -179,3 +180,12 @@ query MyQuery { - The address of the account that created the offer. - **annotation** - A label to store any additional information about the address. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/overview.md b/docs/Schema/ripple/overview.md index 236fd48..40a9730 100644 --- a/docs/Schema/ripple/overview.md +++ b/docs/Schema/ripple/overview.md @@ -1,3 +1,25 @@ +--- +sidebar_position: 1 +title: "Ripple API — Blockchain Data Schema | Bitquery" +description: "Access Ripple blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Ripple API, Ripple GraphQL, Ripple blockchain data, Bitquery] +--- + + + + + + + + + + + + + + + + # Overview Bitquery's Ripple APIs give you information on the XRP's blocks, transactions, addresses, offers, payments and so on. @@ -19,4 +41,12 @@ query{ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/ripple/payments.md b/docs/Schema/ripple/payments.md index 7d86980..01e8446 100644 --- a/docs/Schema/ripple/payments.md +++ b/docs/Schema/ripple/payments.md @@ -1,5 +1,6 @@ --- title: Ripple Payments API +description: "Query Ripple payment transactions, issuers, and amounts." --- @@ -159,3 +160,12 @@ query ($network: RippleNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) - `deliverMinIssuer` - The issuer of the minimum amount that was delivered. - `deliveredAmount` - The amount that was delivered. - `deliverMinCurrency` - The currency of the minimum amount that was delivered. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/rippleStates.md b/docs/Schema/ripple/rippleStates.md index f80500f..8fa56d2 100644 --- a/docs/Schema/ripple/rippleStates.md +++ b/docs/Schema/ripple/rippleStates.md @@ -1,5 +1,6 @@ --- title: Ripple States API +description: "Query RippleState objects for trust lines and balances." --- @@ -111,3 +112,12 @@ query ($network: RippleNetwork!) { - `prevLedgerSequence`: The ledger sequence of the previous transaction, if any. - `timestamp`: The timestamp of the transaction that created the RippleState object. - `transaction`: The transaction that created the RippleState object. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/transactions.md b/docs/Schema/ripple/transactions.md index 638f8ba..8c5f24f 100644 --- a/docs/Schema/ripple/transactions.md +++ b/docs/Schema/ripple/transactions.md @@ -1,5 +1,6 @@ --- title: Ripple Transactions API +description: "Query XRP Ledger transactions and outcomes." --- @@ -104,3 +105,12 @@ query ($from: ISO8601DateTime, $till: ISO8601DateTime) { - `txSigners`: The signers of the transaction. - `type`: The type of the transaction. - `timestamp`: The timestamp of the transaction. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/ripple/transfers.md b/docs/Schema/ripple/transfers.md index 6417a4c..fae6dde 100644 --- a/docs/Schema/ripple/transfers.md +++ b/docs/Schema/ripple/transfers.md @@ -1,5 +1,6 @@ --- title: Ripple Transfers API +description: "Query currency and token transfers on the XRP Ledger." --- @@ -137,3 +138,12 @@ query ($network: RippleNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) - `receiver`: The address of the receiver. - `sender`: The address of the sender. - `transaction`: The transaction ID of the transfer. + +## Related Resources + +- [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) +- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/solana/address.md b/docs/Schema/solana/address.md index 276a47f..be4617c 100644 --- a/docs/Schema/solana/address.md +++ b/docs/Schema/solana/address.md @@ -1,3 +1,24 @@ +--- +title: "Solana Address API" +description: "Query Solana address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Solana API", "Solana Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The Solana address API gives you information of the balance of a wallet in SOL. @@ -41,3 +62,10 @@ The balance of the account in SOL. The balance of the account. +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/blockRewards.md b/docs/Schema/solana/blockRewards.md index 4aecbea..63df2c0 100644 --- a/docs/Schema/solana/blockRewards.md +++ b/docs/Schema/solana/blockRewards.md @@ -1,3 +1,24 @@ +--- +title: "Solana Block Rewards API" +description: "Query Solana block rewards data using Bitquery GraphQL API. Get block reward distributions, validators, and amounts." +keywords: ["Solana API", "Solana Block Rewards", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Block Rewards The BlockRewards API returns information about rewards on the Solana network. Solana implements a proof of stake reward scheme for validator nodes. Rewards are paid every epoch. @@ -87,4 +108,12 @@ query ($network: SolanaNetwork!, $date: ISO8601DateTime, $height: Int) { `postBalance`: The balance of the account after the reward was issued. -`time`: The timestamp the reward was issued. \ No newline at end of file +`time`: The timestamp the reward was issued. + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/blocks.md b/docs/Schema/solana/blocks.md index 2ac2ed1..7c1611e 100644 --- a/docs/Schema/solana/blocks.md +++ b/docs/Schema/solana/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Solana Blocks API" +description: "Query Solana blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Solana API", "Solana Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The Blocks API returns information about blocks on the Solana network. The fields in the schema include: @@ -48,4 +69,12 @@ query ($network: SolanaNetwork!,$from: ISO8601DateTime, $till: ISO8601DateTime) `any`: This field allows you to filter blocks by any of the other fields (OR logic). `transactionCount`: This field allows you to filter blocks by the number of transactions they contain. - \ No newline at end of file + + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/coinpath.md b/docs/Schema/solana/coinpath.md index 4263677..8953548 100644 --- a/docs/Schema/solana/coinpath.md +++ b/docs/Schema/solana/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Solana Coinpath API" +description: "Query Solana coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Solana API", "Solana Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The Solana Coinpath API allows you to get the money flow for an address on the Solana blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. @@ -166,4 +187,11 @@ The depth of the connection between the two addresses. `signature` -The signature of the transfer. \ No newline at end of file +The signature of the transfer. + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/instructionAccounts.md b/docs/Schema/solana/instructionAccounts.md index f8b8681..ee66e06 100644 --- a/docs/Schema/solana/instructionAccounts.md +++ b/docs/Schema/solana/instructionAccounts.md @@ -1,3 +1,24 @@ +--- +title: "Solana Instruction Accounts API" +description: "Query Solana instruction accounts data using Bitquery GraphQL API. Get accounts referenced by each instruction." +keywords: ["Solana API", "Solana Instruction Accounts", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # InstructionAccounts This API returns information about the accounts involved in an instruction. An instruction is the smallest execution logic on Solana. One transaction can have 1 or more instructions. Below are the fields in the API: @@ -215,4 +236,12 @@ This field filters the results by the index of the account that was affected by - **transactionIndex** - This field is a unique identifier for the transaction within the block. \ No newline at end of file + This field is a unique identifier for the transaction within the block. + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/instructions.md b/docs/Schema/solana/instructions.md index 9a6dab4..bbc5fee 100644 --- a/docs/Schema/solana/instructions.md +++ b/docs/Schema/solana/instructions.md @@ -1,3 +1,24 @@ +--- +title: "Solana Instructions API" +description: "Query Solana instructions data using Bitquery GraphQL API. Get program instructions, programs, and instruction-level data." +keywords: ["Solana API", "Solana Instructions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Instructions The Solana instructions API allows you to query information about instructions that have been executed on the Solana blockchain. This information includes the program that executed the instruction, the accounts that were affected by the instruction, the data that was passed to the instruction, and the log message that was produced by the instruction. The schema includes the following fields: @@ -59,3 +80,10 @@ query ($network: SolanaNetwork!, $signature: String!) { ## Fields +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/overview.md b/docs/Schema/solana/overview.md index 106d176..2aa07fd 100644 --- a/docs/Schema/solana/overview.md +++ b/docs/Schema/solana/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Solana API — Blockchain Data Schema | Bitquery" +description: "Access Solana blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Solana API, Solana GraphQL, Solana blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery API offers access to indexed data from the Solana blockchain. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -22,4 +40,12 @@ query MyQuery { Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Solana API examples](https://docs.bitquery.io/v1/docs/Examples/Solana) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/solana/transactions.md b/docs/Schema/solana/transactions.md index 28e53fa..c1c2d05 100644 --- a/docs/Schema/solana/transactions.md +++ b/docs/Schema/solana/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Solana Transactions API" +description: "Query Solana transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Solana API", "Solana Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Solana transactions API allows you to query for transactions on the Solana blockchain. You can use this API to get information about specific transactions, such as the signature, block, transaction fee, success, fee payer, inner instructions count, instructions count, signer, and transaction index. @@ -96,4 +117,12 @@ accountsCount: This field allows you to filter transactions by the number of acc `signer`: The account that signed the transaction. -`transactionIndex`: The index of the transaction in the block. \ No newline at end of file +`transactionIndex`: The index of the transaction in the block. + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/solana/transfers.md b/docs/Schema/solana/transfers.md index 152622d..2a2d9da 100644 --- a/docs/Schema/solana/transfers.md +++ b/docs/Schema/solana/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Solana Transfers API" +description: "Query Solana transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Solana API", "Solana Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The transfers API allows you to get a information on transfers that have occurred on the Solana blockchain.Below are the fields in the schema: @@ -334,4 +355,12 @@ A catch-all filter (OR Logic) that can be used to filter the results by any of t - **type** - The type of the action. - **program** - - The program ID of the program that was used to perform the transfer. \ No newline at end of file + - The program ID of the program that was used to perform the transfer. + +## Related Resources + +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Solana Coinpath API](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/address.md b/docs/Schema/stellar/address.md index 7c21f60..a031329 100644 --- a/docs/Schema/stellar/address.md +++ b/docs/Schema/stellar/address.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Address API" +description: "Query Stellar address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Stellar API", "Stellar Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address Stellar Address API helps you get information on Address balance in the network. Below are the fields in the API: @@ -57,3 +78,11 @@ query ($network: StellarNetwork!) { - **assetType** The type of the asset. This can be either `native` (for XLM) or `credit_alphanum4` (for other assets). - **balance** The balance of the account in the asset. - **assetCode** The symb of the asset. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/addressStats.md b/docs/Schema/stellar/addressStats.md index f6d7e3e..779c039 100644 --- a/docs/Schema/stellar/addressStats.md +++ b/docs/Schema/stellar/addressStats.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Address Stats API" +description: "Query Stellar address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["Stellar API", "Stellar Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # AddressStats Stellar AddressStats API helps you get information on Addresses in the network. Below are the fields in the API: @@ -118,3 +139,10 @@ query ($address: String!, $network: StellarNetwork!) { - **lastTxAt** : The timestamp of the most recent transaction to or from the address. +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/balanceEffects.md b/docs/Schema/stellar/balanceEffects.md index f683d59..9407fdc 100644 --- a/docs/Schema/stellar/balanceEffects.md +++ b/docs/Schema/stellar/balanceEffects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Balance Effects API" +description: "Query Stellar balance effects data using Bitquery GraphQL API. Get balance changes, trust lines, and liabilities." +keywords: ["Stellar API", "Stellar Balance Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # BalanceEffects The Stellar BalanceEffects API allows you to get information about the balance changes of an account.Below are the fields in the API: @@ -94,3 +115,11 @@ query ($network: StellarNetwork!, $address: String!, $from: ISO8601DateTime, $ti - **order** : The order of the balance effect in the list of balance effects. - **timestamp** : The timestamp of the balance change. - **transaction** : The transaction hash that caused the balance change. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/blocks.md b/docs/Schema/stellar/blocks.md index 215c68d..c39a209 100644 --- a/docs/Schema/stellar/blocks.md +++ b/docs/Schema/stellar/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Blocks API" +description: "Query Stellar blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Stellar API", "Stellar Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks Stellar Blocks API helps you get information on Blocks in the network. Below are the fields in the API: @@ -57,3 +78,11 @@ query ($network: StellarNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - **maxTxSetSize** : The maximum size of a transaction set that can be included in a block. - **baseReserve** : The base reserve of the ledger at the time of the block. - **baseFee** : The base fee of the ledger at the time of the block. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/claimableBalanceEffects.md b/docs/Schema/stellar/claimableBalanceEffects.md index 13c74db..f7ac87b 100644 --- a/docs/Schema/stellar/claimableBalanceEffects.md +++ b/docs/Schema/stellar/claimableBalanceEffects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Claimable Balance Effects API" +description: "Query Stellar claimable balance data using Bitquery GraphQL API. Get claimable balance claimants, assets, and predicates." +keywords: ["Stellar API", "Stellar Claimable Balance Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Claimable BalanceEffects Claimable balance allows stellar wallets to send payments in parts.The claimable balance is recorded on the Stellar ledger. Read more [here](https://developers.stellar.org/docs/encyclopedia/claimable-balances) @@ -191,3 +212,11 @@ This field allows you to control the pagination and sorting of the results. The - **transaction** The transaction that created the claimable balance effect. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/coinpath.md b/docs/Schema/stellar/coinpath.md index 1b15f38..10e3f97 100644 --- a/docs/Schema/stellar/coinpath.md +++ b/docs/Schema/stellar/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Coinpath API" +description: "Query Stellar coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Stellar API", "Stellar Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The Coinpath API allows you to get the money flow for an address on the Stellar blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. @@ -151,3 +172,10 @@ query ($network: StellarNetwork!, $address: String!, $from: ISO8601DateTime, $ti - **currencyFrom** The asset that was sent from the sender's account in native asset (XLM) + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/effectArguments.md b/docs/Schema/stellar/effectArguments.md index 954fc97..52f0fa8 100644 --- a/docs/Schema/stellar/effectArguments.md +++ b/docs/Schema/stellar/effectArguments.md @@ -1,5 +1,34 @@ +--- +title: "Stellar Effect Arguments API" +description: "Query Stellar effect arguments data using Bitquery GraphQL API. Get arguments and parameters for Stellar effects." +keywords: ["Stellar API", "Stellar Effect Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Effects Arguments
Filtering Transfers
-## Fields \ No newline at end of file +## Fields + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/effects.md b/docs/Schema/stellar/effects.md index 0f15277..f2f3ade 100644 --- a/docs/Schema/stellar/effects.md +++ b/docs/Schema/stellar/effects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Effects API" +description: "Query Stellar effects data using Bitquery GraphQL API. Get ledger effects, operations, and asset movements." +keywords: ["Stellar API", "Stellar Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Effects According to the Stellar documentation, @@ -151,3 +172,11 @@ query ($network: StellarNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - **address** The account that is the subject of the effect. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/liquidityPoolEffects.md b/docs/Schema/stellar/liquidityPoolEffects.md index d4d5734..0ad6f5b 100644 --- a/docs/Schema/stellar/liquidityPoolEffects.md +++ b/docs/Schema/stellar/liquidityPoolEffects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Liquidity Pool Effects API" +description: "Query Stellar liquidity pool effects data using Bitquery GraphQL API. Get liquidity pool changes, reserves, and shares." +keywords: ["Stellar API", "Stellar Liquidity Pool Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Liquidity PoolEffects Liquidity pools on Stellar support AMMs. Bitquery's LiquidityPoolEffects API gives you effects information regarding liquidity pools. The following are the fields in the schema: @@ -208,3 +229,11 @@ query MyQuery { - **transaction** The transaction that created the liquidity pool trade effect. This includes the hash, index, and sender of the transaction. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/liquidityPoolTradeEffects.md b/docs/Schema/stellar/liquidityPoolTradeEffects.md index 9581358..2a2a19a 100644 --- a/docs/Schema/stellar/liquidityPoolTradeEffects.md +++ b/docs/Schema/stellar/liquidityPoolTradeEffects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Liquidity Pool Trade Effects API" +description: "Query Stellar liquidity pool data using Bitquery GraphQL API. Get liquidity pool trades, reserves, and pool participants." +keywords: ["Stellar API", "Stellar Liquidity Pool Trade Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Liquidity Pool Trade Effects Liquidity pools on Stellar support AMMs. Bitquery's Liquidity TradePoolEffects API gives you trade effects information regarding liquidity pools. The following are the fields in the schema: @@ -212,3 +233,11 @@ query ($network: StellarNetwork!) { - **address** The address of the account that was affected by the liquidity pool trade effect. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/operations.md b/docs/Schema/stellar/operations.md index 1b0cdd3..207000e 100644 --- a/docs/Schema/stellar/operations.md +++ b/docs/Schema/stellar/operations.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Operations API" +description: "Query Stellar operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +keywords: ["Stellar API", "Stellar Operations", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Operations An operation is a command that tells the Stellar network to do something, such as send money, or create an account. A transaction is a group of operations that are submitted to the Stellar network together. @@ -108,3 +129,11 @@ query ($network: StellarNetwork!, $hash: String!) { - **success** A boolean value that indicates whether the operation was successful. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/overview.md b/docs/Schema/stellar/overview.md index a0e3b32..10171cc 100644 --- a/docs/Schema/stellar/overview.md +++ b/docs/Schema/stellar/overview.md @@ -1,3 +1,25 @@ +--- +sidebar_position: 1 +title: "Stellar API — Blockchain Data Schema | Bitquery" +description: "Access Stellar blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Stellar API, Stellar GraphQL, Stellar blockchain data, Bitquery] +--- + + + + + + + + + + + + + + + + # Overview Bitquery's Stellar APIs give you information on the network's blocks, transactions, addresses, operations, payments and so on. @@ -13,4 +35,12 @@ query{ __typename } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Stellar API examples](https://docs.bitquery.io/v1/docs/Examples/stellar) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) diff --git a/docs/Schema/stellar/payments.md b/docs/Schema/stellar/payments.md index f44ced1..ffec85c 100644 --- a/docs/Schema/stellar/payments.md +++ b/docs/Schema/stellar/payments.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Payments API" +description: "Query Stellar payments data using Bitquery GraphQL API. Get payment operations and path payments." +keywords: ["Stellar API", "Stellar Payments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Payments Stellar network is optimized for payments. Bitquery's Payments API will give you information on payments on the XRP ledger. Below are the fields in the schema: @@ -240,3 +261,11 @@ query ($network: StellarNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - **path** The path that the payment took through the Stellar network. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/tradeEffects.md b/docs/Schema/stellar/tradeEffects.md index 5d5d1d7..3e6a410 100644 --- a/docs/Schema/stellar/tradeEffects.md +++ b/docs/Schema/stellar/tradeEffects.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Trade Effects API" +description: "Query Stellar trade effects data using Bitquery GraphQL API. Get trade effects, offers, and asset changes." +keywords: ["Stellar API", "Stellar Trade Effects", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Trade Effects When an offer is fully or partially fulfilled, a trade happens. Trade Effects capture the effects wrt trades. Below are the fields in the schema: @@ -203,3 +224,11 @@ query ($network: StellarNetwork!, $hash: String!) { - **offerId** The ID of the offer that was involved in the trade. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/transactions.md b/docs/Schema/stellar/transactions.md index 5dcc3b2..ca52a92 100644 --- a/docs/Schema/stellar/transactions.md +++ b/docs/Schema/stellar/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Transactions API" +description: "Query Stellar transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Stellar API", "Stellar Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions > Transactions comprise a bundle of between 1-100 operations and are @@ -203,3 +224,11 @@ The memos that were included in the transaction. This is an array of objects tha - **memoType** The type of memo that was included in the transaction. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/stellar/transfers.md b/docs/Schema/stellar/transfers.md index 394ed11..aeb5a4c 100644 --- a/docs/Schema/stellar/transfers.md +++ b/docs/Schema/stellar/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Stellar Transfers API" +description: "Query Stellar transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Stellar API", "Stellar Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers Bitquery's Stellar transfers API provides you the following information: @@ -186,3 +207,11 @@ query ($network: StellarNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime - **operation** The operation that created the transfer. + +## Related Resources + +- [Stellar schema overview](https://docs.bitquery.io/v1/docs/Schema/stellar/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Stellar Coinpath API](https://docs.bitquery.io/v1/docs/Schema/stellar/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/address.md b/docs/Schema/tezos/address.md index 7bbc7a0..5209ee1 100644 --- a/docs/Schema/tezos/address.md +++ b/docs/Schema/tezos/address.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Address API" +description: "Query Tezos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Tezos API", "Tezos Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` API allows you to retrieve detailed information about addresses from the Tezos blockchain. @@ -29,4 +50,12 @@ Here's an example query that demonstrates how to fetch address details: - `address`: Returns the address itself - `annotation`: Provides any available annotation associated with the address -- `balance`: Returns the balance of the address, including staking balance, delegated balance, and total balance \ No newline at end of file +- `balance`: Returns the balance of the address, including staking balance, delegated balance, and total balance + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/arguments.md b/docs/Schema/tezos/arguments.md index 6d6dfa6..d034224 100644 --- a/docs/Schema/tezos/arguments.md +++ b/docs/Schema/tezos/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Arguments API" +description: "Query Tezos GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Tezos API", "Tezos Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The Arguments API provides you with information about arguments. @@ -100,3 +121,11 @@ You can filter arguments using the following fields: - `timestamp`: Returns the timestamp of the transaction. - `transaction`: Returns details of the transaction where the transfer is included. + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/balanceUpdates.md b/docs/Schema/tezos/balanceUpdates.md index bf0745b..f25ae90 100644 --- a/docs/Schema/tezos/balanceUpdates.md +++ b/docs/Schema/tezos/balanceUpdates.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Balance Updates API" +description: "Query Tezos balance updates data using Bitquery GraphQL API. Get balance updates, contracts, and token movements." +keywords: ["Tezos API", "Tezos Balance Updates", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Balance Updates The balanceUpdates API allows you to retrieve information about balance updates for a specific address. @@ -61,3 +82,11 @@ You can filter balance updates data using the following fields: - `source`: returns the source of the transaction - `timestamp`: returns the timestamp of the transaction - `transaction`: returns details of the transaction + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/blocks.md b/docs/Schema/tezos/blocks.md index dfeaaf1..d2900af 100644 --- a/docs/Schema/tezos/blocks.md +++ b/docs/Schema/tezos/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Blocks API" +description: "Query Tezos blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Tezos API", "Tezos Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The Blocks API provides information about the blocks created on the Tezos blockchain. @@ -66,3 +87,10 @@ You can filter blocks data using the following fields: - `timestamp`: returns the timestamp of the block. +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/coinpath.md b/docs/Schema/tezos/coinpath.md index 87950a6..3751b4b 100644 --- a/docs/Schema/tezos/coinpath.md +++ b/docs/Schema/tezos/coinpath.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Coinpath API" +description: "Query Tezos coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Tezos API", "Tezos Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Coinpath The Coinpath API provides information about the movement of funds within the Tezos Blockchain. @@ -34,3 +55,10 @@ You can filter the returned data using the following criteria: - `receiver`: returns the receiver of the transfer. - `sender`: returns the sender of the transfer. - `transaction`: returns details about the transaction where the transfer occurred. + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/operations.md b/docs/Schema/tezos/operations.md index 04d0ca7..3b6ce29 100644 --- a/docs/Schema/tezos/operations.md +++ b/docs/Schema/tezos/operations.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Operations API" +description: "Query Tezos operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +keywords: ["Tezos API", "Tezos Operations", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Operations The Tezos Operations API provides information about operations from the Tezos Blockchain. @@ -47,3 +68,11 @@ You can filter the operations using the following fields: - `success`: indicates the success of the operation. - `timestamp`: returns the timestamp of the operation. - `transaction`: returns details about the transaction. + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/transactions.md b/docs/Schema/tezos/transactions.md index 32aacb0..a59f6d6 100644 --- a/docs/Schema/tezos/transactions.md +++ b/docs/Schema/tezos/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Transactions API" +description: "Query Tezos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Tezos API", "Tezos Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions The Tezos Transactions API allows you to retrieve information about transactions on the Tezos blockchain. @@ -68,3 +89,11 @@ You can filter transactions using various field: - `storageSize`: returns the storage size. - `success`: indicates the success of the transaction. - `timestamp`: returns the timestamp of the transaction. + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tezos/transfers.md b/docs/Schema/tezos/transfers.md index 278293d..f367dd4 100644 --- a/docs/Schema/tezos/transfers.md +++ b/docs/Schema/tezos/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Tezos Transfers API" +description: "Query Tezos transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Tezos API", "Tezos Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers The Tezos Transfers API provides information about the transfers on the Tezos Blockchain. @@ -51,4 +72,12 @@ You can filter transfers using the following fields: - `receiver`: returns the address of the transfer receiver. - `sender`: returns the address of the transfer sender. - `timestamp`: returns the timestamp of the transfer. -- `transaction`: returns details about the transaction where the transfer is included. \ No newline at end of file +- `transaction`: returns details about the transaction where the transfer is included. + +## Related Resources + +- [Tezos schema overview](https://docs.bitquery.io/v1/docs/Schema/tezos/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/tron/address.md b/docs/Schema/tron/address.md index 472b1c7..1c718f6 100644 --- a/docs/Schema/tron/address.md +++ b/docs/Schema/tron/address.md @@ -1,5 +1,6 @@ --- title: Tron Address API +description: "Look up address balances and history on Tron." --- @@ -52,3 +53,12 @@ Address data can be filtered using the following arguments: - `balances`: returns token balance history of address - `claimableRewards`: returns rewards that a witness or a user has not yet withdrawn - `smartContract`: returns details is address is smart contract + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/arguments.md b/docs/Schema/tron/arguments.md index 8f63f53..26447ee 100644 --- a/docs/Schema/tron/arguments.md +++ b/docs/Schema/tron/arguments.md @@ -1,5 +1,6 @@ --- title: Tron Arguments API +description: "Query event and call arguments on Tron smart contracts." --- @@ -107,3 +108,12 @@ Here is an example that demonstrates how to use `arguments` query: - `txHash`: returns transaction hash - `txIndex`: returns transaction index in block - `value`: returns value of method or event argument + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/blocks.md b/docs/Schema/tron/blocks.md index f80f3b9..a632607 100644 --- a/docs/Schema/tron/blocks.md +++ b/docs/Schema/tron/blocks.md @@ -1,5 +1,6 @@ --- title: Tron Blocks API +description: "Query Tron blocks, transactions, fees, and timestamps." --- @@ -80,3 +81,12 @@ Here is an example that demonstrates how to retrieve blocks data: - `version`: returns block version - `witness`: returns block witness - `witnessSignature`: returns block witness signature + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/coinpath.md b/docs/Schema/tron/coinpath.md index e366a2a..efcc51a 100644 --- a/docs/Schema/tron/coinpath.md +++ b/docs/Schema/tron/coinpath.md @@ -1,5 +1,6 @@ --- title: Tron Coinpath API +description: "Track fund flows up to any depth on Tron with coinpath." --- @@ -53,3 +54,12 @@ Coinpath data can be filtered using following arguments: - `receiver`: returns receiver address - `sender`: returns sender address - `transaction`: returns transaction of transfer happened + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/contracts.md b/docs/Schema/tron/contracts.md index d95fd88..a0b2a4e 100644 --- a/docs/Schema/tron/contracts.md +++ b/docs/Schema/tron/contracts.md @@ -1,5 +1,6 @@ --- title: Tron Smart Contract API +description: "Query Tron smart contract deployment, energy, and fees." --- @@ -94,3 +95,12 @@ The following fields are available for the `contracts`: - `success`: returns is call was successful or not - `txHash`: returns transaction hash - `txOwner`: returns address of transaction owner + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/dexTrades.md b/docs/Schema/tron/dexTrades.md index 1439baf..97b5c3d 100644 --- a/docs/Schema/tron/dexTrades.md +++ b/docs/Schema/tron/dexTrades.md @@ -1,5 +1,6 @@ --- title: Tron DEX Trades API +description: "Query DEX trades, pools, and pairs on Tron." --- @@ -144,3 +145,12 @@ The following fields are available for the `dexTrades`: - `tradeAmount`: returns trade amount - `tradeIndex`: returns index of trade in the transaction - `transaction`: returns details of transaction + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/overview.md b/docs/Schema/tron/overview.md index 80a57a7..5d656bc 100644 --- a/docs/Schema/tron/overview.md +++ b/docs/Schema/tron/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Tron API — Blockchain Data Schema | Bitquery" +description: "Access Tron blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Tron API, Tron GraphQL, Tron blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Tron API Overview Bitquery's Tron API offers access to indexed data from the Tron network including shards, block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as shard information, transaction details, events, token transfers, and other relevant information. @@ -24,4 +42,12 @@ Let's dive in and explore the Tron data available through Bitquery API. Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. -::: \ No newline at end of file +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/tron/smartContractCalls.md b/docs/Schema/tron/smartContractCalls.md index eff89e5..bfdf2de 100644 --- a/docs/Schema/tron/smartContractCalls.md +++ b/docs/Schema/tron/smartContractCalls.md @@ -1,5 +1,6 @@ --- title: Tron Smart Contract Calls API +description: "Query smart contract calls and arguments on Tron." --- @@ -109,3 +110,12 @@ The following fields are available for `smartContractCalls`: - `success`: returns if call was success or not - `txFrom`: returns transaction from address - `txTo`: returns transaction to address + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/smartContractEvents.md b/docs/Schema/tron/smartContractEvents.md index 3085cb6..5edd202 100644 --- a/docs/Schema/tron/smartContractEvents.md +++ b/docs/Schema/tron/smartContractEvents.md @@ -1,5 +1,6 @@ --- title: Tron Smart Contract Events API +description: "Query smart contract events and logs on Tron." --- @@ -98,3 +99,12 @@ The following fields are available for `smartContractEvents`: - `txFrom`: returns transaction from address - `txHash`: returns transaction hash - `txTo`: returns transaction to address + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/transactions.md b/docs/Schema/tron/transactions.md index dd782b8..7bd12fc 100644 --- a/docs/Schema/tron/transactions.md +++ b/docs/Schema/tron/transactions.md @@ -1,5 +1,6 @@ --- title: Tron Transactions API +description: "Query Tron transactions, senders, fees, and success status." --- @@ -99,3 +100,12 @@ Here is an example that demonstrates how to fetch transaction data: - `result`: returns result message - `signatures`: returns signatures - `success`: returns if transaction is successful or not + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/tron/transfers.md b/docs/Schema/tron/transfers.md index d7498dd..50cdff4 100644 --- a/docs/Schema/tron/transfers.md +++ b/docs/Schema/tron/transfers.md @@ -1,5 +1,6 @@ --- title: Tron Transfers API +description: "Query TRC-20 and native transfers on Tron." --- @@ -96,4 +97,13 @@ Here is an example that demonstrates how to fetch transfers from a particular bl - `success`: returns success of transfer - `txFrom`: returns transaction from address - `txHash`: returns transaction hash -- `txTo`: returns transaction to address \ No newline at end of file +- `txTo`: returns transaction to address + +## Related Resources + +- [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) +- [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) +- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Documentation intro](https://docs.bitquery.io/v1/docs/intro) + diff --git a/docs/Schema/velas/activeaddresses.md b/docs/Schema/velas/activeaddresses.md index 05c0bee..f97a3a5 100644 --- a/docs/Schema/velas/activeaddresses.md +++ b/docs/Schema/velas/activeaddresses.md @@ -1,3 +1,24 @@ +--- +title: "Velas Active Addresses API" +description: "Query Velas active addresses data using Bitquery GraphQL API. Get active address counts and time-bucketed activity." +keywords: ["Velas API", "Velas Active Addresses", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the velas blockchain. @@ -40,3 +61,11 @@ The following are available fields for the `activeAddresses`: - `address`: returns the address and its annotation. - `count`: returns the aggregate count of active addresses. - `countBigInt`: returns the aggregate count of active addresses in `BigInt` format. + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/address.md b/docs/Schema/velas/address.md index 31046dd..ca5a908 100644 --- a/docs/Schema/velas/address.md +++ b/docs/Schema/velas/address.md @@ -1,3 +1,24 @@ +--- +title: "Velas Address API" +description: "Query Velas address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +keywords: ["Velas API", "Velas Address", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address The `address` allows us to retrieve information about a specific address. @@ -48,3 +69,11 @@ The following are available fields for the address: - `balance`: Returns the current balance of the address. - `balances`: Returns the balance history of the address. - `smartContract`: Returns details if the address is that of a smart contract. + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/addresstats.md b/docs/Schema/velas/addresstats.md index 7ef6e1a..3d4e664 100644 --- a/docs/Schema/velas/addresstats.md +++ b/docs/Schema/velas/addresstats.md @@ -1,3 +1,24 @@ +--- +title: "Velas Address Stats API" +description: "Query Velas address stats data using Bitquery GraphQL API. Get aggregate address statistics and activity metrics." +keywords: ["Velas API", "Velas Address Stats", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. @@ -41,3 +62,11 @@ Here is an example that demonstrates how to retrieve statistics about the USDT s - `address`: Returns statistics for the blockchain address + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/arguments.md b/docs/Schema/velas/arguments.md index 30cd138..5a7fe87 100644 --- a/docs/Schema/velas/arguments.md +++ b/docs/Schema/velas/arguments.md @@ -1,3 +1,24 @@ +--- +title: "Velas Arguments API" +description: "Query Velas GraphQL arguments data using Bitquery GraphQL API. Get query arguments, filters, and options for this schema." +keywords: ["Velas API", "Velas Arguments", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. @@ -70,3 +91,11 @@ The following are available fields for the `arguments`: - `success`: - `transaction`: returns transaction information - `value`: returns value of method or event argument + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/blocks.md b/docs/Schema/velas/blocks.md index 120266f..42f8bd6 100644 --- a/docs/Schema/velas/blocks.md +++ b/docs/Schema/velas/blocks.md @@ -1,3 +1,24 @@ +--- +title: "Velas Blocks API" +description: "Query Velas blocks data using Bitquery GraphQL API. Get block heights, hashes, timestamps, proposers, and protocol metadata." +keywords: ["Velas API", "Velas Blocks", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Blocks The `blocks` field allows us to retrieve information about the blocks from the velas blockchain. @@ -68,3 +89,10 @@ Blocks data can be filtered using following arguments: - `totalDifficulty`: returns the total difficulty. - `transactionCount`: returns the number of transactions included in the block. +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/coinpath.md b/docs/Schema/velas/coinpath.md index 0b950ff..a23856a 100644 --- a/docs/Schema/velas/coinpath.md +++ b/docs/Schema/velas/coinpath.md @@ -1,3 +1,23 @@ +--- +title: "Velas Coinpath API" +description: "Query Velas coinpath data using Bitquery GraphQL API. Get fund flows, hop paths, and address-level tracing across transfers." +keywords: ["Velas API", "Velas Coinpath", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Coinpath @@ -35,4 +55,11 @@ The following are available fields for the `coinpath`: - `receiver`: returns information about the receiver. - `sender`: returns information about the sender. - `transaction`: returns transaction details. -- `transactions`: returns attributes of transactions. \ No newline at end of file +- `transactions`: returns attributes of transactions. + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/dextrades.md b/docs/Schema/velas/dextrades.md index a71d811..26b2950 100644 --- a/docs/Schema/velas/dextrades.md +++ b/docs/Schema/velas/dextrades.md @@ -1,3 +1,24 @@ +--- +title: "Velas DEX Trades API" +description: "Query Velas DEX trades data using Bitquery GraphQL API. Get DEX swaps, pools, amounts, and trader addresses." +keywords: ["Velas API", "Velas DEX Trades", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. @@ -127,4 +148,11 @@ The following are available fields for the `dexTrades`: - `tradeAmount`: returns the trade amount in the base currency. - `tradeIndex`: returns the index of the trade in the transaction. - `transaction`: returns information about the transaction in which the trade was executed. - \ No newline at end of file + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/overview.md b/docs/Schema/velas/overview.md index fecb447..c3a4fd9 100644 --- a/docs/Schema/velas/overview.md +++ b/docs/Schema/velas/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Velas API — Blockchain Data Schema | Bitquery" +description: "Access Velas blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Velas API, Velas GraphQL, Velas blockchain data, Bitquery] --- + + + + + + + + + + + + + + + # Overview Bitquery Velas API offers access to indexed data from the velas blockchain via GraphQL API for developers. @@ -19,3 +37,11 @@ query { ``` Let's dive in and explore the Velas data available through Bitquery API. + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Velas API examples](https://docs.bitquery.io/v1/docs/Examples/velas) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/velas/references.md b/docs/Schema/velas/references.md index 24a6444..f07bd3b 100644 --- a/docs/Schema/velas/references.md +++ b/docs/Schema/velas/references.md @@ -1,3 +1,23 @@ +--- +title: "Velas References API" +description: "Query Velas schema references data using Bitquery GraphQL API. Get reference data and lookup tables for this network schema." +keywords: ["Velas API", "Velas References", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # References @@ -44,4 +64,12 @@ References can be filtered using following arguments: - `smartContract`: - `smartContractSignature`: - `success`: -- `transaction`: \ No newline at end of file +- `transaction`: + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/smartcontractcalls.md b/docs/Schema/velas/smartcontractcalls.md index 0491b0d..89ee014 100644 --- a/docs/Schema/velas/smartcontractcalls.md +++ b/docs/Schema/velas/smartcontractcalls.md @@ -1,3 +1,23 @@ +--- +title: "Velas Smart Contract Calls API" +description: "Query Velas smart contract calls data using Bitquery GraphQL API. Get contract calls, methods, inputs, and execution context." +keywords: ["Velas API", "Velas Smart Contract Calls", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Calls @@ -82,4 +102,12 @@ Smart Contract Calls can be filtered using following arguments: - `smartContract`: returns details of smart contract - `smartContractMethod`: returns details of method to which the call was made - `success`: returns if calls is successful or not -- `transaction`: returns details of the transaction in which smart contract call was executed \ No newline at end of file +- `transaction`: returns details of the transaction in which smart contract call was executed + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/smartcontractevents.md b/docs/Schema/velas/smartcontractevents.md index 7a249bb..340a186 100644 --- a/docs/Schema/velas/smartcontractevents.md +++ b/docs/Schema/velas/smartcontractevents.md @@ -1,3 +1,23 @@ +--- +title: "Velas Smart Contract Events API" +description: "Query Velas smart contract events data using Bitquery GraphQL API. Get contract events, logs, topics, and decoded payloads." +keywords: ["Velas API", "Velas Smart Contract Events", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + # Smart Contract Events @@ -69,3 +89,11 @@ Smart Contract Events can be filtered using following arguments: - `smartContract`: returns details of smart contract on which event happened - `smartContractEvent`: returns details about smart contract event like name, signature, and signature hash - `transaction`: returns details about transaction which emitted smart contract event + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/transactions.md b/docs/Schema/velas/transactions.md index 60ccdb2..80964cb 100644 --- a/docs/Schema/velas/transactions.md +++ b/docs/Schema/velas/transactions.md @@ -1,3 +1,24 @@ +--- +title: "Velas Transactions API" +description: "Query Velas transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +keywords: ["Velas API", "Velas Transactions", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transactions Bitquery `transactions` API allows you to retrieve all the blockchain transactions from velas Blockchain. @@ -110,4 +131,12 @@ Transactions can be filtered using following arguments: - `sender`: returns address of sender of a particular transaction - `success`: returns if transaction is success or not - `to`: returns address to which of a particular transaction was sent -- `txType`: returns transaction type \ No newline at end of file +- `txType`: returns transaction type + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Schema/velas/transfers.md b/docs/Schema/velas/transfers.md index 1318c6f..29f4274 100644 --- a/docs/Schema/velas/transfers.md +++ b/docs/Schema/velas/transfers.md @@ -1,3 +1,24 @@ +--- +title: "Velas Transfers API" +description: "Query Velas transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +keywords: ["Velas API", "Velas Transfers", "Bitquery", "GraphQL"] +--- + + + + + + + + + + + + + + + + # Transfers Bitquery `transfers` API allows you to retrieve currency or token transfers from velas Blockchain. @@ -111,4 +132,12 @@ Data retrieved using `transfers` can be filtered using following arguments: - `receiver`: returns receiver of a particular transfer - `sender`: returns sender of a particular transfer - `success`: returns boolean value for success of a particular transfer -- `transaction`: returns details of transaction in which a particular transfer \ No newline at end of file +- `transaction`: returns details of transaction in which a particular transfer + +## Related Resources + +- [Velas schema overview](https://docs.bitquery.io/v1/docs/Schema/velas/overview) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Velas Coinpath API](https://docs.bitquery.io/v1/docs/Schema/velas/coinpath) +- [GraphQL examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) diff --git a/docs/Use-Cases/crypto-ml-price-prediction.md b/docs/Use-Cases/crypto-ml-price-prediction.md index ffefe46..21112ec 100644 --- a/docs/Use-Cases/crypto-ml-price-prediction.md +++ b/docs/Use-Cases/crypto-ml-price-prediction.md @@ -1,8 +1,25 @@ --- +title: "Crypto Price Prediction with Machine Learning — Bitquery API Use Case" sidebar_position: 3 -description: In this tutorial, we'll explore how to use GraphQL to retrieve historical trading data and use machine learning with Python to build a simple cryptocurrency price prediction model. +description: "Learn how to fetch historical DEX trading data with GraphQL from the Bitquery API and build a Python Random Forest model for cryptocurrency price prediction." +keywords: [machine learning, cryptocurrency, GraphQL, Bitquery API, DEX, Python] --- + + + + + + + + + + + + + + + # Building an ML Model With Crypto Price Data Cryptocurrency markets are known for their volatility, making them a fascinating domain for data science and predictive modeling. In this tutorial, we'll explore how to use GraphQL to retrieve historical trading data and use machine learning with Python to build a simple cryptocurrency price prediction model. @@ -217,3 +234,11 @@ We preprocess the recent trading data and use our trained model for predictions. Predictions for Recent Prices: [1856.33533188 1876.33664406 1881.45406742 1855.9330] Thus, we have built an ML model with blockchain data using BitQuery DEX API to fetch Ethereum-based decentralized exchange (DEX) trading data. + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Use-Cases/react-example.md b/docs/Use-Cases/react-example.md index 64036e0..99c8022 100644 --- a/docs/Use-Cases/react-example.md +++ b/docs/Use-Cases/react-example.md @@ -1,8 +1,25 @@ --- +title: "React App with Bitquery GraphQL API — Tutorial" sidebar_position: 3 -description: In this tutorial we will see how to use Bitquery APIs with ReactJS +description: "Build a React app that shows top DEX gainers and losers using hooks, async data fetching, and the Bitquery GraphQL API for Ethereum trading data." +keywords: [React, GraphQL, Bitquery API, DEX, Ethereum, JavaScript] --- + + + + + + + + + + + + + + + # Using Bitquery APIs with ReactJS to get Top Gainers and Losers Below is a step-by-step tutorial on how to create a React application that displays the top gainers and losers on a particular date using React hooks, async/await for fetching data, and Bitquery V1 APIs for price information. @@ -213,3 +230,11 @@ export default GainersLosers; ``` That concludes the step-by-step guide for creating the `GainersLosers` component. This component demonstrates how to fetch and display data from a V1 API, manage state with hooks, and dynamically update the UI based on user interactions. + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Use-Cases/tradeAmount-heatmap.md b/docs/Use-Cases/tradeAmount-heatmap.md index 2f0349a..6f81a36 100644 --- a/docs/Use-Cases/tradeAmount-heatmap.md +++ b/docs/Use-Cases/tradeAmount-heatmap.md @@ -1,32 +1,23 @@ --- title: Visualizing Trade Volume as Heatmap with Python sidebar_position: 6 -description: In this tutorial, we'll walk you through how to visualize the trade volume of different Ethereum pairs in a Heatmap using Python, pandas, seaborn, matplotlib, and the Bitquery DEX Trades API. +description: "Visualize Ethereum DEX pair trade volume as a heatmap with Python, pandas, seaborn, matplotlib, and the Bitquery DEX Trades API." +keywords: [heatmap, Ethereum, DEX trades, Python, pandas, Bitquery API, trade volume, seaborn] --- - - - - - + + + - - - - - - - - + + - - - - + + In this tutorial, we'll walk you through how to visualize the trade volume of different Ethereum pairs in a Heatmap using Python, pandas, seaborn, matplotlib, and the Bitquery DEX Trades API. @@ -156,3 +147,11 @@ plt.show() The image will look something like the one below. If the data is skewed towards one pair ( large amount of trades), then it is better to filter it or find alternate methods to get a holistic view. ![heatmap](/img/heatmap.png) + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Use-Cases/tradingview.md b/docs/Use-Cases/tradingview.md index 3e5a190..5e3d12c 100644 --- a/docs/Use-Cases/tradingview.md +++ b/docs/Use-Cases/tradingview.md @@ -1,7 +1,25 @@ --- +title: "TradingView Charts with Bitquery API — Integration Guide" sidebar_position: 1 +description: "Build candlestick charts for DEX token data using Bitquery GraphQL, React, Lightweight Charts, and Ethereum dexTrades—includes WETH pricing and OHLC aggregation." +keywords: [TradingView, Lightweight Charts, Bitquery API, DEX, Ethereum, React, blockchain charts] --- + + + + + + + + + + + + + + + # Build a tradingview chart app for blockchain data This tutorial will help you build a TradingView chart app with blockchain data from Bitquery. @@ -281,3 +299,11 @@ This is how it will look finally! ![chart](/img/tv.png) The full code is available in this repo here https://github.com/bitquery/Tradingview-Application + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [React tutorial — Bitquery APIs](https://docs.bitquery.io/v1/docs/Use-Cases/react-example) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Use-Cases/wordpress-wpgetapi.md b/docs/Use-Cases/wordpress-wpgetapi.md index c4eef8b..cc98dc7 100644 --- a/docs/Use-Cases/wordpress-wpgetapi.md +++ b/docs/Use-Cases/wordpress-wpgetapi.md @@ -1,8 +1,25 @@ --- +title: "WordPress Integration with Bitquery API via WPGetAPI" sidebar_position: 2 -description: In this tutorial, we'll use WPGetAPI plugin to show blockchain data on Wordpress sites. +description: "Connect WordPress to the Bitquery GraphQL endpoint with the WPGetAPI plugin: POST queries, JSON body, and shortcodes for on-site blockchain data." +keywords: [WordPress, WPGetAPI, Bitquery API, GraphQL, blockchain, DEX] --- + + + + + + + + + + + + + + + # Step-by-step guide on using the Bitquery API with WPGetAPI on WordPress **Prerequisites:** @@ -114,3 +131,11 @@ Finally set ``` [wpgetapi_endpoint api_id='bitquery_v1' endpoint_id='v1' debug='false'] ``` + +## Related Resources + +- [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) +- [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/building-queries/FAQ.md b/docs/building-queries/FAQ.md index 10e2de8..a27adc4 100644 --- a/docs/building-queries/FAQ.md +++ b/docs/building-queries/FAQ.md @@ -1,3 +1,24 @@ +--- +title: "Bitquery API FAQ — Frequently Asked Questions" +description: "Answers to common Bitquery API questions: DEX maker/taker, transfers vs transactions, USD price, priceAsymmetry, and token market cap." +keywords: [Bitquery, FAQ, GraphQL API, DEX, token price, market cap] +--- + + + + + + + + + + + + + + + + # Glossary and Frequently Asked Questions ## What is a maker and taker in a DEX Trade? @@ -180,3 +201,11 @@ In the following query, we will get the initial supply from the contract attribu ``` Note: In many cases token attributes shown as null in those cases you should find other ways to get supply of the token. + +## Related Resources + +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Expressions overview](https://docs.bitquery.io/v1/docs/query-features/expressions/overview) +- [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) diff --git a/docs/building-queries/basic-structure-of-a-query.md b/docs/building-queries/basic-structure-of-a-query.md index af74b22..2e7bff8 100644 --- a/docs/building-queries/basic-structure-of-a-query.md +++ b/docs/building-queries/basic-structure-of-a-query.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Understanding Bitquery Query Architecture — Cubes, Dimensions & Metrics" +description: "Learn how Bitquery models blockchain data as cubes with dimensions, metrics, and filters, and how GraphQL maps to ClickHouse analytics." +keywords: [Bitquery, GraphQL, cube, dimensions, metrics, query architecture] --- + + + + + + + + + + + + + + + # Basic Structure of A Query Bitquery Architechture @@ -60,4 +78,12 @@ Metrics look similar to Dimensions, however, they behave differently. For exampl ## Dataset and Filters -Datasets are types of data such as Ethereum and Binance smart chain, both are Ethereum type datasets because they are similar types of blockchains. Filters help in adding scope and range to queries. \ No newline at end of file +Datasets are types of data such as Ethereum and Binance smart chain, both are Ethereum type datasets because they are similar types of blockchains. Filters help in adding scope and range to queries. + +## Related Resources + +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) +- [Aggregation in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) +- [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) \ No newline at end of file diff --git a/docs/building-queries/network-selection.md b/docs/building-queries/network-selection.md index 042fcda..0fb7abb 100644 --- a/docs/building-queries/network-selection.md +++ b/docs/building-queries/network-selection.md @@ -1,7 +1,25 @@ --- sidebar_position: 2 +title: "Network Selection in Bitquery GraphQL API" +description: "Learn how to select blockchain networks in Bitquery API requests and use the IDE network filter for Ethereum and other chains." +keywords: [Bitquery, GraphQL, network selection, blockchain API, IDE] --- + + + + + + + + + + + + + + + # Network Selection When using Bitquery APIs, you can specify the network that you want to query. This is done by setting the network parameter in the request. @@ -14,3 +32,11 @@ Click on any chain, and in the list, let' say for example ethereum, you will fin ![network](/img/ide/network_selection.gif) +## Related Resources + +- [Understanding Bitquery query architecture](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Schema — Ethereum overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Query arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) +- [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) + diff --git a/docs/graphql-ide/account.md b/docs/graphql-ide/account.md index 730b5f5..60864c6 100644 --- a/docs/graphql-ide/account.md +++ b/docs/graphql-ide/account.md @@ -1,7 +1,32 @@ --- sidebar_position: 6 +title: "Bitquery Account Dashboard — API Usage, Billing & Stats" +description: "Use the Bitquery account dashboard for subscriptions, billing, API usage, points consumption, saved queries, errors, and blockchain system status." +keywords: + [ + Bitquery account, + API usage dashboard, + billing, + points consumption, + system status, + ] --- + + + + + + + + + + + + + + + # Your Account Dashboard Account dashboard gives you details related to your account like your subscriptions plan, API usage, frequently used queries etc. Let's epxlore each section on the page. @@ -32,4 +57,12 @@ The "Errors" section shows you number of errors, both accumulated since the crea ## System Status -This section offers a comprehensive system status overview for all the blockchains we support. It keeps you informed about any potential data delays, data quality concerns, or GraphQL API issues, ensuring transparency and allowing you to stay updated on the health of our services. \ No newline at end of file +This section offers a comprehensive system status overview for all the blockchains we support. It keeps you informed about any potential data delays, data quality concerns, or GraphQL API issues, ensuring transparency and allowing you to stay updated on the health of our services. + +## Related Resources + +- [What are API points?](https://docs.bitquery.io/v1/docs/graphql-ide/points) +- [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) +- [Common API errors and fixes](https://docs.bitquery.io/v1/docs/graphql-ide/errors) +- [Supported blockchains and status](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) +- [How to use the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) diff --git a/docs/graphql-ide/apikey.md b/docs/graphql-ide/apikey.md index b217884..3ba8d4a 100644 --- a/docs/graphql-ide/apikey.md +++ b/docs/graphql-ide/apikey.md @@ -1,7 +1,32 @@ --- sidebar_position: 2 +title: "Bitquery API Access Token — Create, Generate & Use OAuth Tokens" +description: "Create Bitquery applications, generate OAuth2 access tokens for V1 and V2 GraphQL APIs, use Bearer authentication, and revoke tokens securely." +keywords: + [ + Bitquery API key, + access token, + OAuth2, + Bearer token, + GraphQL authentication, + ] --- + + + + + + + + + + + + + + + # Getting the Access Token Update: We now use Access Token for both V1 and V2 APIs. You can access the token [here](https://account.bitquery.io/user/api_v2/access_tokens). @@ -111,3 +136,11 @@ If you no longer need an application, you can delete it by clicking **Delete** o Your Access Token is your identity in the system, you have to be very careful to whom and where you place your Access Token, as this will directly impact the performance of your account. ::: + +## Related Resources + +- [Use Bitquery in your application](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) +- [How to use the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) +- [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [V1 vs V2 APIs](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) +- [Account dashboard](https://docs.bitquery.io/v1/docs/graphql-ide/account) diff --git a/docs/graphql-ide/errors.md b/docs/graphql-ide/errors.md index ff5ba35..5849bba 100644 --- a/docs/graphql-ide/errors.md +++ b/docs/graphql-ide/errors.md @@ -1,3 +1,32 @@ +--- +sidebar_position: 8 +title: "Bitquery API Common Errors — Troubleshooting GraphQL & ClickHouse" +description: "Interpret Bitquery GraphQL API errors including ClickHouse 400, parse errors, memory limits, rate limits, timeouts, and 403/500 responses with resolution steps." +keywords: + [ + Bitquery errors, + GraphQL troubleshooting, + ClickHouse error, + API rate limit, + query memory limit, + ] +--- + + + + + + + + + + + + + + + + # Common Errors and What to Do This section will guide you through the interpretation of common error messages encountered within Bitquery APIs. It will help you decide when to escalate issues by filing a ticket at [Bitquery Support](https://support.bitquery.io/). @@ -112,8 +141,17 @@ When request fails with status code 403, please contact support on telegram. + ### Important Notes - **Resource Consideration**: Be cautious when setting high limits, as large queries might consume significant resources and impact performance. - **Pagination**: For large datasets, consider implementing pagination with `offset` to retrieve data in smaller chunks for better efficiency. Read more on limits and offsets [here](/docs/query-features/filtering/limits) - **Optimization**: Always aim to optimize your queries to retrieve the necessary data efficiently without exceeding resource limits. + +## Related Resources + +- [Getting started with queries](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [What are API points?](https://docs.bitquery.io/v1/docs/graphql-ide/points) +- [Account dashboard — errors and usage](https://docs.bitquery.io/v1/docs/graphql-ide/account) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/graphql-ide/how-to-start.md b/docs/graphql-ide/how-to-start.md index 2399e78..a74044e 100644 --- a/docs/graphql-ide/how-to-start.md +++ b/docs/graphql-ide/how-to-start.md @@ -1,7 +1,32 @@ --- sidebar_position: 1 +title: "Getting Started with Bitquery GraphQL IDE" +description: "Create a Bitquery account, open the GraphQL IDE, and run your first blockchain query with autocomplete, examples, and the query builder." +keywords: + [ + Bitquery IDE, + GraphQL tutorial, + first query, + blockchain GraphQL, + account signup, + ] --- + + + + + + + + + + + + + + + # Running your First Query Create and run your first query on Bitquery IDE by visiting [https://ide.bitquery.io/](https://ide.bitquery.io/). @@ -101,3 +126,11 @@ We have written blog posts to help you explain our APIs, please them on the [Bit If you still don't question our GraphQL APIs please ask them on this forum, and always provide complete details. Check our [Youtube Channel](https://www.youtube.com/@bitquery) for video tutorials. + +## Related Resources + +- [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) +- [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) +- [Use Bitquery in your application](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [V1 vs V2 APIs](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) diff --git a/docs/graphql-ide/ide.md b/docs/graphql-ide/ide.md index a4c52a5..ae48260 100644 --- a/docs/graphql-ide/ide.md +++ b/docs/graphql-ide/ide.md @@ -1,7 +1,33 @@ --- sidebar_position: 2 +title: "How to Use the Bitquery GraphQL IDE" +description: "Learn the Bitquery GraphQL IDE: visual query builder, writing queries, saving and sharing, access tokens, billing, and API usage from your dashboard." +keywords: + [ + Bitquery IDE, + GraphQL IDE, + query builder, + save queries, + OAuth token, + API dashboard, + ] --- + + + + + + + + + + + + + + + # How to use the IDE ? ## What is Bitquery IDE? @@ -56,3 +82,11 @@ You can find which queries have consumed substantial points within the "Queries" ## What if I don't want to use IDE? If the IDE isn't your preferred route, you can still directly access our API from your application using your Access Token. + +## Related Resources + +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [GraphQL query builder guide](https://docs.bitquery.io/v1/docs/graphql-ide/query-builder) +- [API access token setup](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) +- [Account dashboard overview](https://docs.bitquery.io/v1/docs/graphql-ide/account) +- [Use Bitquery APIs in your app](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) diff --git a/docs/graphql-ide/points.md b/docs/graphql-ide/points.md index 7dec4db..d147d85 100644 --- a/docs/graphql-ide/points.md +++ b/docs/graphql-ide/points.md @@ -1,7 +1,32 @@ --- sidebar_position: 4 +title: "Bitquery API Points — Pricing, Consumption & Query Cost" +description: "Understand Bitquery API points: how query cost is calculated from complexity and data volume, plans, free tier, and how to optimize usage and billing." +keywords: + [ + Bitquery points, + API pricing, + query cost, + billing, + GraphQL limits, + ] --- + + + + + + + + + + + + + + + # What are Points? At Bitquery we use points system to calculate the cost for a query. Each query will use different number of points, based on the complexity and size of the query requested. For a comprehensive understanding of the points system, please refer to [our detailed post](https://community.bitquery.io/t/introducing-points/874). @@ -23,3 +48,11 @@ The number of points can vary for various reasons. Even the same query can produ - The level of complexity of the query. For instance, if you include additional addresses, the points will be calculated considering the resources occupied by those addresses. To optimize this query, there are a few approaches you can consider. Firstly, narrowing down the date range can help to refine the results. Secondly, reducing the list of addresses may also be beneficial. However, the effectiveness of these strategies will depend on your specific goal. + +## Related Resources + +- [Account dashboard — API usage and billing](https://docs.bitquery.io/v1/docs/graphql-ide/account) +- [Common API errors](https://docs.bitquery.io/v1/docs/graphql-ide/errors) +- [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Use Bitquery in your application](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/graphql-ide/query-builder.md b/docs/graphql-ide/query-builder.md index 7fd4232..a9176e5 100644 --- a/docs/graphql-ide/query-builder.md +++ b/docs/graphql-ide/query-builder.md @@ -1,7 +1,32 @@ --- sidebar_position: 5 +title: "Bitquery GraphQL Query Builder — Visual Blockchain Queries" +description: "Build Bitquery GraphQL queries visually: pick blockchain and network, explore schema fields, set filters, select data fields, and run queries in the IDE." +keywords: + [ + Bitquery query builder, + visual GraphQL, + blockchain query builder, + schema explorer, + IDE, + ] --- + + + + + + + + + + + + + + + # Query Builder ## What is Query Builder? @@ -27,3 +52,11 @@ Creating precise queries using the Query Builder is a straightforward process. F 7. Execute Your Query: When you've your query and want to fetch the data, simply click the green button and fetch the data. Simplify your query creation process and access the data you need from various blockchain networks using the Query Builder. + +## Related Resources + +- [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) +- [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Supported blockchains](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) diff --git a/docs/graphql-ide/supported-blockchains.md b/docs/graphql-ide/supported-blockchains.md index 5baec8f..a0f6355 100644 --- a/docs/graphql-ide/supported-blockchains.md +++ b/docs/graphql-ide/supported-blockchains.md @@ -1,7 +1,32 @@ --- sidebar_position: 7 +title: "Supported Blockchains — Bitquery V1 API Networks & Status" +description: "Bitquery V1 supports 40+ blockchains including Ethereum, BSC, Solana, Cosmos, Bitcoin, and more. Check system status and data availability for each network." +keywords: + [ + supported blockchains, + Bitquery networks, + Ethereum API, + Bitcoin API, + multi-chain data, + ] --- + + + + + + + + + + + + + + + # Supported Blockchains and System Status Bitquery supports 40+ blockchains, including EVM-based blockchains like Ethereum, BSC, Polygon, along with other blockchains like Solana, Cosmos, and many more. Here is a list of the blockchains we support: @@ -19,3 +44,11 @@ Bitquery supports 40+ blockchains, including EVM-based blockchains like Ethereum ## System status To check the status of each blockchain service, you can visit the following link: [https://app-status.bitquery.io/](https://app-status.bitquery.io/) + +## Related Resources + +- [V1 vs V2 APIs — coverage and features](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) +- [Network selection in queries](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/graphql-ide/use-it-in-your-application.md b/docs/graphql-ide/use-it-in-your-application.md index bfdc7ac..2ed6cda 100644 --- a/docs/graphql-ide/use-it-in-your-application.md +++ b/docs/graphql-ide/use-it-in-your-application.md @@ -1,7 +1,32 @@ --- sidebar_position: 3 +title: "Integrate Bitquery GraphQL API in Your Application" +description: "Generate language-specific code snippets from the Bitquery IDE, copy your query, and call the GraphQL API with your access token from any stack." +keywords: + [ + Bitquery integration, + GraphQL client, + REST alternative, + code snippet, + API in app, + ] --- + + + + + + + + + + + + + + + # Use it in Your Application You can write any API and use it any application built on any language.To get the code, simply write your query and on the right side, you will see a `````` symbol. @@ -12,3 +37,11 @@ Click on the `````` symbol to view the code snippet tab. You can select the l ![language](/img/ide/code_dropdown.png) + +## Related Resources + +- [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) +- [How to use the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) +- [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Common API errors](https://docs.bitquery.io/v1/docs/graphql-ide/errors) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/graphql-ide/v1-and-v2.md b/docs/graphql-ide/v1-and-v2.md index 7a20af3..e9f3437 100644 --- a/docs/graphql-ide/v1-and-v2.md +++ b/docs/graphql-ide/v1-and-v2.md @@ -1,3 +1,32 @@ +--- +sidebar_position: 10 +title: "Bitquery GraphQL V1 vs V2 APIs — Endpoints & Features" +description: "Compare Bitquery V1 and V2 Streaming APIs: endpoints, real-time data, WebSockets, supported chains, NFTs, traces, and when to use each API." +keywords: + [ + Bitquery V1 vs V2, + Streaming API, + GraphQL endpoint, + WebSocket subscriptions, + blockchain API migration, + ] +--- + + + + + + + + + + + + + + + + # Difference between Bitquery GraphQL V1 and V2 APIs Today we will explain the difference between our V1 and V2 APIs. Let’s start with naming; we call our V2 APIs as Streaming APIs. Additionally, there is also a difference in the endpoint. @@ -74,4 +103,12 @@ We are very excited to see enable more features in our Streaming APIs. Here are * **More blockchains** — We are adding Optimism and going to add more blockchains with high throughput. * [**Data in the cloud** ](https://bitquery.io/products/streaming)— This is our new product, which uses streaming internally, using which we will allow complete historical and Real-time data through AWS, Snowflake, Google, and other Cloud vendors. -If you have questions about our APIs, please check out [Telegram](https://t.me/bloxy_info), and the [forum](https://community.bitquery.io/). \ No newline at end of file +If you have questions about our APIs, please check out [Telegram](https://t.me/bloxy_info), and the [forum](https://community.bitquery.io/). + +## Related Resources + +- [Bitquery V1 documentation overview](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Supported blockchains (V1)](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) +- [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/intro.md b/docs/intro.md index a3d0e25..a45cb35 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -1,7 +1,33 @@ --- sidebar_position: 1 +title: "Bitquery V1 API Documentation — Blockchain Data for 40+ Chains" +description: "Overview of the Bitquery V1 GraphQL API for historical and real-time blockchain data across 40+ networks, with guides for queries, schemas, and integration." +keywords: + [ + Bitquery, + GraphQL API, + blockchain data, + V1 API, + cryptocurrency data, + multi-chain API, + ] --- + + + + + + + + + + + + + + + # Overview Bitquery 's infrastructure provides you access to historical and real-time blockchain data through various interfaces such as GraphQL APIs. In this documentation @@ -26,3 +52,11 @@ We highly encourage you to dig into our docs first; however, you can contact us 1. [Telegram](https://t.me/bloxy_info) - For quick questions and doubts 2. [Community Forum](https://community.bitquery.io/) - For how to questions, features requests that can also help wider community 3. [Support Desk](https://support.bitquery.io/hc/en-us/requests/new) - For data problems, bugs + +## Related Resources + +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) diff --git a/docs/query-features/Metrics.md b/docs/query-features/Metrics.md index 622165f..edaa948 100644 --- a/docs/query-features/Metrics.md +++ b/docs/query-features/Metrics.md @@ -1,7 +1,25 @@ --- sidebar_position: 6 +title: "Metrics in Bitquery GraphQL API" +description: "Use the IDE metrics API and utilities metrics to inspect query cost, points, SQL requests, and chain-specific usage." +keywords: [Bitquery, metrics, API usage, query cost, GraphQL] --- + + + + + + + + + + + + + + + # Metrics The IDE Builder provides a metrics API that you can use to get details on your usage. @@ -50,4 +68,12 @@ And one of the response fields in the `list` was The Extra Memory Consumption, GB metric measures the amount of extra memory that was used by the query. -Some chains have specific metrics that you can get using the metrics API. For example, the Tron chain has a `netUsage` metric that you can use to get the network usage for a query. \ No newline at end of file +Some chains have specific metrics that you can get using the metrics API. For example, the Tron chain has a `netUsage` metric that you can use to get the network usage for a query. + +## Related Resources + +- [Utilities API](https://docs.bitquery.io/v1/docs/query-features/utilities/utilities) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) \ No newline at end of file diff --git a/docs/query-features/aggregation/aggregation.md b/docs/query-features/aggregation/aggregation.md index 2329d45..db6c9d5 100644 --- a/docs/query-features/aggregation/aggregation.md +++ b/docs/query-features/aggregation/aggregation.md @@ -1,7 +1,24 @@ --- sidebar_position: 1 +title: "Aggregation in Bitquery GraphQL API" +description: "Group and aggregate blockchain data with sum, count, average, maximum, minimum, and median on Bitquery V1 GraphQL." +keywords: [Bitquery, GraphQL, aggregation, calculate, sum, count] --- + + + + + + + + + + + + + + # Aggregation in V1 @@ -64,4 +81,12 @@ parameters: > Notes: -The calculate argument can be used to specify the aggregation function that should be used. \ No newline at end of file +The calculate argument can be used to specify the aggregation function that should be used. + +## Related Resources + +- [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) +- [Sum aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/sum) +- [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) \ No newline at end of file diff --git a/docs/query-features/aggregation/count.md b/docs/query-features/aggregation/count.md index e02848c..8b233d2 100644 --- a/docs/query-features/aggregation/count.md +++ b/docs/query-features/aggregation/count.md @@ -1,7 +1,25 @@ --- sidebar_position: 3 +title: "Count Aggregation in Bitquery GraphQL API" +description: "Use count and countBigInt in Bitquery queries for transactions, events, and grouped results with sorting and filters." +keywords: [Bitquery, GraphQL, count, countBigInt, aggregation] --- + + + + + + + + + + + + + + + # Count @@ -117,3 +135,11 @@ query ($network: EverscaleNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTi "dateFormat": "%Y-%m-%d" } ``` + +## Related Resources + +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) +- [Sum aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/sum) +- [GraphQL aliases](https://docs.bitquery.io/v1/docs/query-features/aliases) +- [Sorting](https://docs.bitquery.io/v1/docs/query-features/filtering/sorting) +- [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) diff --git a/docs/query-features/aggregation/sum.md b/docs/query-features/aggregation/sum.md index be8b1cb..44be075 100644 --- a/docs/query-features/aggregation/sum.md +++ b/docs/query-features/aggregation/sum.md @@ -1,7 +1,25 @@ --- sidebar_position: 4 +title: "Sum Aggregation in Bitquery GraphQL API" +description: "Calculate total amounts with sum and conditional criteria for transfers, volume, and USD in Bitquery GraphQL." +keywords: [Bitquery, GraphQL, sum, aggregation, transfers, USD] --- + + + + + + + + + + + + + + + # Sum @@ -52,4 +70,12 @@ query ($network: EthereumNetwork!, $address: String!, $from: ISO8601DateTime, $t By mention the address as a sender or receiver we are calculating: - The total amount of ETH that was transferred into and out of the address, as `sum_in` and `sum_out` fields -- The total amount of ETH that was transferred into and out of the address as the `sum_in_usd` and `sum_out_usd` fields \ No newline at end of file +- The total amount of ETH that was transferred into and out of the address as the `sum_in_usd` and `sum_out_usd` fields + +## Related Resources + +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) +- [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) +- [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) \ No newline at end of file diff --git a/docs/query-features/aliases.md b/docs/query-features/aliases.md index cfebf77..5515a2b 100644 --- a/docs/query-features/aliases.md +++ b/docs/query-features/aliases.md @@ -1,7 +1,25 @@ --- sidebar_position: 2 +title: "GraphQL Aliases in Bitquery API" +description: "Rename GraphQL response fields with aliases in Bitquery queries for clearer DEX trade and token data." +keywords: [Bitquery, GraphQL, aliases, field renaming, DEX] --- + + + + + + + + + + + + + + + # Aliases @@ -54,4 +72,12 @@ Here's an example of a query with aliasing: } } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Fragments overview](https://docs.bitquery.io/v1/docs/query-features/fragments/overview) +- [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Schema — Ethereum overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) \ No newline at end of file diff --git a/docs/query-features/arguments/EVM_arguments.md b/docs/query-features/arguments/EVM_arguments.md index 3595e4c..363b980 100644 --- a/docs/query-features/arguments/EVM_arguments.md +++ b/docs/query-features/arguments/EVM_arguments.md @@ -1,6 +1,25 @@ --- sidebar_position: 2 +title: "EVM Arguments in Bitquery GraphQL API" +description: "Query transaction and event arguments on Ethereum and EVM chains with smartContractEvent and argument filters." +keywords: [Bitquery, GraphQL, EVM, arguments, smart contract events] --- + + + + + + + + + + + + + + + + # EVM Arguments You can use the `arguments` method with EVM chains to get arguments and values of transactions, trades and calls. @@ -65,4 +84,12 @@ Here the arguments are completely different. In this example, the borrow method has six arguments: `offer.totalAmount`, `offer.minAmount`, `offer.maxAmount`, `loanAmount`, `offer.auctionDuration`, and `offer`.`expirationTime`. The argument field is used to specify the name of the argument that you want to retrieve. -In this case, the `totalAmount`, `minAmount`, `maxAmount`, `loanAmount`, `auctionDuration`, and `expirationTime` arguments are retrieved \ No newline at end of file +In this case, the `totalAmount`, `minAmount`, `maxAmount`, `loanAmount`, `auctionDuration`, and `expirationTime` arguments are retrieved + +## Related Resources + +- [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) +- [Arguments on other chains](https://docs.bitquery.io/v1/docs/query-features/arguments/Other_Chains_arguments) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Filtering options](https://docs.bitquery.io/v1/docs/query-features/filtering/options) \ No newline at end of file diff --git a/docs/query-features/arguments/Other_Chains_arguments.md b/docs/query-features/arguments/Other_Chains_arguments.md index e292b91..baf3e95 100644 --- a/docs/query-features/arguments/Other_Chains_arguments.md +++ b/docs/query-features/arguments/Other_Chains_arguments.md @@ -1,7 +1,25 @@ --- sidebar_position: 3 +title: "Arguments on Algorand, Hedera & Other Chains — Bitquery API" +description: "Examples of the arguments API on non-EVM chains including Algorand and Hedera with Bitquery GraphQL." +keywords: [Bitquery, GraphQL, arguments, Algorand, Hedera] --- + + + + + + + + + + + + + + + # Using Arguments on Other Chains Using arguments in other chains varies from one to another. @@ -72,4 +90,12 @@ query MyQuery { } } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) +- [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/query-features/arguments/argument.md b/docs/query-features/arguments/argument.md index ee18f0b..af0c73a 100644 --- a/docs/query-features/arguments/argument.md +++ b/docs/query-features/arguments/argument.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Arguments API in Bitquery GraphQL" +description: "Overview of the arguments query for smart contract method and event parameters across EVM and other supported chains." +keywords: [Bitquery, GraphQL, arguments, smart contract, EVM] --- + + + + + + + + + + + + + + + # Arguments The arguments query method returns the arguments of a transaction or smart contract call. Currently arguments are supported on EVM, Algorand, Everscale, Conflux, Harmony, Hedera and Flow. @@ -13,6 +31,13 @@ For detailed examples check - [EVM](/docs/query-features/arguments/EVM_arguments.md) - [Other Chains](/docs/query-features/arguments/Other_Chains_arguments.md) - + +## Related Resources + +- [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) +- [Arguments on other chains](https://docs.bitquery.io/v1/docs/query-features/arguments/Other_Chains_arguments) +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) diff --git a/docs/query-features/expressions/overview.md b/docs/query-features/expressions/overview.md index e732dbd..aa6e046 100644 --- a/docs/query-features/expressions/overview.md +++ b/docs/query-features/expressions/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Expressions in Bitquery GraphQL API" +description: "Define custom calculated fields with expression() in Bitquery V1 GraphQL, including limitBy and derived metrics." +keywords: [Bitquery, GraphQL, expressions, expression(), calculated fields] --- + + + + + + + + + + + + + + + # Expressions **What is an Expression?** @@ -97,3 +115,11 @@ The `limitby` field can be used to limit the results of a query to a specific nu } } ``` + +## Related Resources + +- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) +- [Limits and limitBy](https://docs.bitquery.io/v1/docs/query-features/filtering/limits) +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) +- [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/query-features/filtering/fields.md b/docs/query-features/filtering/fields.md index c8fed2d..c28d83a 100644 --- a/docs/query-features/filtering/fields.md +++ b/docs/query-features/filtering/fields.md @@ -1,7 +1,25 @@ --- sidebar_position: 2 +title: "Filter Fields in Bitquery GraphQL API" +description: "Use method filters, date, time, uniq counts, and field combinations to narrow Bitquery blockchain and DEX queries." +keywords: [Bitquery, GraphQL, filters, fields, uniq, transactions] --- + + + + + + + + + + + + + + + # Fields Each method for every API will have different set of fields as filters. For example, the blocks method will have the following fields as filters: @@ -43,3 +61,11 @@ query MyQuery { ``` + +## Related Resources + +- [Options filter](https://docs.bitquery.io/v1/docs/query-features/filtering/options) +- [Limits and limitBy](https://docs.bitquery.io/v1/docs/query-features/filtering/limits) +- [Sorting](https://docs.bitquery.io/v1/docs/query-features/filtering/sorting) +- [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) diff --git a/docs/query-features/filtering/limits.md b/docs/query-features/filtering/limits.md index f9c4ebc..00d1097 100644 --- a/docs/query-features/filtering/limits.md +++ b/docs/query-features/filtering/limits.md @@ -1,7 +1,25 @@ --- sidebar_position: 4 +title: "Limits and LimitBy in Bitquery GraphQL API" +description: "Control result size with limit and limitBy options in Bitquery GraphQL for DEX trades and aggregated queries." +keywords: [Bitquery, GraphQL, limit, limitBy, pagination] --- + + + + + + + + + + + + + + + # Limits You can limit of the number of results retrieved using the `limit` or `limitby` filter both of which work differently. @@ -83,3 +101,11 @@ limitBy: {each: "baseCurrency.address", limit: 1} - `each`: The field to limit by, in this case `baseCurrency.address`. - `limit`: The maximum number of results to return for each value of the `each` field, in this case 1. + +## Related Resources + +- [Options filter](https://docs.bitquery.io/v1/docs/query-features/filtering/options) +- [Sorting](https://docs.bitquery.io/v1/docs/query-features/filtering/sorting) +- [Expressions overview](https://docs.bitquery.io/v1/docs/query-features/expressions/overview) +- [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/query-features/filtering/options.md b/docs/query-features/filtering/options.md index db61ee2..6e853fa 100644 --- a/docs/query-features/filtering/options.md +++ b/docs/query-features/filtering/options.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "Options Filter in Bitquery GraphQL API" +description: "Combine limit, offset, ascending and descending sort in the options argument for Bitquery GraphQL queries." +keywords: [Bitquery, GraphQL, options, limit, offset, sorting] --- + + + + + + + + + + + + + + + # Options The options filter contains most of the sorting and result limiting features as shown in the screenshot. @@ -32,4 +50,12 @@ query ($network: EthereumNetwork!, $dateFormat: String!, $from: ISO8601DateTime, > Notes: - The options filter is case-sensitive. -- The limit and offset option must be a positive integer. \ No newline at end of file +- The limit and offset option must be a positive integer. + +## Related Resources + +- [Sorting](https://docs.bitquery.io/v1/docs/query-features/filtering/sorting) +- [Limits and limitBy](https://docs.bitquery.io/v1/docs/query-features/filtering/limits) +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/query-features/filtering/sorting.md b/docs/query-features/filtering/sorting.md index d665c1e..7a11ab1 100644 --- a/docs/query-features/filtering/sorting.md +++ b/docs/query-features/filtering/sorting.md @@ -1,7 +1,25 @@ --- sidebar_position: 3 +title: "Sorting in Bitquery GraphQL API" +description: "Sort API results with asc, desc, and descByInteger options in Bitquery GraphQL for blocks, trades, and events." +keywords: [Bitquery, GraphQL, sorting, asc, desc, options] --- + + + + + + + + + + + + + + + # Sorting You can sort the results in ascending or descending order using two filters. @@ -23,4 +41,11 @@ There's another flavour of this sorting option called `descbyInteger` which is n Here's an example of how you can use it ```options: {descByInteger: "tradeIndex"}``` +## Related Resources + +- [Options filter](https://docs.bitquery.io/v1/docs/query-features/filtering/options) +- [Limits and limitBy](https://docs.bitquery.io/v1/docs/query-features/filtering/limits) +- [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) +- [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) +- [Schema — Ethereum overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/query-features/fragments/overview.md b/docs/query-features/fragments/overview.md index 2ed57bd..746e7de 100644 --- a/docs/query-features/fragments/overview.md +++ b/docs/query-features/fragments/overview.md @@ -1,7 +1,25 @@ --- sidebar_position: 1 +title: "GraphQL Fragments in Bitquery API" +description: "Reuse query fragments for balance history and other patterns to reduce duplication in Bitquery GraphQL." +keywords: [Bitquery, GraphQL, fragments, reuse, queries] --- + + + + + + + + + + + + + + + # Fragments A fragment spread is a way to reuse a fragment definition in another fragment or query. This can be useful for reducing code duplication and making your queries more readable. @@ -48,4 +66,11 @@ fragment balanceChange on EthereumBalanceChange { } ``` +## Related Resources + +- [GraphQL aliases](https://docs.bitquery.io/v1/docs/query-features/aliases) +- [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Utilities API](https://docs.bitquery.io/v1/docs/query-features/utilities/utilities) diff --git a/docs/query-features/search/search.md b/docs/query-features/search/search.md index bf4cccb..f838cda 100644 --- a/docs/query-features/search/search.md +++ b/docs/query-features/search/search.md @@ -1,3 +1,25 @@ +--- +sidebar_position: 1 +title: "Search API in Bitquery GraphQL" +description: "Search addresses, tokens, and hashes across chains with the Bitquery search method and typed subject results." +keywords: [Bitquery, GraphQL, search, address, multi-chain] +--- + + + + + + + + + + + + + + + + # Search The Search method allows you to identify the type of object that was found and the network that it belongs to by typing a string. You can for example type an address and to check which network the address belongs. Each result also has a `subject` field, which has a `__typename` subfield which tells you the type of the object found ( e.g. `Address`). @@ -79,4 +101,12 @@ query MyQuery { } -``` \ No newline at end of file +``` + +## Related Resources + +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) +- [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) \ No newline at end of file diff --git a/docs/query-features/utilities/utilities.md b/docs/query-features/utilities/utilities.md index 657391d..b5a5d4c 100644 --- a/docs/query-features/utilities/utilities.md +++ b/docs/query-features/utilities/utilities.md @@ -1,3 +1,25 @@ +--- +sidebar_position: 1 +title: "Utilities API in Bitquery GraphQL" +description: "Check account billing, points, and API usage metrics with the Bitquery utilities root query." +keywords: [Bitquery, GraphQL, utilities, API usage, billing, metrics] +--- + + + + + + + + + + + + + + + + # Utilities Utilities method helps understand your API consumption. It provides information on your account, such as your active period, billing day, and points remaining. It also provides metrics on your API usage, such as the number of SQL requests you have made and the cost of those requests. @@ -47,3 +69,11 @@ The metrics subfield provides metrics on your API usage. To get metrics on your } ``` + +## Related Resources + +- [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) +- [GraphQL IDE — how to start](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) From 277d27a53ad82ae04e0e4413fd3d253b70db3214 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 22:02:10 +0530 Subject: [PATCH 03/14] Fix SEO quality issues: duplicate meta, broken URLs, inaccurate descriptions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Removed duplicate blocks from 273 newly-added pages (keep front matter as single source of truth; Docusaurus generates title/description/OG/Twitter) - Fixed broken Bitcoin example hub URLs (Examples/bitcoin → examples/Bitcoin) - Fixed space-in-URL on addressstats.md - Fixed inaccurate descriptions: Bitcoin overview (removed "smart contracts"), ethereum2 (Beacon Chain specifics), Bitcoin transactions (UTXO-specific) - Fixed copy-paste errors: Bitcoin-Blocks-API "Cosmos" → "Bitcoin", tron transfers "rpovides", ethereum transactions "exmaple", intro "Bitquery 's", basic-structure "Architechture" - Cleaned keyword spam on bitcoin/ethereum coinpath meta tags - Added SEO to missed pages: multi-chain-portfolio-tracker, tezos/harmony overviews Made-with: Cursor --- docs/API-Blog/dogecoin-wallet-auditing.md | 17 +---- .../Beacon Chain Examples/eth2_examples.md | 15 ----- docs/Examples/Dogecoin/get-latest-price.md | 15 ----- docs/Examples/Dogecoin/inflow-outflow.md | 15 ----- docs/Examples/Input_Output/IO_examples.md | 15 ----- docs/Examples/Solana/address-api.md | 15 ----- docs/Examples/Solana/instructions.md | 15 ----- docs/Examples/Solana/transactions-api.md | 15 ----- docs/Examples/Solana/transfers.md | 17 +---- docs/Examples/Staking/stake_examples.md | 15 ----- docs/Examples/Transactions/Trace_API.md | 15 ----- .../Examples/Transactions/input-output-api.md | 15 ----- docs/Examples/Transactions/transaction-api.md | 15 ----- docs/Examples/Transfers/transfer-api.md | 15 ----- docs/Examples/Zcash/address-api.md | 4 +- docs/Examples/Zcash/zenzec-api.md | 4 +- .../blockchain-active-addresses-api.md | 15 ----- .../Blockchain-Address-API-Examples.md | 15 ----- docs/Examples/address/specific-queries.md | 15 ----- .../addressStats/address-stats-api.md | 15 ----- docs/Examples/algorand/address.md | 15 ----- docs/Examples/algorand/arguments.md | 15 ----- docs/Examples/algorand/blocks.md | 15 ----- docs/Examples/algorand/coinpath.md | 15 ----- docs/Examples/bitcoin/Bitcoin-Blocks-API.md | 19 +----- docs/Examples/bitcoin/Bitcoin-Coinpath-API.md | 15 ----- ...-OmniTransactions-and-OmniTransfers API.md | 17 +---- .../bitcoin/Bitcoin-Transaction-API.md | 17 +---- docs/Examples/bitcoin/bitcoin-address-api.md | 17 +---- docs/Examples/bitcoin/bitcoin-fee-api.md | 17 +---- docs/Examples/bitcoin/index.md | 15 ----- docs/Examples/coinpath/money-flow-api.md | 2 +- docs/Examples/cosmos/address.md | 15 ----- docs/Examples/cosmos/attributes.md | 15 ----- docs/Examples/cosmos/blocks.md | 15 ----- docs/Examples/cosmos/coinpath.md | 15 ----- docs/Examples/cosmos/messages.md | 15 ----- docs/Examples/cosmos/transactions.md | 15 ----- docs/Examples/cosmos/transfers.md | 15 ----- docs/Examples/cross-chain/cross-chain-api.md | 15 ----- docs/Examples/dexTrades/dex-pool-api.md | 15 ----- .../dexTrades/dex-trading-data-api.md | 15 ----- docs/Examples/dexTrades/ohlc.md | 15 ----- docs/Examples/filecoin/messages.md | 15 ----- docs/Examples/hedera/hedera-address.md | 15 ----- docs/Examples/hedera/hedera-io.md | 15 ----- docs/Examples/hedera/hedera-messages.md | 15 ----- docs/Examples/hedera/hedera-transactions.md | 15 ----- docs/Examples/overview.md | 17 +---- docs/Examples/ripple/nft_token_offers.md | 15 ----- .../smart-contract-calls-api.md | 15 ----- .../smartcontractEvents/Non_EVM_events.md | 15 ----- .../smart-contract-events-api.md | 15 ----- docs/Examples/stellar/stellar-address-api.md | 15 ----- docs/Examples/stellar/stellar-effects-api.md | 15 ----- .../stellar/stellar-liquiditypool-api.md | 15 ----- docs/Examples/stellar/stellar-payments-api.md | 15 ----- .../stellar/stellar-tradeeffects-api.md | 15 ----- .../stellar/stellar-transactions-api.md | 15 ----- docs/Examples/tokens/token-api.md | 15 ----- docs/Examples/tron/address.md | 15 ----- docs/Examples/tron/arguments.md | 15 ----- docs/Examples/tron/blocks.md | 15 ----- docs/Examples/tron/coinpath.md | 15 ----- docs/Examples/tron/contracts.md | 15 ----- docs/Examples/tron/dexTrades.md | 15 ----- docs/Examples/tron/smartContractCalls.md | 15 ----- docs/Examples/tron/smartContractEvents.md | 15 ----- docs/Examples/tron/transaction.md | 15 ----- docs/Examples/tron/transfers.md | 17 +---- docs/Schema/Avalanche/overview.md | 15 ----- docs/Schema/Cronos/activeaddresses.md | 15 ----- docs/Schema/Cronos/address.md | 15 ----- docs/Schema/Cronos/addresstats.md | 15 ----- docs/Schema/Cronos/arguments.md | 15 ----- docs/Schema/Cronos/blocks.md | 15 ----- docs/Schema/Cronos/coinpath.md | 15 ----- docs/Schema/Cronos/dextrades.md | 15 ----- docs/Schema/Cronos/overview.md | 15 ----- docs/Schema/Cronos/references.md | 15 ----- docs/Schema/Cronos/smartcontractcalls.md | 15 ----- docs/Schema/Cronos/smartcontractevents.md | 15 ----- docs/Schema/Cronos/transactions.md | 15 ----- docs/Schema/Cronos/transfers.md | 15 ----- docs/Schema/Dash/overview.md | 15 ----- docs/Schema/Dogecoin/overview.md | 15 ----- docs/Schema/Polygon/overview.md | 16 ----- docs/Schema/algorand/address.md | 15 ----- docs/Schema/algorand/arguments.md | 15 ----- docs/Schema/algorand/blocks.md | 15 ----- docs/Schema/algorand/coinpath.md | 15 ----- docs/Schema/algorand/overview.md | 15 ----- docs/Schema/algorand/smartContractCalls.md | 15 ----- docs/Schema/algorand/transactions.md | 15 ----- docs/Schema/algorand/transfers.md | 15 ----- docs/Schema/binance_smart_chain/overview.md | 15 ----- docs/Schema/bitcoin/addressstats.md | 4 +- docs/Schema/bitcoin/blocks.md | 2 +- docs/Schema/bitcoin/coinpath.md | 4 +- docs/Schema/bitcoin/inputs.md | 2 +- docs/Schema/bitcoin/omnitransactions.md | 2 +- docs/Schema/bitcoin/omnitransfers.md | 2 +- docs/Schema/bitcoin/outputs.md | 2 +- docs/Schema/bitcoin/overview.md | 19 +----- docs/Schema/bitcoin/transactions.md | 10 +-- docs/Schema/cardano/address.md | 15 ----- docs/Schema/cardano/addressstats.md | 15 ----- docs/Schema/cardano/blocks.md | 15 ----- docs/Schema/cardano/coinpath.md | 15 ----- docs/Schema/cardano/inputsOutputs.md | 15 ----- docs/Schema/cardano/mints.md | 15 ----- docs/Schema/cardano/overview.md | 15 ----- docs/Schema/cardano/transactions.md | 15 ----- docs/Schema/celo/activeaddresses.md | 15 ----- docs/Schema/celo/address.md | 15 ----- docs/Schema/celo/addresstats.md | 15 ----- docs/Schema/celo/arguments.md | 15 ----- docs/Schema/celo/blocks.md | 15 ----- docs/Schema/celo/coinpath.md | 15 ----- docs/Schema/celo/dextrades.md | 15 ----- docs/Schema/celo/overview.md | 15 ----- docs/Schema/celo/references.md | 15 ----- docs/Schema/celo/smartcontractcalls.md | 15 ----- docs/Schema/celo/smartcontractevents.md | 15 ----- docs/Schema/celo/transactions.md | 15 ----- docs/Schema/celo/transfers.md | 15 ----- docs/Schema/conflux/activeaddress.md | 15 ----- docs/Schema/conflux/address.md | 15 ----- docs/Schema/conflux/arguments.md | 15 ----- docs/Schema/conflux/blocks.md | 15 ----- docs/Schema/conflux/coinpath.md | 15 ----- docs/Schema/conflux/overview.md | 15 ----- docs/Schema/conflux/smartcontractcalls.md | 15 ----- docs/Schema/conflux/smartcontractevents.md | 15 ----- docs/Schema/conflux/transactions.md | 15 ----- docs/Schema/conflux/transfers.md | 15 ----- docs/Schema/cosmos/address.md | 15 ----- docs/Schema/cosmos/attributes.md | 15 ----- docs/Schema/cosmos/blocks.md | 15 ----- docs/Schema/cosmos/coinpath.md | 15 ----- docs/Schema/cosmos/messages.md | 15 ----- docs/Schema/cosmos/overview.md | 15 ----- docs/Schema/cosmos/transactions.md | 15 ----- docs/Schema/cosmos/transfer.md | 15 ----- docs/Schema/elrond/address.md | 15 ----- docs/Schema/elrond/blocks.md | 15 ----- docs/Schema/elrond/blockvalidators.md | 15 ----- docs/Schema/elrond/callresults.md | 15 ----- docs/Schema/elrond/miniblocks.md | 15 ----- docs/Schema/elrond/notarizedblocks.md | 15 ----- docs/Schema/elrond/operations.md | 15 ----- docs/Schema/elrond/overview.md | 15 ----- docs/Schema/elrond/transactions.md | 15 ----- docs/Schema/elrond/transfers.md | 15 ----- docs/Schema/eos/addressstats.md | 15 ----- docs/Schema/eos/blocks.md | 15 ----- docs/Schema/eos/coinpath.md | 15 ----- docs/Schema/eos/overview.md | 15 ----- docs/Schema/eos/proposers.md | 15 ----- docs/Schema/eos/smartcontractcalls.md | 15 ----- docs/Schema/eos/transactions.md | 15 ----- docs/Schema/eos/transfers.md | 15 ----- docs/Schema/ethereum/coinpath.md | 2 +- docs/Schema/ethereum/overview.md | 15 ----- docs/Schema/ethereum/transactions.md | 2 +- docs/Schema/ethereum2/overview.md | 17 +---- docs/Schema/filecoin/address.md | 15 ----- docs/Schema/filecoin/arguments.md | 15 ----- docs/Schema/filecoin/blocks.md | 15 ----- docs/Schema/filecoin/calls.md | 15 ----- docs/Schema/filecoin/messages.md | 15 ----- docs/Schema/filecoin/overview.md | 16 ----- docs/Schema/filecoin/transfers.md | 15 ----- docs/Schema/flow/address.md | 15 ----- docs/Schema/flow/arguments.md | 15 ----- docs/Schema/flow/blockSeals.md | 15 ----- docs/Schema/flow/blocks.md | 15 ----- docs/Schema/flow/coinpath.md | 15 ----- docs/Schema/flow/collections.md | 15 ----- docs/Schema/flow/eventFields.md | 15 ----- docs/Schema/flow/events.md | 15 ----- docs/Schema/flow/inputs.md | 15 ----- docs/Schema/flow/outputs.md | 15 ----- docs/Schema/flow/overview.md | 65 +++++++------------ docs/Schema/flow/transactionAuthorizers.md | 15 ----- .../flow/transactionEnvelopeSignatures.md | 15 ----- .../flow/transactionPayloadSignatures.md | 15 ----- docs/Schema/flow/transactions.md | 15 ----- docs/Schema/harmony/arguments.md | 15 ----- docs/Schema/harmony/blocks.md | 15 ----- docs/Schema/harmony/overview.md | 9 +++ docs/Schema/harmony/smartContractCalls.md | 15 ----- docs/Schema/harmony/smartContractEvents.md | 15 ----- docs/Schema/harmony/stakingTransactions.md | 15 ----- docs/Schema/harmony/transactions.md | 15 ----- docs/Schema/harmony/transfers.md | 15 ----- docs/Schema/hedera/address.md | 15 ----- docs/Schema/hedera/arguments.md | 15 ----- docs/Schema/hedera/calls.md | 15 ----- docs/Schema/hedera/coinpath.md | 15 ----- docs/Schema/hedera/inputs.md | 15 ----- docs/Schema/hedera/messages.md | 15 ----- docs/Schema/hedera/outputs.md | 15 ----- docs/Schema/hedera/overview.md | 15 ----- docs/Schema/hedera/transactions.md | 15 ----- docs/Schema/ripple/overview.md | 15 ----- docs/Schema/solana/address.md | 15 ----- docs/Schema/solana/blockRewards.md | 15 ----- docs/Schema/solana/blocks.md | 15 ----- docs/Schema/solana/coinpath.md | 15 ----- docs/Schema/solana/instructionAccounts.md | 15 ----- docs/Schema/solana/instructions.md | 15 ----- docs/Schema/solana/overview.md | 15 ----- docs/Schema/solana/transactions.md | 15 ----- docs/Schema/solana/transfers.md | 15 ----- docs/Schema/stellar/address.md | 15 ----- docs/Schema/stellar/addressStats.md | 15 ----- docs/Schema/stellar/balanceEffects.md | 15 ----- docs/Schema/stellar/blocks.md | 15 ----- .../Schema/stellar/claimableBalanceEffects.md | 15 ----- docs/Schema/stellar/coinpath.md | 15 ----- docs/Schema/stellar/effectArguments.md | 15 ----- docs/Schema/stellar/effects.md | 15 ----- docs/Schema/stellar/liquidityPoolEffects.md | 15 ----- .../stellar/liquidityPoolTradeEffects.md | 15 ----- docs/Schema/stellar/operations.md | 15 ----- docs/Schema/stellar/overview.md | 15 ----- docs/Schema/stellar/payments.md | 15 ----- docs/Schema/stellar/tradeEffects.md | 15 ----- docs/Schema/stellar/transactions.md | 15 ----- docs/Schema/stellar/transfers.md | 15 ----- docs/Schema/tezos/address.md | 15 ----- docs/Schema/tezos/arguments.md | 15 ----- docs/Schema/tezos/balanceUpdates.md | 15 ----- docs/Schema/tezos/blocks.md | 15 ----- docs/Schema/tezos/coinpath.md | 15 ----- docs/Schema/tezos/operations.md | 15 ----- docs/Schema/tezos/overview.md | 9 +++ docs/Schema/tezos/transactions.md | 15 ----- docs/Schema/tezos/transfers.md | 15 ----- docs/Schema/tron/overview.md | 15 ----- docs/Schema/velas/activeaddresses.md | 15 ----- docs/Schema/velas/address.md | 15 ----- docs/Schema/velas/addresstats.md | 15 ----- docs/Schema/velas/arguments.md | 15 ----- docs/Schema/velas/blocks.md | 15 ----- docs/Schema/velas/coinpath.md | 15 ----- docs/Schema/velas/dextrades.md | 15 ----- docs/Schema/velas/overview.md | 15 ----- docs/Schema/velas/references.md | 15 ----- docs/Schema/velas/smartcontractcalls.md | 15 ----- docs/Schema/velas/smartcontractevents.md | 15 ----- docs/Schema/velas/transactions.md | 15 ----- docs/Schema/velas/transfers.md | 15 ----- docs/Use-Cases/crypto-ml-price-prediction.md | 17 +---- .../multi-chain-portfolio-tracker.md | 22 ++++++- docs/Use-Cases/react-example.md | 15 ----- docs/Use-Cases/tradingview.md | 15 ----- docs/Use-Cases/wordpress-wpgetapi.md | 17 +---- docs/building-queries/FAQ.md | 17 +---- .../basic-structure-of-a-query.md | 17 +---- docs/building-queries/network-selection.md | 15 ----- docs/graphql-ide/account.md | 15 ----- docs/graphql-ide/apikey.md | 15 ----- docs/graphql-ide/errors.md | 15 ----- docs/graphql-ide/how-to-start.md | 15 ----- docs/graphql-ide/ide.md | 15 ----- docs/graphql-ide/points.md | 15 ----- docs/graphql-ide/query-builder.md | 17 +---- docs/graphql-ide/supported-blockchains.md | 17 +---- .../graphql-ide/use-it-in-your-application.md | 15 ----- docs/graphql-ide/v1-and-v2.md | 15 ----- docs/intro.md | 19 +----- docs/query-features/Metrics.md | 15 ----- .../query-features/aggregation/aggregation.md | 15 ----- docs/query-features/aggregation/count.md | 15 ----- docs/query-features/aggregation/sum.md | 17 +---- docs/query-features/aliases.md | 15 ----- .../query-features/arguments/EVM_arguments.md | 15 ----- .../arguments/Other_Chains_arguments.md | 17 +---- docs/query-features/arguments/argument.md | 15 ----- docs/query-features/expressions/overview.md | 15 ----- docs/query-features/filtering/fields.md | 15 ----- docs/query-features/filtering/limits.md | 15 ----- docs/query-features/filtering/options.md | 15 ----- docs/query-features/filtering/sorting.md | 15 ----- docs/query-features/fragments/overview.md | 15 ----- docs/query-features/search/search.md | 15 ----- docs/query-features/utilities/utilities.md | 15 ----- 289 files changed, 108 insertions(+), 4167 deletions(-) diff --git a/docs/API-Blog/dogecoin-wallet-auditing.md b/docs/API-Blog/dogecoin-wallet-auditing.md index e7d1f9c..67a063a 100644 --- a/docs/API-Blog/dogecoin-wallet-auditing.md +++ b/docs/API-Blog/dogecoin-wallet-auditing.md @@ -4,21 +4,6 @@ description: "Audit Dogecoin wallets for reporting, compliance, and forensics us keywords: [Dogecoin, wallet audit, Bitquery API, blockchain, forensics, transactions] --- - - - - - - - - - - - - - - - # How to Audit a Dogecoin Wallet Dogecoin, originally created as a meme cryptocurrency, has grown to be a significant digital asset with a vibrant community. With the increasing adoption of Dogecoin in transactions and investments, there is a rising need to audit Dogecoin wallets for various purposes, including financial reporting, compliance, and forensic investigations. In this blog, we will explore who needs Dogecoin wallet data, the types of data required, and how to audit Dogecoin wallets using Bitquery APIs. @@ -88,6 +73,6 @@ Understanding the complexities of Dogecoin transactions and balances is key to a - [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) - [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Blockchain API examples — overview](https://docs.bitquery.io/v1/docs/Examples/overview) - [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Examples/Beacon Chain Examples/eth2_examples.md b/docs/Examples/Beacon Chain Examples/eth2_examples.md index 49230d8..6114907 100644 --- a/docs/Examples/Beacon Chain Examples/eth2_examples.md +++ b/docs/Examples/Beacon Chain Examples/eth2_examples.md @@ -5,21 +5,6 @@ keywords: [Ethereum 2 API examples, Beacon Chain GraphQL queries, Bitquery] sidebar_position: 1 --- - - - - - - - - - - - - - - - # ETH2 Examples Our ETH2 APIs provides extensive data on Beacon Chain. Let's look at some of the examples. diff --git a/docs/Examples/Dogecoin/get-latest-price.md b/docs/Examples/Dogecoin/get-latest-price.md index e8550d6..7822ef6 100644 --- a/docs/Examples/Dogecoin/get-latest-price.md +++ b/docs/Examples/Dogecoin/get-latest-price.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Dogecoin USD price from on-chain data. keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Get Latest Price of Doge Coin in USD Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/dogecoin-price-in-use_1) query, we can get the latest price of Doge Coin in `USD`. diff --git a/docs/Examples/Dogecoin/inflow-outflow.md b/docs/Examples/Dogecoin/inflow-outflow.md index fd072d9..5437135 100644 --- a/docs/Examples/Dogecoin/inflow-outflow.md +++ b/docs/Examples/Dogecoin/inflow-outflow.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Dogecoin transfers and address flows. keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Tranfers of an Address on DogeCoin Network Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/zFB1y4MP5B) query, we can get the transfers of Doge Coin to a particular address. diff --git a/docs/Examples/Input_Output/IO_examples.md b/docs/Examples/Input_Output/IO_examples.md index bcb0f66..84f58ff 100644 --- a/docs/Examples/Input_Output/IO_examples.md +++ b/docs/Examples/Input_Output/IO_examples.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for chain inputs and outputs. Get spend vo keywords: [inputs outputs API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Inputs and Outputs ## Getting Spend Volume of a Token diff --git a/docs/Examples/Solana/address-api.md b/docs/Examples/Solana/address-api.md index d6f4a9f..dc492c2 100644 --- a/docs/Examples/Solana/address-api.md +++ b/docs/Examples/Solana/address-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Solana addresses. Get balances, annota keywords: [Solana API examples, Solana GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Solana Address API ## Latest Balance of an address diff --git a/docs/Examples/Solana/instructions.md b/docs/Examples/Solana/instructions.md index 11a25b4..baae1ba 100644 --- a/docs/Examples/Solana/instructions.md +++ b/docs/Examples/Solana/instructions.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Solana instructions. Get program instr keywords: [Solana API examples, Solana GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Solana Instructions Data ## Recent Solana Instructions diff --git a/docs/Examples/Solana/transactions-api.md b/docs/Examples/Solana/transactions-api.md index c40e7af..c5f3f8e 100644 --- a/docs/Examples/Solana/transactions-api.md +++ b/docs/Examples/Solana/transactions-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Solana transactions. Get transactions keywords: [Solana API examples, Solana GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Solana Transactions API ## Transactions in a specific timeperiod diff --git a/docs/Examples/Solana/transfers.md b/docs/Examples/Solana/transfers.md index a63c411..0b43e8f 100644 --- a/docs/Examples/Solana/transfers.md +++ b/docs/Examples/Solana/transfers.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Solana transfer data. Get SPL and SOL keywords: [Solana API examples, Solana GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Solana Historical Transfers API The Solana Historical Transfers API provides comprehensive access to token transfer data on the Solana blockchain, including SPL token transfers, SOL transfers, and detailed transaction information. This API enables real-time monitoring and historical analysis of all transfer activities across the Solana network. @@ -65,7 +50,7 @@ For real-time transfer monitoring, you can convert GraphQL queries to subscripti Learn more about [WebSocket subscriptions](https://docs.bitquery.io/docs/subscriptions/websockets/) and [real-time Solana data streams](https://docs.bitquery.io/docs/streams/real-time-solana-data/). -For streaming real-time data, check our [Solana Streaming API docs](https://docs.bitquery.io/docs/examples/Solana/) +For streaming real-time data, check our [Solana Streaming API docs](https://docs.bitquery.io/v1/docs/examples/Solana) ## Recent transfers to/from a wallet address diff --git a/docs/Examples/Staking/stake_examples.md b/docs/Examples/Staking/stake_examples.md index 6c65251..52b3cd5 100644 --- a/docs/Examples/Staking/stake_examples.md +++ b/docs/Examples/Staking/stake_examples.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for staking data. Get Cardano stake reward keywords: [staking API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Staking Data Examples ## Get Staking Data for a Stake Address on Cardano diff --git a/docs/Examples/Transactions/Trace_API.md b/docs/Examples/Transactions/Trace_API.md index 1c3a512..e429bf8 100644 --- a/docs/Examples/Transactions/Trace_API.md +++ b/docs/Examples/Transactions/Trace_API.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for EVM transaction traces. Inspect intern keywords: [Ethereum API examples, trace GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Ethereum Trace API ## What is Ethereum Trace? diff --git a/docs/Examples/Transactions/input-output-api.md b/docs/Examples/Transactions/input-output-api.md index 5452bd0..c397959 100644 --- a/docs/Examples/Transactions/input-output-api.md +++ b/docs/Examples/Transactions/input-output-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for UTXO inputs and outputs on Bitcoin-fam keywords: [UTXO API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # UTXO Input output API diff --git a/docs/Examples/Transactions/transaction-api.md b/docs/Examples/Transactions/transaction-api.md index 75b62b9..ca35342 100644 --- a/docs/Examples/Transactions/transaction-api.md +++ b/docs/Examples/Transactions/transaction-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for transactions on Bitcoin, Ethereum, and keywords: [transaction API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transaction API To get transactions from different blockchains, you can use our Transaction API. Let's see some examples. diff --git a/docs/Examples/Transfers/transfer-api.md b/docs/Examples/Transfers/transfer-api.md index be4a407..d749dd6 100644 --- a/docs/Examples/Transfers/transfer-api.md +++ b/docs/Examples/Transfers/transfer-api.md @@ -5,21 +5,6 @@ keywords: [transfer API examples, GraphQL queries, Bitquery] sidebar_position: 1 --- - - - - - - - - - - - - - - - # Transfer API Transfer API is available for all blockchains that have smart contract capabilities, especially EVMs. This api helps you get token (native or non-native) transfers. Let's see a few examples. diff --git a/docs/Examples/Zcash/address-api.md b/docs/Examples/Zcash/address-api.md index eab5f4e..2abf66b 100644 --- a/docs/Examples/Zcash/address-api.md +++ b/docs/Examples/Zcash/address-api.md @@ -293,7 +293,7 @@ You can query multiple addresses at once by using `{in: ["address1", "address2", Check out our other Zcash examples: -- [UTXO Input/Output API ➤](https://docs.bitquery.io/docs/Examples/Transactions/input-output-api/) -- [Transaction API ➤](https://docs.bitquery.io/docs/Examples/Transactions/transaction-api/) +- [UTXO Input/Output API ➤](https://docs.bitquery.io/v1/docs/examples/Transactions/input-output-api) +- [Transaction API ➤](https://docs.bitquery.io/v1/docs/examples/Transactions/transaction-api) ::: diff --git a/docs/Examples/Zcash/zenzec-api.md b/docs/Examples/Zcash/zenzec-api.md index 3e32509..a0641fd 100644 --- a/docs/Examples/Zcash/zenzec-api.md +++ b/docs/Examples/Zcash/zenzec-api.md @@ -150,7 +150,7 @@ query LatestTrades { **Need More Solana Token Data?** Check out our other Solana examples: -- [Solana Transfers API ➤](https://docs.bitquery.io/docs/Examples/Solana/transfers) -- [Solana DEX Trades API ➤](https://docs.bitquery.io/docs/Examples/dexTrades/) +- [Solana Transfers API ➤](https://docs.bitquery.io/v1/docs/examples/Solana/transfers) +- [Solana DEX Trades API ➤](https://docs.bitquery.io/v1/docs/examples/dexTrades/dex-trading-data-api) ::: diff --git a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md index c806c5c..29e5cd6 100644 --- a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md +++ b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for active addresses by chain or token. Co keywords: [active addresses API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Active address API Use our activeAddresses API to get active address for any blockchain, currency, block etc. diff --git a/docs/Examples/address/Blockchain-Address-API-Examples.md b/docs/Examples/address/Blockchain-Address-API-Examples.md index 900a4e3..0cd5ab7 100644 --- a/docs/Examples/address/Blockchain-Address-API-Examples.md +++ b/docs/Examples/address/Blockchain-Address-API-Examples.md @@ -5,21 +5,6 @@ keywords: [address API examples, GraphQL queries, Bitquery] sidebar_position: 1 --- - - - - - - - - - - - - - - - # Address API Our APIs can provide all sorts of details for any address on the blockchain. Let's see some examples. diff --git a/docs/Examples/address/specific-queries.md b/docs/Examples/address/specific-queries.md index c1b211a..d755705 100644 --- a/docs/Examples/address/specific-queries.md +++ b/docs/Examples/address/specific-queries.md @@ -5,21 +5,6 @@ keywords: [address API examples, GraphQL queries, Bitquery] sidebar_position: 2 --- - - - - - - - - - - - - - - - # Specific Queries on Address and Balances ## Get Native and Token Balance for a Matic Address diff --git a/docs/Examples/addressStats/address-stats-api.md b/docs/Examples/addressStats/address-stats-api.md index fad2817..0de6150 100644 --- a/docs/Examples/addressStats/address-stats-api.md +++ b/docs/Examples/addressStats/address-stats-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for EVM address statistics. Get balance, s keywords: [address stats API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Address Stats API diff --git a/docs/Examples/algorand/address.md b/docs/Examples/algorand/address.md index 86d7e7a..a36b020 100644 --- a/docs/Examples/algorand/address.md +++ b/docs/Examples/algorand/address.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Algorand addresses. Get balances, asse keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Algorand Address API Our Algorand Address API provides all details regarding any address on Algorand Blockchain. If given address is a smart contract, API also provides details of that smart contract too. Below are some examples of `address` API: diff --git a/docs/Examples/algorand/arguments.md b/docs/Examples/algorand/arguments.md index 142ecde..c074954 100644 --- a/docs/Examples/algorand/arguments.md +++ b/docs/Examples/algorand/arguments.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Algorand smart contract arguments on c keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Algorand Arguments API Our Algorand Arguments API provides all the details regarding all the arguments of smart contract calls and events. diff --git a/docs/Examples/algorand/blocks.md b/docs/Examples/algorand/blocks.md index 807142b..4c074cd 100644 --- a/docs/Examples/algorand/blocks.md +++ b/docs/Examples/algorand/blocks.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Algorand blocks. Get proposers, reward keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Algorand Blocks API Pur Alogrand Blocks API provides all details regarding blocks generated on Algorand Blockchain. Below are some examples of `blocks` API: diff --git a/docs/Examples/algorand/coinpath.md b/docs/Examples/algorand/coinpath.md index 3a6bc0f..d02348c 100644 --- a/docs/Examples/algorand/coinpath.md +++ b/docs/Examples/algorand/coinpath.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Algorand coinpath. Trace senders, rece keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Algorand Coinpath API Our Algorand Coinpath API provides detailed information about money flow of addresses on the Algorand Blockchain. diff --git a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md index d9ec4fa..2c14819 100644 --- a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin block data. Get recent blocks, keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Blocks API Our Bitcoin Blocks API provides all the information related to blocks produced on Bitcoin network. @@ -43,7 +28,7 @@ query { ``` -This query retrieves details about the 10 most recent blocks on the Cosmos blockchain. It includes information like block hash, height, difficulty, block size, and timestamp for each block. The results are ordered by block heights in descending order. +This query retrieves details about the 10 most recent blocks on the Bitcoin blockchain. It includes information like block hash, height, difficulty, block size, and timestamp for each block. The results are ordered by block heights in descending order. ## Get the Blocks with maximum Transactions @@ -70,5 +55,5 @@ This query fetches details about the 10 most transaction-laden blocks on the Bit - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/examples/Bitcoin/index) - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md index b05cb25..acbffb2 100644 --- a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin coinpath and fund flow data. T keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Coinpath API Our Bitcoin Coinpath API provides comprehensive information about money flow of addresses on the **Bitcoin** blockchain. diff --git a/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md b/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md index 4403c90..d9c6032 100644 --- a/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md +++ b/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers API.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin Omni Layer data. Get Omni tran keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Bitcoin OmniTransactions and OmniTransfers API ## Get the Latest Omni Transaction on Bitcoin @@ -74,5 +59,5 @@ This query provides all the omni transfers from a particular wallet address whic - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/examples/Bitcoin/index) - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md index 844e5fb..1ce03e6 100644 --- a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin transactions. Get latest txs, keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transaction API ## Get Latest Transaction @@ -104,5 +89,5 @@ The query retrieves the count of all transactions sent by the specified Bitcoin - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/examples/Bitcoin/index) - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/bitcoin-address-api.md b/docs/Examples/bitcoin/bitcoin-address-api.md index a0f1c0a..f64d356 100644 --- a/docs/Examples/bitcoin/bitcoin-address-api.md +++ b/docs/Examples/bitcoin/bitcoin-address-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin address data. Get balances, in keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # BTC Balance API Our Input/Output APIs provides all the details regarding any address on Bitcoin Blockchain. To get the balance simply get all inputs and outputs and subtract (outputs - inputs). If will give you bitcoin balance. You can also get bitcoin balance in USD as we also getting usd values inputs and outputs. Remember we actually multiple usd value of bitcoin at the time of transaction as we also have historical usd price of bitcoin. @@ -214,5 +199,5 @@ Try this API to get inputs and outputs of a bitcoin address here.[https://ide.bi - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/examples/Bitcoin/index) - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/Examples/bitcoin/bitcoin-fee-api.md b/docs/Examples/bitcoin/bitcoin-fee-api.md index b8c6624..7dc1f16 100644 --- a/docs/Examples/bitcoin/bitcoin-fee-api.md +++ b/docs/Examples/bitcoin/bitcoin-fee-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Bitcoin transaction fees. Get per-tx f keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Bitcoin Fee API This Bitquery API allows you to query Bitcoin transaction fees using GraphQL. You can retrieve detailed fee information for specific addresses, calculate total fees paid by an account, and convert fee values to USD. The examples below demonstrate how to use the API for common fee-related queries. @@ -89,5 +74,5 @@ query MyQuery { - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/Examples/bitcoin/index) +- [Bitcoin examples index](https://docs.bitquery.io/v1/docs/examples/Bitcoin/index) - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Examples/bitcoin/index.md b/docs/Examples/bitcoin/index.md index 5d921d6..52be42d 100644 --- a/docs/Examples/bitcoin/index.md +++ b/docs/Examples/bitcoin/index.md @@ -5,21 +5,6 @@ keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] slug: /examples/Bitcoin/ --- - - - - - - - - - - - - - - - # Bitcoin API Documentation This section contains Bitcoin API/Streams examples and guides, organized into categories for easier navigation. This is not exhaustive; we will add more examples as users request different scenarios. Also available in real-time via [Bitquery Kafka Streams](https://docs.bitquery.io/docs/streams/protobuf/chains/Bitcoin-protobuf/). Please contact sales for trial credentials. diff --git a/docs/Examples/coinpath/money-flow-api.md b/docs/Examples/coinpath/money-flow-api.md index 2d3a288..8b3af01 100644 --- a/docs/Examples/coinpath/money-flow-api.md +++ b/docs/Examples/coinpath/money-flow-api.md @@ -879,7 +879,7 @@ Discover direct and indirect funding relationships between a token creator and b You may also be interested in: -- [Cross-Chain API ➤](https://docs.bitquery.io/docs/Examples/cross-chain/cross-chain-api/) +- [Cross-Chain API ➤](https://docs.bitquery.io/v1/docs/examples/cross-chain/cross-chain-api) - [Solana DEX Trades API ➤](https://docs.bitquery.io/docs/blockchain/Solana/solana-dextrades/) - [Blockchain Address API Examples ➤](https://docs.bitquery.io/docs/blockchain/Ethereum/balances/balance-api/) - [Transaction API ➤](https://docs.bitquery.io/docs/blockchain/Ethereum/transactions/transaction-api/) diff --git a/docs/Examples/cosmos/address.md b/docs/Examples/cosmos/address.md index 11f9ff2..558d90b 100644 --- a/docs/Examples/cosmos/address.md +++ b/docs/Examples/cosmos/address.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos addresses. Get balances, transf keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Cosmos Address API Our Cosmos Address API provides all the details regarding any address on Cosmos Blockchain. diff --git a/docs/Examples/cosmos/attributes.md b/docs/Examples/cosmos/attributes.md index de607c6..8c04c83 100644 --- a/docs/Examples/cosmos/attributes.md +++ b/docs/Examples/cosmos/attributes.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos event attributes. Filter by eve keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Attributes API Our Cosmos Attribtues API provides all the details regarding event attributes from Cosmos network. diff --git a/docs/Examples/cosmos/blocks.md b/docs/Examples/cosmos/blocks.md index a21f433..5041ef1 100644 --- a/docs/Examples/cosmos/blocks.md +++ b/docs/Examples/cosmos/blocks.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos blocks. Get heights, proposers, keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Blocks API Our Cosmos Blocks API provides all the information related to blocks produced on Cosmos network. diff --git a/docs/Examples/cosmos/coinpath.md b/docs/Examples/cosmos/coinpath.md index dc321e1..050e78d 100644 --- a/docs/Examples/cosmos/coinpath.md +++ b/docs/Examples/cosmos/coinpath.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos coinpath flows. Trace funds bet keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Coinpath API Our Cosmos Coinpath API provides comprehensive information about money flow of addresses on the Cosmos blockchain. diff --git a/docs/Examples/cosmos/messages.md b/docs/Examples/cosmos/messages.md index 4d81269..5476fb5 100644 --- a/docs/Examples/cosmos/messages.md +++ b/docs/Examples/cosmos/messages.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos messages. Get message types by keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Messages API Our Cosmos Messages API provides all the information related to messages generated on Cosmos Blockchain. diff --git a/docs/Examples/cosmos/transactions.md b/docs/Examples/cosmos/transactions.md index f9e3696..f2c0468 100644 --- a/docs/Examples/cosmos/transactions.md +++ b/docs/Examples/cosmos/transactions.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos transactions. Get fees, gas, si keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transactions API Our Cosmos Transactions API provides information related to transactions created on Cosmos Blockchain. diff --git a/docs/Examples/cosmos/transfers.md b/docs/Examples/cosmos/transfers.md index fabe74e..2d02215 100644 --- a/docs/Examples/cosmos/transfers.md +++ b/docs/Examples/cosmos/transfers.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Cosmos transfers. Get transfers by sig keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transfers API Our Cosmos Transfers API provides all the information about token transfers happened on Cosmos Blockchain. diff --git a/docs/Examples/cross-chain/cross-chain-api.md b/docs/Examples/cross-chain/cross-chain-api.md index 6fd8f8a..464186f 100644 --- a/docs/Examples/cross-chain/cross-chain-api.md +++ b/docs/Examples/cross-chain/cross-chain-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries spanning multiple blockchains. Get balance keywords: [cross-chain API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Cross-Chain API In this section we see how to use Bitquery APIs to get information across multiple chains in one go. diff --git a/docs/Examples/dexTrades/dex-pool-api.md b/docs/Examples/dexTrades/dex-pool-api.md index 12ba86a..55199c6 100644 --- a/docs/Examples/dexTrades/dex-pool-api.md +++ b/docs/Examples/dexTrades/dex-pool-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for DEX liquidity pools. Get pair creation keywords: [DEX API examples, DEX GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Pools API In this section, we will look at some examples regarding DEX Pools data. diff --git a/docs/Examples/dexTrades/dex-trading-data-api.md b/docs/Examples/dexTrades/dex-trading-data-api.md index cbbb75e..9a5d9ca 100644 --- a/docs/Examples/dexTrades/dex-trading-data-api.md +++ b/docs/Examples/dexTrades/dex-trading-data-api.md @@ -5,21 +5,6 @@ keywords: [DEX API examples, DEX GraphQL queries, Bitquery] sidebar_position: 1 --- - - - - - - - - - - - - - - - # DEX Trading Data APIs Our DEX trading APIs provides DEX data for 100s of DEXs from [40+ blockchains](https://app-status.bitquery.io/). Let's see some of example of getting DEX data. diff --git a/docs/Examples/dexTrades/ohlc.md b/docs/Examples/dexTrades/ohlc.md index c23407e..f64ae3b 100644 --- a/docs/Examples/dexTrades/ohlc.md +++ b/docs/Examples/dexTrades/ohlc.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for DEX OHLC candle data. Get open, high, keywords: [DEX API examples, DEX GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # OHLC API Using our APIs, you can also get [OHLC](https://en.wikipedia.org/wiki/Open-high-low-close_chart) data. diff --git a/docs/Examples/filecoin/messages.md b/docs/Examples/filecoin/messages.md index e8eb230..4fc1513 100644 --- a/docs/Examples/filecoin/messages.md +++ b/docs/Examples/filecoin/messages.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Filecoin messages and storage deals. T keywords: [Filecoin API examples, Filecoin GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Filecoin Storage & Deal Data Examples In this section we will see some example queries that track different stages in a storae deal flow on Filecoin. For further details on Storage deals on Filecoin, refer to their [official documentation](https://docs.filecoin.io/storage-providers/filecoin-deals/storage-deals). diff --git a/docs/Examples/hedera/hedera-address.md b/docs/Examples/hedera/hedera-address.md index c66f6bc..83cefab 100644 --- a/docs/Examples/hedera/hedera-address.md +++ b/docs/Examples/hedera/hedera-address.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Hedera accounts. Get latest HBAR balan keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Hedera Address API In this section we will see how to get information on wallets on Hedera. diff --git a/docs/Examples/hedera/hedera-io.md b/docs/Examples/hedera/hedera-io.md index e1fba67..7ba9418 100644 --- a/docs/Examples/hedera/hedera-io.md +++ b/docs/Examples/hedera/hedera-io.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Hedera transfers and account balances. keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Hedera Inputs & Outputs API diff --git a/docs/Examples/hedera/hedera-messages.md b/docs/Examples/hedera/hedera-messages.md index ed28d0e..6ef3721 100644 --- a/docs/Examples/hedera/hedera-messages.md +++ b/docs/Examples/hedera/hedera-messages.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Hedera network messages. Get memos, no keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Hedera Messages API diff --git a/docs/Examples/hedera/hedera-transactions.md b/docs/Examples/hedera/hedera-transactions.md index 7f3519f..c21e50e 100644 --- a/docs/Examples/hedera/hedera-transactions.md +++ b/docs/Examples/hedera/hedera-transactions.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Hedera consensus transactions. Get fee keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Hedera Transactions API diff --git a/docs/Examples/overview.md b/docs/Examples/overview.md index a3c4e78..da7612d 100644 --- a/docs/Examples/overview.md +++ b/docs/Examples/overview.md @@ -5,21 +5,6 @@ description: "Browse ready-made GraphQL examples for Bitquery APIs—learn what keywords: [Bitquery, GraphQL examples, blockchain API, query library, documentation] --- - - - - - - - - - - - - - - - # Overview In this section we will see some examples of how to use the different APIs and what data you can get using them. @@ -29,5 +14,5 @@ In this section we will see some examples of how to use the different APIs and w - [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) - [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) \ No newline at end of file diff --git a/docs/Examples/ripple/nft_token_offers.md b/docs/Examples/ripple/nft_token_offers.md index d75fdb0..b876cd5 100644 --- a/docs/Examples/ripple/nft_token_offers.md +++ b/docs/Examples/ripple/nft_token_offers.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for XRPL NFT token offers. Filter by sende keywords: [Ripple API examples, XRP GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Ripple NFT Token Offers API Ripple NFT Token Offers API provides all details regarding NFT Token offers on Ripple Blockchain. Below are some examples of `nftokenOffers` API: diff --git a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md index 4aa06b9..9eaca89 100644 --- a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md +++ b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for EVM smart contract calls. Get methods, keywords: [smart contract API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Smart contract call API Our Smart contract call API allows you access to parsed smart contract calls and arguments for all the blockchains we support. diff --git a/docs/Examples/smartcontractEvents/Non_EVM_events.md b/docs/Examples/smartcontractEvents/Non_EVM_events.md index 097f84b..7cca976 100644 --- a/docs/Examples/smartcontractEvents/Non_EVM_events.md +++ b/docs/Examples/smartcontractEvents/Non_EVM_events.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for events on non-EVM chains like Flow. Ge keywords: [smart contract API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Events on Non-EVM Chains Our Smart contract event API allows you access parsed smart contract events and arguments for all the blockchains we support. In this section let's focus on examples for chain other than ones on EVM. diff --git a/docs/Examples/smartcontractEvents/smart-contract-events-api.md b/docs/Examples/smartcontractEvents/smart-contract-events-api.md index 0d34e31..7775634 100644 --- a/docs/Examples/smartcontractEvents/smart-contract-events-api.md +++ b/docs/Examples/smartcontractEvents/smart-contract-events-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for EVM smart contract events. Get logs, t keywords: [smart contract API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Smart contract event API Our Smart contract event API allows you access parsed smart contract events and arguments for all the blockchains we support. diff --git a/docs/Examples/stellar/stellar-address-api.md b/docs/Examples/stellar/stellar-address-api.md index d9f300b..9a8b75e 100644 --- a/docs/Examples/stellar/stellar-address-api.md +++ b/docs/Examples/stellar/stellar-address-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Stellar addresses. Get wallet balances keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Stellar Address API This API allows you to retrieve detailed information about Stellar wallet addresses, including their balances and token holdings. diff --git a/docs/Examples/stellar/stellar-effects-api.md b/docs/Examples/stellar/stellar-effects-api.md index 032d8f1..86bca6a 100644 --- a/docs/Examples/stellar/stellar-effects-api.md +++ b/docs/Examples/stellar/stellar-effects-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Stellar ledger effects. Get state chan keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Stellar Effects API All changes on the ledger are recorded as effects including changes after transactions, trades and so on. In this section we will see how to use Bitquery API to get effects information. diff --git a/docs/Examples/stellar/stellar-liquiditypool-api.md b/docs/Examples/stellar/stellar-liquiditypool-api.md index e86cd3b..c6ea827 100644 --- a/docs/Examples/stellar/stellar-liquiditypool-api.md +++ b/docs/Examples/stellar/stellar-liquiditypool-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Stellar liquidity pool effects. Get po keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Stellar Liquidity Pools API This API allows you to access and analyze effects from Stellar's liquidity pools. Effects are specific changes that occur within the ledger due to operations performed on the liquidity pools. diff --git a/docs/Examples/stellar/stellar-payments-api.md b/docs/Examples/stellar/stellar-payments-api.md index 8aa23e7..d693cb2 100644 --- a/docs/Examples/stellar/stellar-payments-api.md +++ b/docs/Examples/stellar/stellar-payments-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Stellar payments. Get amounts, currenc keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Stellar Payments API This API enables you to access and analyze payment transactions on the Stellar network, providing detailed information about each payment, including amounts, currencies, issuers, timestamps, and paths. diff --git a/docs/Examples/stellar/stellar-tradeeffects-api.md b/docs/Examples/stellar/stellar-tradeeffects-api.md index 078aced..98cae3e 100644 --- a/docs/Examples/stellar/stellar-tradeeffects-api.md +++ b/docs/Examples/stellar/stellar-tradeeffects-api.md @@ -5,21 +5,6 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] slug: /blockchain/Stellar/trade-effects-api --- - - - - - - - - - - - - - - - # Stellar Trades API diff --git a/docs/Examples/stellar/stellar-transactions-api.md b/docs/Examples/stellar/stellar-transactions-api.md index 83eeff8..795bba5 100644 --- a/docs/Examples/stellar/stellar-transactions-api.md +++ b/docs/Examples/stellar/stellar-transactions-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Stellar transactions. Get fees, hashes keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Stellar Transactions API This API enables you to access and analyze transactions on the Stellar network, providing detailed information about each transaction, including the fee, hash, sender, and timestamp. diff --git a/docs/Examples/tokens/token-api.md b/docs/Examples/tokens/token-api.md index e75f349..2d4edc8 100644 --- a/docs/Examples/tokens/token-api.md +++ b/docs/Examples/tokens/token-api.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for token prices, holders, supply, and DEX keywords: [token API examples, GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Token API Bitquery's flexible GraphQL APIs will help you get all sorts of token related data. We will show example of USDT on Ethereum but you can actually use same APIs to get data for any token on all chains supported by Bitquery. diff --git a/docs/Examples/tron/address.md b/docs/Examples/tron/address.md index b4cb1a8..02a8d64 100644 --- a/docs/Examples/tron/address.md +++ b/docs/Examples/tron/address.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron addresses. Get balance, rewards, keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Address API Our Tron Address API provides all details regarding any address on Tron Blockchain. If given address is a smart contract API also details of that smart contract too. diff --git a/docs/Examples/tron/arguments.md b/docs/Examples/tron/arguments.md index 17a20ba..7c71b2b 100644 --- a/docs/Examples/tron/arguments.md +++ b/docs/Examples/tron/arguments.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron smart contract call arguments. Fi keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Arguments API diff --git a/docs/Examples/tron/blocks.md b/docs/Examples/tron/blocks.md index da05476..78b7d2e 100644 --- a/docs/Examples/tron/blocks.md +++ b/docs/Examples/tron/blocks.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron blocks. Get recent blocks, witnes keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Blocks API diff --git a/docs/Examples/tron/coinpath.md b/docs/Examples/tron/coinpath.md index eec8797..dd727c4 100644 --- a/docs/Examples/tron/coinpath.md +++ b/docs/Examples/tron/coinpath.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron coinpath and fund flows. Trace se keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Coinpath API diff --git a/docs/Examples/tron/contracts.md b/docs/Examples/tron/contracts.md index f14602c..74b006f 100644 --- a/docs/Examples/tron/contracts.md +++ b/docs/Examples/tron/contracts.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron smart contracts and on-chain cont keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Contracts API ## Related Resources diff --git a/docs/Examples/tron/dexTrades.md b/docs/Examples/tron/dexTrades.md index 92c50f4..a2e4e73 100644 --- a/docs/Examples/tron/dexTrades.md +++ b/docs/Examples/tron/dexTrades.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron DEX trades. Get pairs, base/quote keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # DEX Trade API diff --git a/docs/Examples/tron/smartContractCalls.md b/docs/Examples/tron/smartContractCalls.md index 9b3d1ba..8f2b553 100644 --- a/docs/Examples/tron/smartContractCalls.md +++ b/docs/Examples/tron/smartContractCalls.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron smart contract calls. Filter by m keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Smart Contract Calls API diff --git a/docs/Examples/tron/smartContractEvents.md b/docs/Examples/tron/smartContractEvents.md index 5a60090..62a2772 100644 --- a/docs/Examples/tron/smartContractEvents.md +++ b/docs/Examples/tron/smartContractEvents.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron smart contract events. Filter by keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Smart Contract Events API diff --git a/docs/Examples/tron/transaction.md b/docs/Examples/tron/transaction.md index 163123e..58c5685 100644 --- a/docs/Examples/tron/transaction.md +++ b/docs/Examples/tron/transaction.md @@ -4,21 +4,6 @@ description: "Example GraphQL queries for Tron transactions. Get transactions by keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transaction API Our Tron Transaction API provides detailed information about transactions from Tron Blockchain. diff --git a/docs/Examples/tron/transfers.md b/docs/Examples/tron/transfers.md index acd003f..b03b3b3 100644 --- a/docs/Examples/tron/transfers.md +++ b/docs/Examples/tron/transfers.md @@ -4,24 +4,9 @@ description: "Example GraphQL queries for Tron token transfers. Get latest trans keywords: [Tron API examples, Tron GraphQL queries, Bitquery] --- - - - - - - - - - - - - - - - # Transfer API -Our Tron Transfers API rpovides detailed information about token transfers made on the Tron blockchain. +Our Tron Transfers API provides detailed information about token transfers made on the Tron blockchain. ## Get latest transfer for a token diff --git a/docs/Schema/Avalanche/overview.md b/docs/Schema/Avalanche/overview.md index 460562c..db4f4a9 100644 --- a/docs/Schema/Avalanche/overview.md +++ b/docs/Schema/Avalanche/overview.md @@ -5,21 +5,6 @@ description: "Access Avalanche blockchain data through Bitquery's GraphQL API. Q keywords: [Avalanche API, Avalanche GraphQL, Avalanche blockchain data, Bitquery] --- - - - - - - - - - - - - - - - Avalanche is an open-source platform for building dApps that uses its own consensus protocol (Avalanche Consensus). Bitquery offers a Avalanche C-Chain [explorer](https://explorer.bitquery.io/avalanche) to view Avalanche data easily. diff --git a/docs/Schema/Cronos/activeaddresses.md b/docs/Schema/Cronos/activeaddresses.md index 2d035f3..c663f21 100644 --- a/docs/Schema/Cronos/activeaddresses.md +++ b/docs/Schema/Cronos/activeaddresses.md @@ -4,21 +4,6 @@ description: "Query Cronos active addresses data using Bitquery GraphQL API. Get keywords: ["Cronos API", "Cronos Active Addresses", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the cronos blockchain. diff --git a/docs/Schema/Cronos/address.md b/docs/Schema/Cronos/address.md index 6337384..a168a4b 100644 --- a/docs/Schema/Cronos/address.md +++ b/docs/Schema/Cronos/address.md @@ -4,21 +4,6 @@ description: "Query Cronos address data using Bitquery GraphQL API. Get address keywords: ["Cronos API", "Cronos Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` allows us to retrieve information about a specific address. diff --git a/docs/Schema/Cronos/addresstats.md b/docs/Schema/Cronos/addresstats.md index 786f6a3..15a35bb 100644 --- a/docs/Schema/Cronos/addresstats.md +++ b/docs/Schema/Cronos/addresstats.md @@ -4,21 +4,6 @@ description: "Query Cronos address stats data using Bitquery GraphQL API. Get ag keywords: ["Cronos API", "Cronos Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. diff --git a/docs/Schema/Cronos/arguments.md b/docs/Schema/Cronos/arguments.md index 1df9049..8347324 100644 --- a/docs/Schema/Cronos/arguments.md +++ b/docs/Schema/Cronos/arguments.md @@ -4,21 +4,6 @@ description: "Query Cronos GraphQL arguments data using Bitquery GraphQL API. Ge keywords: ["Cronos API", "Cronos Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. diff --git a/docs/Schema/Cronos/blocks.md b/docs/Schema/Cronos/blocks.md index 2dc3e07..fe73d09 100644 --- a/docs/Schema/Cronos/blocks.md +++ b/docs/Schema/Cronos/blocks.md @@ -4,21 +4,6 @@ description: "Query Cronos blocks data using Bitquery GraphQL API. Get block hei keywords: ["Cronos API", "Cronos Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The `blocks` field allows us to retrieve information about the blocks from the cronos blockchain. diff --git a/docs/Schema/Cronos/coinpath.md b/docs/Schema/Cronos/coinpath.md index aea02c0..157a6c2 100644 --- a/docs/Schema/Cronos/coinpath.md +++ b/docs/Schema/Cronos/coinpath.md @@ -4,21 +4,6 @@ description: "Query Cronos coinpath data using Bitquery GraphQL API. Get fund fl keywords: ["Cronos API", "Cronos Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology. diff --git a/docs/Schema/Cronos/dextrades.md b/docs/Schema/Cronos/dextrades.md index 2384e3e..20c8a7e 100644 --- a/docs/Schema/Cronos/dextrades.md +++ b/docs/Schema/Cronos/dextrades.md @@ -4,21 +4,6 @@ description: "Query Cronos DEX trades data using Bitquery GraphQL API. Get DEX s keywords: ["Cronos API", "Cronos DEX Trades", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. diff --git a/docs/Schema/Cronos/overview.md b/docs/Schema/Cronos/overview.md index 021753d..1a63adf 100644 --- a/docs/Schema/Cronos/overview.md +++ b/docs/Schema/Cronos/overview.md @@ -5,21 +5,6 @@ description: "Access Cronos blockchain data through Bitquery's GraphQL API. Quer keywords: [Cronos API, Cronos GraphQL, Cronos blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery Cronos API offers access to indexed data from the cronos blockchain via GraphQL API for developers. diff --git a/docs/Schema/Cronos/references.md b/docs/Schema/Cronos/references.md index 7037a21..ecd2000 100644 --- a/docs/Schema/Cronos/references.md +++ b/docs/Schema/Cronos/references.md @@ -4,21 +4,6 @@ description: "Query Cronos schema references data using Bitquery GraphQL API. Ge keywords: ["Cronos API", "Cronos References", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # References
diff --git a/docs/Schema/Cronos/smartcontractcalls.md b/docs/Schema/Cronos/smartcontractcalls.md index 6870a2f..acc80e7 100644 --- a/docs/Schema/Cronos/smartcontractcalls.md +++ b/docs/Schema/Cronos/smartcontractcalls.md @@ -4,21 +4,6 @@ description: "Query Cronos smart contract calls data using Bitquery GraphQL API. keywords: ["Cronos API", "Cronos Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Calls `smartContractCalls` type allows you to retrieve smart contract calls made to any smart contract on Ethereum Blockchain. diff --git a/docs/Schema/Cronos/smartcontractevents.md b/docs/Schema/Cronos/smartcontractevents.md index 2b34dba..bc37ff4 100644 --- a/docs/Schema/Cronos/smartcontractevents.md +++ b/docs/Schema/Cronos/smartcontractevents.md @@ -4,21 +4,6 @@ description: "Query Cronos smart contract events data using Bitquery GraphQL API keywords: ["Cronos API", "Cronos Smart Contract Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Events `smartContractEvents` type allows you to retrieve all events emitted by different smart contracts on cronos Blockchain. diff --git a/docs/Schema/Cronos/transactions.md b/docs/Schema/Cronos/transactions.md index 3700055..cb01210 100644 --- a/docs/Schema/Cronos/transactions.md +++ b/docs/Schema/Cronos/transactions.md @@ -4,21 +4,6 @@ description: "Query Cronos transactions data using Bitquery GraphQL API. Get tra keywords: ["Cronos API", "Cronos Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions Bitquery `transactions` API allows you to retrieve all the blockchain transactions from cronos Blockchain. diff --git a/docs/Schema/Cronos/transfers.md b/docs/Schema/Cronos/transfers.md index 253aa68..0b2a2ce 100644 --- a/docs/Schema/Cronos/transfers.md +++ b/docs/Schema/Cronos/transfers.md @@ -4,21 +4,6 @@ description: "Query Cronos transfers data using Bitquery GraphQL API. Get asset keywords: ["Cronos API", "Cronos Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers Bitquery `transfers` API allows you to retrieve currency or token transfers from cronos Blockchain. diff --git a/docs/Schema/Dash/overview.md b/docs/Schema/Dash/overview.md index 163d8e0..b828b57 100644 --- a/docs/Schema/Dash/overview.md +++ b/docs/Schema/Dash/overview.md @@ -5,21 +5,6 @@ description: "Access Dash blockchain data through Bitquery's GraphQL API. Query keywords: [Dash API, Dash GraphQL, Dash blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Dash API Overview Bitquery API offers access to indexed data from the Dash blockchain through the Dash schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. diff --git a/docs/Schema/Dogecoin/overview.md b/docs/Schema/Dogecoin/overview.md index 91b5125..c447ae4 100644 --- a/docs/Schema/Dogecoin/overview.md +++ b/docs/Schema/Dogecoin/overview.md @@ -5,21 +5,6 @@ description: "Access Dogecoin blockchain data through Bitquery's GraphQL API. Qu keywords: [Dogecoin API, Dogecoin GraphQL, Dogecoin blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Dogecoin API Overview Bitquery API offers access to indexed data from the Dogecoin blockchain through the Dogecoin schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. diff --git a/docs/Schema/Polygon/overview.md b/docs/Schema/Polygon/overview.md index 5695b59..4746df9 100644 --- a/docs/Schema/Polygon/overview.md +++ b/docs/Schema/Polygon/overview.md @@ -6,22 +6,6 @@ keywords: [Polygon API, Polygon GraphQL, Polygon blockchain data, Bitquery] --- - - - - - - - - - - - - - - - - ## What is Polygon(Matic) API? Bitquery's GraphQL API offers access to indexed data from the Polygon (Matic) blockchain. diff --git a/docs/Schema/algorand/address.md b/docs/Schema/algorand/address.md index 07e4fe3..e944f3f 100644 --- a/docs/Schema/algorand/address.md +++ b/docs/Schema/algorand/address.md @@ -4,21 +4,6 @@ description: "Query Algorand address data using Bitquery GraphQL API. Get addres keywords: ["Algorand API", "Algorand Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` field allows us to fetch information about a specific address or a list of addresses from the Algorand blockchain. diff --git a/docs/Schema/algorand/arguments.md b/docs/Schema/algorand/arguments.md index 4fd8bad..dfdca9f 100644 --- a/docs/Schema/algorand/arguments.md +++ b/docs/Schema/algorand/arguments.md @@ -4,21 +4,6 @@ description: "Query Algorand GraphQL arguments data using Bitquery GraphQL API. keywords: ["Algorand API", "Algorand Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and events. diff --git a/docs/Schema/algorand/blocks.md b/docs/Schema/algorand/blocks.md index de01eca..ecb5147 100644 --- a/docs/Schema/algorand/blocks.md +++ b/docs/Schema/algorand/blocks.md @@ -4,21 +4,6 @@ description: "Query Algorand blocks data using Bitquery GraphQL API. Get block h keywords: ["Algorand API", "Algorand Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The `blocks` field allows us to retrieve details about blocks from Algorand blockchain. diff --git a/docs/Schema/algorand/coinpath.md b/docs/Schema/algorand/coinpath.md index 3744d2f..3795544 100644 --- a/docs/Schema/algorand/coinpath.md +++ b/docs/Schema/algorand/coinpath.md @@ -4,21 +4,6 @@ description: "Query Algorand coinpath data using Bitquery GraphQL API. Get fund keywords: ["Algorand API", "Algorand Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology from Algorand. diff --git a/docs/Schema/algorand/overview.md b/docs/Schema/algorand/overview.md index 491b60e..c35fde7 100644 --- a/docs/Schema/algorand/overview.md +++ b/docs/Schema/algorand/overview.md @@ -5,21 +5,6 @@ description: "Access Algorand blockchain data through Bitquery's GraphQL API. Qu keywords: [Algorand API, Algorand GraphQL, Algorand blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery API offers access to indexed data from the Algorand blockchain. diff --git a/docs/Schema/algorand/smartContractCalls.md b/docs/Schema/algorand/smartContractCalls.md index 0499c10..d3e8554 100644 --- a/docs/Schema/algorand/smartContractCalls.md +++ b/docs/Schema/algorand/smartContractCalls.md @@ -4,21 +4,6 @@ description: "Query Algorand smart contract calls data using Bitquery GraphQL AP keywords: ["Algorand API", "Algorand Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Calls The `smartContractCalls` field allows you to retrieve smart contract calls made to any smart contract on Algorand blockchain. diff --git a/docs/Schema/algorand/transactions.md b/docs/Schema/algorand/transactions.md index ba0b5c3..5f104f1 100644 --- a/docs/Schema/algorand/transactions.md +++ b/docs/Schema/algorand/transactions.md @@ -4,21 +4,6 @@ description: "Query Algorand transactions data using Bitquery GraphQL API. Get t keywords: ["Algorand API", "Algorand Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Algorand Transactions API can be used to get information about transactions, such as the sender, the recipient, the amount, the fee, and the timestamp. Here are the fields in the schema. diff --git a/docs/Schema/algorand/transfers.md b/docs/Schema/algorand/transfers.md index ec86a66..e586c1e 100644 --- a/docs/Schema/algorand/transfers.md +++ b/docs/Schema/algorand/transfers.md @@ -4,21 +4,6 @@ description: "Query Algorand transfers data using Bitquery GraphQL API. Get asse keywords: ["Algorand API", "Algorand Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The `transfers` field allows us to fetch details about token transfers from the Algorand blockchain. diff --git a/docs/Schema/binance_smart_chain/overview.md b/docs/Schema/binance_smart_chain/overview.md index d728b9e..2f4e9f6 100644 --- a/docs/Schema/binance_smart_chain/overview.md +++ b/docs/Schema/binance_smart_chain/overview.md @@ -5,21 +5,6 @@ description: "Access BNB Smart Chain blockchain data through Bitquery's GraphQL keywords: [BNB Smart Chain API, BNB Smart Chain GraphQL, BNB Smart Chain blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # BNB API Overview Bitquery API offers access to indexed data from the BNB blockchain via GraphQL API for developers. diff --git a/docs/Schema/bitcoin/addressstats.md b/docs/Schema/bitcoin/addressstats.md index 6d4b27b..ef5a9d5 100644 --- a/docs/Schema/bitcoin/addressstats.md +++ b/docs/Schema/bitcoin/addressstats.md @@ -24,7 +24,7 @@ description: "Get address balance and history on the Bitcoin blockchain. Also, g The `addressstats` field allows us to retrieves statistics related to blockchain addresses. -Here is an example that demonstrates how to retrieve statistics about a specific address; there is a balance field, too; please avoid using it; if you require a BTC balance, then please use [this API](https://docs.bitquery.io/v1/docs/Examples/bitcoin%20/bitcoin-address-api). +Here is an example that demonstrates how to retrieve statistics about a specific address; there is a balance field, too; please avoid using it; if you require a BTC balance, then please use [this API](https://docs.bitquery.io/v1/docs/examples/Bitcoin/bitcoin-address-api). ``` { @@ -60,7 +60,7 @@ Here is an example that demonstrates how to retrieve statistics about a specific ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/blocks.md b/docs/Schema/bitcoin/blocks.md index dcd428f..25db601 100644 --- a/docs/Schema/bitcoin/blocks.md +++ b/docs/Schema/bitcoin/blocks.md @@ -92,7 +92,7 @@ The following fields are available for the `blocks`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/coinpath.md b/docs/Schema/bitcoin/coinpath.md index b10bbeb..c5d23be 100644 --- a/docs/Schema/bitcoin/coinpath.md +++ b/docs/Schema/bitcoin/coinpath.md @@ -6,7 +6,7 @@ description: "Track flow of funds up to any depth on the Bitcoin blockchain. Als - + @@ -60,7 +60,7 @@ The following are available fields for the `coinpath`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/inputs.md b/docs/Schema/bitcoin/inputs.md index dd00a70..c974a0c 100644 --- a/docs/Schema/bitcoin/inputs.md +++ b/docs/Schema/bitcoin/inputs.md @@ -100,7 +100,7 @@ The following are available fields for the `inputs`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/omnitransactions.md b/docs/Schema/bitcoin/omnitransactions.md index cafe598..7203ca8 100644 --- a/docs/Schema/bitcoin/omnitransactions.md +++ b/docs/Schema/bitcoin/omnitransactions.md @@ -100,7 +100,7 @@ The following are available fields for the `omniTransactions`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/omnitransfers.md b/docs/Schema/bitcoin/omnitransfers.md index 9648e2f..6050b1a 100644 --- a/docs/Schema/bitcoin/omnitransfers.md +++ b/docs/Schema/bitcoin/omnitransfers.md @@ -111,7 +111,7 @@ Omni Transfers can be filtered using the following arguments: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/outputs.md b/docs/Schema/bitcoin/outputs.md index bc877c7..695cca3 100644 --- a/docs/Schema/bitcoin/outputs.md +++ b/docs/Schema/bitcoin/outputs.md @@ -107,7 +107,7 @@ The following are available fields for the `outputs`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/overview.md b/docs/Schema/bitcoin/overview.md index 7418c1e..d05c517 100644 --- a/docs/Schema/bitcoin/overview.md +++ b/docs/Schema/bitcoin/overview.md @@ -1,25 +1,10 @@ --- sidebar_position: 1 title: "Bitcoin API — Blockchain Data Schema | Bitquery" -description: "Access Bitcoin blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +description: "Access Bitcoin blockchain data through Bitquery's GraphQL API. Query blocks, transactions, addresses, coinpath fund tracking, and UTXO data." keywords: [Bitcoin API, Bitcoin GraphQL, Bitcoin blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Bitcoin API Overview Bitquery API offers access to indexed data from the Bitcoin blockchain through the bitcoin schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. @@ -42,6 +27,6 @@ Let's dive in and explore the Bitcoin data available through Bitquery API. - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/bitcoin/transactions.md b/docs/Schema/bitcoin/transactions.md index 0d80c8c..4bf3585 100644 --- a/docs/Schema/bitcoin/transactions.md +++ b/docs/Schema/bitcoin/transactions.md @@ -1,11 +1,11 @@ --- title: Bitcoin Transactions API -description: "Get information on transaction details and wallets on the Bitcoin blockchain. Also, get information on blocks for tokens or NFTs on the Bitcoin blockchain." +description: "Query Bitcoin transactions via GraphQL: transaction hash, inputs and outputs, fees, sizes, and block height and timestamps." --- - + @@ -14,12 +14,12 @@ description: "Get information on transaction details and wallets on the Bitcoin - + - + The `transactions` allows us to fetch details about transactions from Bitcoins network. @@ -124,7 +124,7 @@ The following are available fields for the `transactions`: ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/cardano/address.md b/docs/Schema/cardano/address.md index e310a76..b348c7b 100644 --- a/docs/Schema/cardano/address.md +++ b/docs/Schema/cardano/address.md @@ -4,21 +4,6 @@ description: "Query Cardano address data using Bitquery GraphQL API. Get address keywords: ["Cardano API", "Cardano Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The Address API schema returns information about a wallet. The schema includes the following fields: diff --git a/docs/Schema/cardano/addressstats.md b/docs/Schema/cardano/addressstats.md index d61c1ca..4a39026 100644 --- a/docs/Schema/cardano/addressstats.md +++ b/docs/Schema/cardano/addressstats.md @@ -4,21 +4,6 @@ description: "Query Cardano address stats data using Bitquery GraphQL API. Get a keywords: ["Cardano API", "Cardano Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # AddressStats The AddressStats API schema returns information about a wallet on its inflows, outflows and activity. The schema includes the following fields: diff --git a/docs/Schema/cardano/blocks.md b/docs/Schema/cardano/blocks.md index 3cd406b..780f588 100644 --- a/docs/Schema/cardano/blocks.md +++ b/docs/Schema/cardano/blocks.md @@ -4,21 +4,6 @@ description: "Query Cardano blocks data using Bitquery GraphQL API. Get block he keywords: ["Cardano API", "Cardano Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks diff --git a/docs/Schema/cardano/coinpath.md b/docs/Schema/cardano/coinpath.md index a228dd7..7ef1a1a 100644 --- a/docs/Schema/cardano/coinpath.md +++ b/docs/Schema/cardano/coinpath.md @@ -4,21 +4,6 @@ description: "Query Cardano coinpath data using Bitquery GraphQL API. Get fund f keywords: ["Cardano API", "Cardano Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath Coinpath APIs are a set of money-tracing APIs that help you track funds from one address to another. diff --git a/docs/Schema/cardano/inputsOutputs.md b/docs/Schema/cardano/inputsOutputs.md index 402095c..abbc5fa 100644 --- a/docs/Schema/cardano/inputsOutputs.md +++ b/docs/Schema/cardano/inputsOutputs.md @@ -4,21 +4,6 @@ description: "Query Cardano inputs outputs data using Bitquery GraphQL API. Get keywords: ["Cardano API", "Cardano Inputs and Outputs", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Inputs and Outputs The Inputs and Outputs API schema returns information about the inputs and outputs of a transaction. The schema includes the following fields: diff --git a/docs/Schema/cardano/mints.md b/docs/Schema/cardano/mints.md index 6ac58cb..1953b5a 100644 --- a/docs/Schema/cardano/mints.md +++ b/docs/Schema/cardano/mints.md @@ -4,21 +4,6 @@ description: "Query Cardano mints data using Bitquery GraphQL API. Get mint even keywords: ["Cardano API", "Cardano Mints", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Mints The Mints API query returns information about the mints on the Cardano network. A mint is an event where new tokens are created. The query returns information about the block that the mint occurred in, the amount of tokens minted, the transaction that minted the tokens, and the currency that was minted. diff --git a/docs/Schema/cardano/overview.md b/docs/Schema/cardano/overview.md index 5acded7..9ffa2ed 100644 --- a/docs/Schema/cardano/overview.md +++ b/docs/Schema/cardano/overview.md @@ -5,21 +5,6 @@ description: "Access Cardano blockchain data through Bitquery's GraphQL API. Que keywords: [Cardano API, Cardano GraphQL, Cardano blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery provides as [explorer](https://explorer.bitquery.io/cardano) for you to easily view data on Cardano. diff --git a/docs/Schema/cardano/transactions.md b/docs/Schema/cardano/transactions.md index 08fe93e..62abdb1 100644 --- a/docs/Schema/cardano/transactions.md +++ b/docs/Schema/cardano/transactions.md @@ -4,21 +4,6 @@ description: "Query Cardano transactions data using Bitquery GraphQL API. Get tr keywords: ["Cardano API", "Cardano Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Transactions API schema returns a list of transactions that occurred on the Cardano blockchain within a specified date range. The schema includes the following fields: diff --git a/docs/Schema/celo/activeaddresses.md b/docs/Schema/celo/activeaddresses.md index dd39555..bebc02e 100644 --- a/docs/Schema/celo/activeaddresses.md +++ b/docs/Schema/celo/activeaddresses.md @@ -4,21 +4,6 @@ description: "Query Celo active addresses data using Bitquery GraphQL API. Get a keywords: ["Celo API", "Celo Active Addresses", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the Celo blockchain. diff --git a/docs/Schema/celo/address.md b/docs/Schema/celo/address.md index 1be6bb6..a88ff45 100644 --- a/docs/Schema/celo/address.md +++ b/docs/Schema/celo/address.md @@ -4,21 +4,6 @@ description: "Query Celo address data using Bitquery GraphQL API. Get address ba keywords: ["Celo API", "Celo Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` allows us to retrieve information about a specific address. diff --git a/docs/Schema/celo/addresstats.md b/docs/Schema/celo/addresstats.md index f93417b..b501fd1 100644 --- a/docs/Schema/celo/addresstats.md +++ b/docs/Schema/celo/addresstats.md @@ -4,21 +4,6 @@ description: "Query Celo address stats data using Bitquery GraphQL API. Get aggr keywords: ["Celo API", "Celo Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. diff --git a/docs/Schema/celo/arguments.md b/docs/Schema/celo/arguments.md index 1b8c483..7627c0e 100644 --- a/docs/Schema/celo/arguments.md +++ b/docs/Schema/celo/arguments.md @@ -4,21 +4,6 @@ description: "Query Celo GraphQL arguments data using Bitquery GraphQL API. Get keywords: ["Celo API", "Celo Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. diff --git a/docs/Schema/celo/blocks.md b/docs/Schema/celo/blocks.md index b96a76a..ab95c22 100644 --- a/docs/Schema/celo/blocks.md +++ b/docs/Schema/celo/blocks.md @@ -4,21 +4,6 @@ description: "Query Celo blocks data using Bitquery GraphQL API. Get block heigh keywords: ["Celo API", "Celo Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The `blocks` field allows us to retrieve information about the blocks from the Ethereum blockchain. diff --git a/docs/Schema/celo/coinpath.md b/docs/Schema/celo/coinpath.md index e310b2d..fbea8d0 100644 --- a/docs/Schema/celo/coinpath.md +++ b/docs/Schema/celo/coinpath.md @@ -4,21 +4,6 @@ description: "Query Celo coinpath data using Bitquery GraphQL API. Get fund flow keywords: ["Celo API", "Celo Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology. diff --git a/docs/Schema/celo/dextrades.md b/docs/Schema/celo/dextrades.md index 20e9c16..532757d 100644 --- a/docs/Schema/celo/dextrades.md +++ b/docs/Schema/celo/dextrades.md @@ -4,21 +4,6 @@ description: "Query Celo DEX trades data using Bitquery GraphQL API. Get DEX swa keywords: ["Celo API", "Celo DEX Trades", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. diff --git a/docs/Schema/celo/overview.md b/docs/Schema/celo/overview.md index b9e0489..218652e 100644 --- a/docs/Schema/celo/overview.md +++ b/docs/Schema/celo/overview.md @@ -5,21 +5,6 @@ description: "Access Celo blockchain data through Bitquery's GraphQL API. Query keywords: [Celo API, Celo GraphQL, Celo blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery API offers access to indexed data from the Celo blockchain to enable blockchain data retrieval via GraphQL API for developers. diff --git a/docs/Schema/celo/references.md b/docs/Schema/celo/references.md index 144b001..c06125a 100644 --- a/docs/Schema/celo/references.md +++ b/docs/Schema/celo/references.md @@ -4,21 +4,6 @@ description: "Query Celo schema references data using Bitquery GraphQL API. Get keywords: ["Celo API", "Celo References", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # References
diff --git a/docs/Schema/celo/smartcontractcalls.md b/docs/Schema/celo/smartcontractcalls.md index ab60701..070f699 100644 --- a/docs/Schema/celo/smartcontractcalls.md +++ b/docs/Schema/celo/smartcontractcalls.md @@ -4,21 +4,6 @@ description: "Query Celo smart contract calls data using Bitquery GraphQL API. G keywords: ["Celo API", "Celo Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Calls `smartContractCalls` type allows you to retrieve smart contract calls made to any smart contract on Celo Blockchain. diff --git a/docs/Schema/celo/smartcontractevents.md b/docs/Schema/celo/smartcontractevents.md index 762b93a..2a47b97 100644 --- a/docs/Schema/celo/smartcontractevents.md +++ b/docs/Schema/celo/smartcontractevents.md @@ -4,21 +4,6 @@ description: "Query Celo smart contract events data using Bitquery GraphQL API. keywords: ["Celo API", "Celo Smart Contract Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Events `smartContractEvents` type allows you to retrieve all events emitted by different smart contracts on Ethereum Blockchain. diff --git a/docs/Schema/celo/transactions.md b/docs/Schema/celo/transactions.md index 113f6b9..944d3b3 100644 --- a/docs/Schema/celo/transactions.md +++ b/docs/Schema/celo/transactions.md @@ -4,21 +4,6 @@ description: "Query Celo transactions data using Bitquery GraphQL API. Get trans keywords: ["Celo API", "Celo Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions Celo `Transactions` API allows you to retrieve all the blockchain transactions from Celo Blockchain. diff --git a/docs/Schema/celo/transfers.md b/docs/Schema/celo/transfers.md index e14d186..43aff0d 100644 --- a/docs/Schema/celo/transfers.md +++ b/docs/Schema/celo/transfers.md @@ -4,21 +4,6 @@ description: "Query Celo transfers data using Bitquery GraphQL API. Get asset tr keywords: ["Celo API", "Celo Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers Celo `transfers` API allows you to retrieve currency or token transfers from Celo Blockchain. diff --git a/docs/Schema/conflux/activeaddress.md b/docs/Schema/conflux/activeaddress.md index e887804..7c2a4c8 100644 --- a/docs/Schema/conflux/activeaddress.md +++ b/docs/Schema/conflux/activeaddress.md @@ -4,21 +4,6 @@ description: "Query Conflux active address data using Bitquery GraphQL API. Get keywords: ["Conflux API", "Conflux Active Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Active Address API Conflux Active Address API gives you information on the active addresses on the Conflux chain. The following are the fields on the schema: diff --git a/docs/Schema/conflux/address.md b/docs/Schema/conflux/address.md index c4cf33a..738e4f4 100644 --- a/docs/Schema/conflux/address.md +++ b/docs/Schema/conflux/address.md @@ -4,21 +4,6 @@ description: "Query Conflux address data using Bitquery GraphQL API. Get address keywords: ["Conflux API", "Conflux Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Address API The Address API schema returns information about a wallet. The schema includes the following fields: diff --git a/docs/Schema/conflux/arguments.md b/docs/Schema/conflux/arguments.md index ce0e145..45a7a0c 100644 --- a/docs/Schema/conflux/arguments.md +++ b/docs/Schema/conflux/arguments.md @@ -4,21 +4,6 @@ description: "Query Conflux GraphQL arguments data using Bitquery GraphQL API. G keywords: ["Conflux API", "Conflux Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Arguments API Bitquery's Conflux Arguments API gives you information on the arguments passed during on chain updates to functions. Below are the fields in the schema: diff --git a/docs/Schema/conflux/blocks.md b/docs/Schema/conflux/blocks.md index 5ab479b..0f57b70 100644 --- a/docs/Schema/conflux/blocks.md +++ b/docs/Schema/conflux/blocks.md @@ -4,21 +4,6 @@ description: "Query Conflux blocks data using Bitquery GraphQL API. Get block he keywords: ["Conflux API", "Conflux Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Blocks API Bitquery's Conflux blocks API provides information on blocks in the Conflux chain. Below are the fields in the schema: diff --git a/docs/Schema/conflux/coinpath.md b/docs/Schema/conflux/coinpath.md index 87f79c2..39500b6 100644 --- a/docs/Schema/conflux/coinpath.md +++ b/docs/Schema/conflux/coinpath.md @@ -4,21 +4,6 @@ description: "Query Conflux coinpath data using Bitquery GraphQL API. Get fund f keywords: ["Conflux API", "Conflux Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Coinpath API The Conflux Coinpath API allows you to get the money flow for an address on the Conflux blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. diff --git a/docs/Schema/conflux/overview.md b/docs/Schema/conflux/overview.md index f2a6947..6c4c791 100644 --- a/docs/Schema/conflux/overview.md +++ b/docs/Schema/conflux/overview.md @@ -5,21 +5,6 @@ description: "Access Conflux blockchain data through Bitquery's GraphQL API. Que keywords: [Conflux API, Conflux GraphQL, Conflux blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery provides APIs to access Conflux data. You can get info on the conflux chain which uses the Tree-Graph consensus, a consensus method with parallel-processing to reach distributed consensus. diff --git a/docs/Schema/conflux/smartcontractcalls.md b/docs/Schema/conflux/smartcontractcalls.md index f5b9654..0680db0 100644 --- a/docs/Schema/conflux/smartcontractcalls.md +++ b/docs/Schema/conflux/smartcontractcalls.md @@ -4,21 +4,6 @@ description: "Query Conflux smart contract calls data using Bitquery GraphQL API keywords: ["Conflux API", "Conflux Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Smart Contract Calls API Bitquery's Conflux Calls API captures information on smart contract calls made on chain . Below are the fields in this schema: diff --git a/docs/Schema/conflux/smartcontractevents.md b/docs/Schema/conflux/smartcontractevents.md index ee64834..f8812da 100644 --- a/docs/Schema/conflux/smartcontractevents.md +++ b/docs/Schema/conflux/smartcontractevents.md @@ -4,21 +4,6 @@ description: "Query Conflux smart contract events data using Bitquery GraphQL AP keywords: ["Conflux API", "Conflux Smart Contract Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Smart Contract Events API ``` diff --git a/docs/Schema/conflux/transactions.md b/docs/Schema/conflux/transactions.md index 94867f6..0208b29 100644 --- a/docs/Schema/conflux/transactions.md +++ b/docs/Schema/conflux/transactions.md @@ -4,21 +4,6 @@ description: "Query Conflux transactions data using Bitquery GraphQL API. Get tr keywords: ["Conflux API", "Conflux Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Transactions API ``` diff --git a/docs/Schema/conflux/transfers.md b/docs/Schema/conflux/transfers.md index cc94721..5553133 100644 --- a/docs/Schema/conflux/transfers.md +++ b/docs/Schema/conflux/transfers.md @@ -4,21 +4,6 @@ description: "Query Conflux transfers data using Bitquery GraphQL API. Get asset keywords: ["Conflux API", "Conflux Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Conflux Transfers API Bitquery's conflux transfers API gives you information on the asset transfers on conflux. The following are the fields in the schema: diff --git a/docs/Schema/cosmos/address.md b/docs/Schema/cosmos/address.md index 582fdb3..351dba5 100644 --- a/docs/Schema/cosmos/address.md +++ b/docs/Schema/cosmos/address.md @@ -4,21 +4,6 @@ description: "Query Cosmos address data using Bitquery GraphQL API. Get address keywords: ["Cosmos API", "Cosmos Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` field allows us to retrieve basic information about a particular address or list of address like balance, annotation, etc. diff --git a/docs/Schema/cosmos/attributes.md b/docs/Schema/cosmos/attributes.md index 80aa24d..e873e79 100644 --- a/docs/Schema/cosmos/attributes.md +++ b/docs/Schema/cosmos/attributes.md @@ -4,21 +4,6 @@ description: "Query Cosmos attributes data using Bitquery GraphQL API. Get event keywords: ["Cosmos API", "Cosmos Attributes", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Attributes The `attributes` field allows us to retrieve information about the attributes from cosmos networks. diff --git a/docs/Schema/cosmos/blocks.md b/docs/Schema/cosmos/blocks.md index 61d1817..96da04f 100644 --- a/docs/Schema/cosmos/blocks.md +++ b/docs/Schema/cosmos/blocks.md @@ -4,21 +4,6 @@ description: "Query Cosmos blocks data using Bitquery GraphQL API. Get block hei keywords: ["Cosmos API", "Cosmos Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The `blocks` field allows us to fetch details about the blocks from Cosmos blockchain. diff --git a/docs/Schema/cosmos/coinpath.md b/docs/Schema/cosmos/coinpath.md index 039c058..a34e6cf 100644 --- a/docs/Schema/cosmos/coinpath.md +++ b/docs/Schema/cosmos/coinpath.md @@ -4,21 +4,6 @@ description: "Query Cosmos coinpath data using Bitquery GraphQL API. Get fund fl keywords: ["Cosmos API", "Cosmos Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The coinpath API provides detailed information about the money flow using coinpath technology. diff --git a/docs/Schema/cosmos/messages.md b/docs/Schema/cosmos/messages.md index 7b34ff5..01d5dc4 100644 --- a/docs/Schema/cosmos/messages.md +++ b/docs/Schema/cosmos/messages.md @@ -4,21 +4,6 @@ description: "Query Cosmos messages data using Bitquery GraphQL API. Get chain m keywords: ["Cosmos API", "Cosmos Messages", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Messages The `messages` field allows us to retrieve detaild information about messages from Cosmos blockchain. diff --git a/docs/Schema/cosmos/overview.md b/docs/Schema/cosmos/overview.md index dfbe973..a8ac31e 100644 --- a/docs/Schema/cosmos/overview.md +++ b/docs/Schema/cosmos/overview.md @@ -5,21 +5,6 @@ description: "Access Cosmos blockchain data through Bitquery's GraphQL API. Quer keywords: [Cosmos API, Cosmos GraphQL, Cosmos blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery empowers developers by offering comprehensive access to indexed data from the Cosmos blockchain through our user-friendly and efficient GraphQL API. diff --git a/docs/Schema/cosmos/transactions.md b/docs/Schema/cosmos/transactions.md index 879565d..ba547dd 100644 --- a/docs/Schema/cosmos/transactions.md +++ b/docs/Schema/cosmos/transactions.md @@ -4,21 +4,6 @@ description: "Query Cosmos transactions data using Bitquery GraphQL API. Get tra keywords: ["Cosmos API", "Cosmos Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transaction The Transactions API returns information about transactions on Cosmos network. diff --git a/docs/Schema/cosmos/transfer.md b/docs/Schema/cosmos/transfer.md index d62ebb1..4a5c914 100644 --- a/docs/Schema/cosmos/transfer.md +++ b/docs/Schema/cosmos/transfer.md @@ -4,21 +4,6 @@ description: "Query Cosmos transfer data using Bitquery GraphQL API. Get transfe keywords: ["Cosmos API", "Cosmos Transfer", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The Transfers API returns information about token transfers on Cosmos network. diff --git a/docs/Schema/elrond/address.md b/docs/Schema/elrond/address.md index 1bd6cea..5a65f51 100644 --- a/docs/Schema/elrond/address.md +++ b/docs/Schema/elrond/address.md @@ -4,21 +4,6 @@ description: "Query Elrond address data using Bitquery GraphQL API. Get address keywords: ["Elrond API", "Elrond Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Transaction API Below are the fields in the schema: diff --git a/docs/Schema/elrond/blocks.md b/docs/Schema/elrond/blocks.md index 5d5303a..4280b1b 100644 --- a/docs/Schema/elrond/blocks.md +++ b/docs/Schema/elrond/blocks.md @@ -4,21 +4,6 @@ description: "Query Elrond blocks data using Bitquery GraphQL API. Get block hei keywords: ["Elrond API", "Elrond Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Blocks API The MultiversX Blocks API allows you to query information about blocks on the MultiversX blockchain. You can use this API to get information about the block hash, height, timestamp, and other details.Below are the fields in the schema: diff --git a/docs/Schema/elrond/blockvalidators.md b/docs/Schema/elrond/blockvalidators.md index d0b9947..deb4bc2 100644 --- a/docs/Schema/elrond/blockvalidators.md +++ b/docs/Schema/elrond/blockvalidators.md @@ -4,21 +4,6 @@ description: "Query Elrond validators data using Bitquery GraphQL API. Get valid keywords: ["Elrond API", "Elrond Block Validators", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Block Validators API The MultiversX Block Validators API allows you to query information about the validators of a block on the MultiversX blockchain. A validator is a node that has been elected to participate in the consensus process and produce blocks. The API can be used to get information about the validators of a block, including their addresses, shards, and public key bitmaps. diff --git a/docs/Schema/elrond/callresults.md b/docs/Schema/elrond/callresults.md index aeb65c4..047e7b0 100644 --- a/docs/Schema/elrond/callresults.md +++ b/docs/Schema/elrond/callresults.md @@ -4,21 +4,6 @@ description: "Query Elrond call results data using Bitquery GraphQL API. Get sma keywords: ["Elrond API", "Elrond Call Results", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX CallResults API The MultiversX CallResults API allows you to query information about call results on the MultiversX blockchain. A call result is a record of a function call that was made to a smart contract. The API can be used to get information about the sender, receiver, value, type, and other details of a call result. diff --git a/docs/Schema/elrond/miniblocks.md b/docs/Schema/elrond/miniblocks.md index 63c5217..7c8bea4 100644 --- a/docs/Schema/elrond/miniblocks.md +++ b/docs/Schema/elrond/miniblocks.md @@ -4,21 +4,6 @@ description: "Query Elrond miniblocks data using Bitquery GraphQL API. Get minib keywords: ["Elrond API", "Elrond Miniblocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Miniblocks API MultiversX uses a concept called mini-blocks to handle cross-shard transactions. A mini-block is a small block that contains only cross-shard transactions. These mini-blocks are then aggregated into regular blocks, which are mined on each shard. diff --git a/docs/Schema/elrond/notarizedblocks.md b/docs/Schema/elrond/notarizedblocks.md index 2bf7f60..3e61ebd 100644 --- a/docs/Schema/elrond/notarizedblocks.md +++ b/docs/Schema/elrond/notarizedblocks.md @@ -4,21 +4,6 @@ description: "Query Elrond notarized blocks data using Bitquery GraphQL API. Get keywords: ["Elrond API", "Elrond Notarized Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Notarized Blocks API The MultiversX Notarized Blocks API allows you to query information about notarized blocks on the MultiversX blockchain. A notarized block is a block that has been verified by a set of validators. The API can be used to get information about notarized blocks, including their hashes, epochs, heights, and public key bitmaps. diff --git a/docs/Schema/elrond/operations.md b/docs/Schema/elrond/operations.md index 871c5c6..921d373 100644 --- a/docs/Schema/elrond/operations.md +++ b/docs/Schema/elrond/operations.md @@ -4,21 +4,6 @@ description: "Query Elrond operations data using Bitquery GraphQL API. Get chain keywords: ["Elrond API", "Elrond Operations", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Operations API The MultiversX Operations API allows you to query information about operations on the MultiversX blockchain. You can use this API to get information about the sender, receiver, type, action, and other details of an operation. diff --git a/docs/Schema/elrond/overview.md b/docs/Schema/elrond/overview.md index 8c52d69..a245984 100644 --- a/docs/Schema/elrond/overview.md +++ b/docs/Schema/elrond/overview.md @@ -5,21 +5,6 @@ description: "Access Elrond blockchain data through Bitquery's GraphQL API. Quer keywords: [Elrond API, Elrond GraphQL, Elrond blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview MultiversX API offers access to indexed data from the MultiversX network including shards, block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as shard information, transaction details, events, token transfers, and other relevant information. diff --git a/docs/Schema/elrond/transactions.md b/docs/Schema/elrond/transactions.md index 593af9d..ac5d077 100644 --- a/docs/Schema/elrond/transactions.md +++ b/docs/Schema/elrond/transactions.md @@ -4,21 +4,6 @@ description: "Query Elrond transactions data using Bitquery GraphQL API. Get tra keywords: ["Elrond API", "Elrond Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Transaction API he MultiversX Transactions API allows you to query information about transactions on the MultiversX blockchain. You can use this API to get information about the sender, receiver, amount, currency, and other details of a transaction. diff --git a/docs/Schema/elrond/transfers.md b/docs/Schema/elrond/transfers.md index 0abf038..4809fed 100644 --- a/docs/Schema/elrond/transfers.md +++ b/docs/Schema/elrond/transfers.md @@ -4,21 +4,6 @@ description: "Query Elrond transfers data using Bitquery GraphQL API. Get asset keywords: ["Elrond API", "Elrond Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # MultiversX Transfers API The MultiversX Transfers API gets information about the sender, receiver, amount, currency, and other details related to transfers on the network. Below are the fields in the schema: diff --git a/docs/Schema/eos/addressstats.md b/docs/Schema/eos/addressstats.md index e969d5a..2ecd6e4 100644 --- a/docs/Schema/eos/addressstats.md +++ b/docs/Schema/eos/addressstats.md @@ -4,21 +4,6 @@ description: "Query EOS address stats data using Bitquery GraphQL API. Get aggre keywords: ["EOS API", "EOS Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Address Stats API ``` diff --git a/docs/Schema/eos/blocks.md b/docs/Schema/eos/blocks.md index d6ab0f6..1209614 100644 --- a/docs/Schema/eos/blocks.md +++ b/docs/Schema/eos/blocks.md @@ -4,21 +4,6 @@ description: "Query EOS blocks data using Bitquery GraphQL API. Get block height keywords: ["EOS API", "EOS Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Blocks API Bitquery's EOS blocks API provides information on blocks in the EOS chain. Below are the fields in the schema: diff --git a/docs/Schema/eos/coinpath.md b/docs/Schema/eos/coinpath.md index 2fec986..b96e193 100644 --- a/docs/Schema/eos/coinpath.md +++ b/docs/Schema/eos/coinpath.md @@ -4,21 +4,6 @@ description: "Query EOS coinpath data using Bitquery GraphQL API. Get fund flows keywords: ["EOS API", "EOS Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Coinpath The EOS Coinpath API allows you to get the money flow for an address on the EOS blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. diff --git a/docs/Schema/eos/overview.md b/docs/Schema/eos/overview.md index f7cd9be..cc2995f 100644 --- a/docs/Schema/eos/overview.md +++ b/docs/Schema/eos/overview.md @@ -5,21 +5,6 @@ description: "Access EOS blockchain data through Bitquery's GraphQL API. Query b keywords: [EOS API, EOS GraphQL, EOS blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview EOS is a open-source blockchain network focused on building high-performance blockchain platforms on top of the network. diff --git a/docs/Schema/eos/proposers.md b/docs/Schema/eos/proposers.md index 4a6671a..8970a9b 100644 --- a/docs/Schema/eos/proposers.md +++ b/docs/Schema/eos/proposers.md @@ -4,21 +4,6 @@ description: "Query EOS proposers data using Bitquery GraphQL API. Get block pro keywords: ["EOS API", "EOS Proposers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Producers API ``` diff --git a/docs/Schema/eos/smartcontractcalls.md b/docs/Schema/eos/smartcontractcalls.md index 68fa697..44ae574 100644 --- a/docs/Schema/eos/smartcontractcalls.md +++ b/docs/Schema/eos/smartcontractcalls.md @@ -4,21 +4,6 @@ description: "Query EOS smart contract calls data using Bitquery GraphQL API. Ge keywords: ["EOS API", "EOS Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Smart Contract Calls API According to the official documentation, EOS smart contracts include definition for diff --git a/docs/Schema/eos/transactions.md b/docs/Schema/eos/transactions.md index 7e60880..47608b9 100644 --- a/docs/Schema/eos/transactions.md +++ b/docs/Schema/eos/transactions.md @@ -4,21 +4,6 @@ description: "Query EOS transactions data using Bitquery GraphQL API. Get transa keywords: ["EOS API", "EOS Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Transactions API Bitquery's EOS Transactions API gives you information on cpuUsageUs, status of transaction and, netUsage details. Below are the fields in the schema: diff --git a/docs/Schema/eos/transfers.md b/docs/Schema/eos/transfers.md index 26ff5a6..c6560ab 100644 --- a/docs/Schema/eos/transfers.md +++ b/docs/Schema/eos/transfers.md @@ -4,21 +4,6 @@ description: "Query EOS transfers data using Bitquery GraphQL API. Get asset tra keywords: ["EOS API", "EOS Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # EOS Transfers API Bitquery's EOS transfers API gives you information including sender, receiver, currency details. Below are the fields in the schema: diff --git a/docs/Schema/ethereum/coinpath.md b/docs/Schema/ethereum/coinpath.md index 1ddf9af..558f210 100644 --- a/docs/Schema/ethereum/coinpath.md +++ b/docs/Schema/ethereum/coinpath.md @@ -8,7 +8,7 @@ description: "Retrieve detailed money flow information using the coinpath API. F - + diff --git a/docs/Schema/ethereum/overview.md b/docs/Schema/ethereum/overview.md index 738bcdd..ab5b86a 100644 --- a/docs/Schema/ethereum/overview.md +++ b/docs/Schema/ethereum/overview.md @@ -5,21 +5,6 @@ description: "Access Ethereum blockchain data through Bitquery's GraphQL API. Qu keywords: [Ethereum API, Ethereum GraphQL, Ethereum blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery API offers access to indexed data from the Ethereum blockchain through the ethereum schema. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. diff --git a/docs/Schema/ethereum/transactions.md b/docs/Schema/ethereum/transactions.md index 17cc452..cedab71 100644 --- a/docs/Schema/ethereum/transactions.md +++ b/docs/Schema/ethereum/transactions.md @@ -31,7 +31,7 @@ description: "Explore Ethereum transactions. Get insights into the Ethereum bloc `transactions` type allows you to retrieve all the blockchain transactions from Ethereum Blockchain. -Here's an exmaple query that retrieves 10 latest transactions from Ethereum blockchain: +Here's an example query that retrieves 10 latest transactions from Ethereum blockchain: ``` query { diff --git a/docs/Schema/ethereum2/overview.md b/docs/Schema/ethereum2/overview.md index e4db73b..eec52b5 100644 --- a/docs/Schema/ethereum2/overview.md +++ b/docs/Schema/ethereum2/overview.md @@ -1,25 +1,10 @@ --- sidebar_position: 1 title: "Ethereum Beacon Chain API — Blockchain Data Schema | Bitquery" -description: "Access Ethereum Beacon Chain blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +description: "Access Ethereum Beacon Chain data through Bitquery's GraphQL API. Query attestations, validators, beacon blocks, proposer slashings, and staking data." keywords: [Ethereum Beacon Chain API, Ethereum Beacon Chain GraphQL, Ethereum Beacon Chain blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Ethereum Beacon Chain API Overview Bitquery provides APIs to access Eth2 data. You can get info on the ethereum's staking model. It uses the Proof-of-stake, a consensus method that blockchain networks utilize to reach distributed consensus. diff --git a/docs/Schema/filecoin/address.md b/docs/Schema/filecoin/address.md index bd5578f..33e8361 100644 --- a/docs/Schema/filecoin/address.md +++ b/docs/Schema/filecoin/address.md @@ -4,21 +4,6 @@ description: "Query Filecoin address data using Bitquery GraphQL API. Get addres keywords: ["Filecoin API", "Filecoin Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The Address API allows you to query information about addresses on the Filecoin blockchain. diff --git a/docs/Schema/filecoin/arguments.md b/docs/Schema/filecoin/arguments.md index dc3a1c5..6f35a13 100644 --- a/docs/Schema/filecoin/arguments.md +++ b/docs/Schema/filecoin/arguments.md @@ -4,21 +4,6 @@ description: "Query Filecoin GraphQL arguments data using Bitquery GraphQL API. keywords: ["Filecoin API", "Filecoin Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - ## Related Resources - [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) diff --git a/docs/Schema/filecoin/blocks.md b/docs/Schema/filecoin/blocks.md index 912a611..c15abf5 100644 --- a/docs/Schema/filecoin/blocks.md +++ b/docs/Schema/filecoin/blocks.md @@ -4,21 +4,6 @@ description: "Query Filecoin blocks data using Bitquery GraphQL API. Get block h keywords: ["Filecoin API", "Filecoin Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The Filecoin Blocks API allows you to query information about blocks on the Filecoin blockchain. diff --git a/docs/Schema/filecoin/calls.md b/docs/Schema/filecoin/calls.md index 3185db5..00723d0 100644 --- a/docs/Schema/filecoin/calls.md +++ b/docs/Schema/filecoin/calls.md @@ -4,21 +4,6 @@ description: "Query Filecoin calls data using Bitquery GraphQL API. Get contract keywords: ["Filecoin API", "Filecoin Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Calls In Filecoin, calls are used to invoke methods on actors and transfer FIL. Bitquery's Calls API provides you the following information: diff --git a/docs/Schema/filecoin/messages.md b/docs/Schema/filecoin/messages.md index a2a131d..fb18dcf 100644 --- a/docs/Schema/filecoin/messages.md +++ b/docs/Schema/filecoin/messages.md @@ -4,21 +4,6 @@ description: "Query Filecoin messages data using Bitquery GraphQL API. Get chain keywords: ["Filecoin API", "Filecoin Messages", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Messages According to the [official Filecoin documentation](https://docs.filecoin.io/basics/the-blockchain/blocks-and-tipsets/), diff --git a/docs/Schema/filecoin/overview.md b/docs/Schema/filecoin/overview.md index 53d6bb7..0f841a0 100644 --- a/docs/Schema/filecoin/overview.md +++ b/docs/Schema/filecoin/overview.md @@ -5,22 +5,6 @@ description: "Access Filecoin blockchain data through Bitquery's GraphQL API. Qu keywords: [Filecoin API, Filecoin GraphQL, Filecoin blockchain data, Bitquery] --- - - - - - - - - - - - - - - - - # Overview Filecoin is a network built on top of IPFS that allows you store and retrieve data. It uses proof of storage: a miner’s power in the consensus protocol is proportional to the amount of storage it provides. diff --git a/docs/Schema/filecoin/transfers.md b/docs/Schema/filecoin/transfers.md index 9bea066..9bfa358 100644 --- a/docs/Schema/filecoin/transfers.md +++ b/docs/Schema/filecoin/transfers.md @@ -4,21 +4,6 @@ description: "Query Filecoin transfers data using Bitquery GraphQL API. Get asse keywords: ["Filecoin API", "Filecoin Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The Transfers API allows you to query information about transfers on the Filecoin blockchain. diff --git a/docs/Schema/flow/address.md b/docs/Schema/flow/address.md index dde9d33..e38bd78 100644 --- a/docs/Schema/flow/address.md +++ b/docs/Schema/flow/address.md @@ -4,21 +4,6 @@ description: "Query Flow address data using Bitquery GraphQL API. Get address ba keywords: ["Flow API", "Flow Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The Flow Address API offers basic information about addresses from the Flow Blockchain. diff --git a/docs/Schema/flow/arguments.md b/docs/Schema/flow/arguments.md index 165f552..39d270d 100644 --- a/docs/Schema/flow/arguments.md +++ b/docs/Schema/flow/arguments.md @@ -4,21 +4,6 @@ description: "Query Flow GraphQL arguments data using Bitquery GraphQL API. Get keywords: ["Flow API", "Flow Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The Flow Arguments API provides information about transaction arguments from the flow blockchain which contains the payload and envelope signatures diff --git a/docs/Schema/flow/blockSeals.md b/docs/Schema/flow/blockSeals.md index 1e3307c..6738b43 100644 --- a/docs/Schema/flow/blockSeals.md +++ b/docs/Schema/flow/blockSeals.md @@ -4,21 +4,6 @@ description: "Query Flow block seals data using Bitquery GraphQL API. Get block keywords: ["Flow API", "Flow Block Seals", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Block Seals The Flow Block Seals API provides you information about blocks seal from the Flow Blockchain. A block seal is an attestation that execution result of a specific block has been verified and approved by a quorum of verification nodes. diff --git a/docs/Schema/flow/blocks.md b/docs/Schema/flow/blocks.md index b9f5b85..792f9bc 100644 --- a/docs/Schema/flow/blocks.md +++ b/docs/Schema/flow/blocks.md @@ -4,21 +4,6 @@ description: "Query Flow blocks data using Bitquery GraphQL API. Get block heigh keywords: ["Flow API", "Flow Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The Flow Blocks API provides detailed information about blocks created on the Flow Blockchain. diff --git a/docs/Schema/flow/coinpath.md b/docs/Schema/flow/coinpath.md index 8efd847..bb183cf 100644 --- a/docs/Schema/flow/coinpath.md +++ b/docs/Schema/flow/coinpath.md @@ -4,21 +4,6 @@ description: "Query Flow coinpath data using Bitquery GraphQL API. Get fund flow keywords: ["Flow API", "Flow Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The Tezos Coinpath API provides information about money flow from the Flow Blockchain. diff --git a/docs/Schema/flow/collections.md b/docs/Schema/flow/collections.md index 779a8a6..61e6fc2 100644 --- a/docs/Schema/flow/collections.md +++ b/docs/Schema/flow/collections.md @@ -4,21 +4,6 @@ description: "Query Flow collections data using Bitquery GraphQL API. Get NFT co keywords: ["Flow API", "Flow Collections", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Collections The Flow Collections API provides information about collections from the Flow Blockchain. A collection is batch of transactions that have been includes in a block. diff --git a/docs/Schema/flow/eventFields.md b/docs/Schema/flow/eventFields.md index b8d6215..c6faa0d 100644 --- a/docs/Schema/flow/eventFields.md +++ b/docs/Schema/flow/eventFields.md @@ -4,21 +4,6 @@ description: "Query Flow event fields data using Bitquery GraphQL API. Get event keywords: ["Flow API", "Flow Event Fields", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Event Fields The Flow Event Fields API provides information about events from the Flow Blockchain. diff --git a/docs/Schema/flow/events.md b/docs/Schema/flow/events.md index 51837ed..65eb1c2 100644 --- a/docs/Schema/flow/events.md +++ b/docs/Schema/flow/events.md @@ -4,21 +4,6 @@ description: "Query Flow events data using Bitquery GraphQL API. Get on-chain ev keywords: ["Flow API", "Flow Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Events The Flow Events API provides information about events emiited on the Flow Blockchain. diff --git a/docs/Schema/flow/inputs.md b/docs/Schema/flow/inputs.md index 165b712..31224b3 100644 --- a/docs/Schema/flow/inputs.md +++ b/docs/Schema/flow/inputs.md @@ -4,21 +4,6 @@ description: "Query Flow inputs data using Bitquery GraphQL API. Get transaction keywords: ["Flow API", "Flow Inputs", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Inputs The Flow Inputs API provides information about transaction inputs from the Flow Blockchain. diff --git a/docs/Schema/flow/outputs.md b/docs/Schema/flow/outputs.md index ffb6262..c951a8b 100644 --- a/docs/Schema/flow/outputs.md +++ b/docs/Schema/flow/outputs.md @@ -4,21 +4,6 @@ description: "Query Flow outputs data using Bitquery GraphQL API. Get transactio keywords: ["Flow API", "Flow Outputs", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Outputs The Flow Outputs API provides information about the transaction outputs from the Flow Blockchain. diff --git a/docs/Schema/flow/overview.md b/docs/Schema/flow/overview.md index ba5134a..8e8dbb7 100644 --- a/docs/Schema/flow/overview.md +++ b/docs/Schema/flow/overview.md @@ -1,40 +1,25 @@ ---- -sidebar_position: 1 -title: "Flow API — Blockchain Data Schema | Bitquery" -description: "Access Flow blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." -keywords: [Flow API, Flow GraphQL, Flow blockchain data, Bitquery] ---- - - - - - - - - - - - - - - - - -# Overview - -Flow is a layer 1 blockchain for creating and trading non-fungible tokens (NFTs), decentralized applications (dApps), and games. -![flow explorer](/img/flow.png) - - -:::info - -Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. - -::: - -## Related Resources - -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) -- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) +--- +sidebar_position: 1 +title: "Flow API — Blockchain Data Schema | Bitquery" +description: "Access Flow blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, and more." +keywords: [Flow API, Flow GraphQL, Flow blockchain data, Bitquery] +--- + +# Overview + +Flow is a layer 1 blockchain for creating and trading non-fungible tokens (NFTs), decentralized applications (dApps), and games. +![flow explorer](/img/flow.png) + + +:::info + +Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access Token, Read _[our guide](/docs/graphql-ide/how-to-start/)_ on getting started. + +::: + +## Related Resources + +- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/flow/transactionAuthorizers.md b/docs/Schema/flow/transactionAuthorizers.md index 783188f..75764c0 100644 --- a/docs/Schema/flow/transactionAuthorizers.md +++ b/docs/Schema/flow/transactionAuthorizers.md @@ -4,21 +4,6 @@ description: "Query Flow authorizers data using Bitquery GraphQL API. Get author keywords: ["Flow API", "Flow Transaction Authorizers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transaction Authorizers The Flow Transaction Authorizers API provides information about transaction authorizers from the Flow Blcockhain. diff --git a/docs/Schema/flow/transactionEnvelopeSignatures.md b/docs/Schema/flow/transactionEnvelopeSignatures.md index bf8f74f..59388a3 100644 --- a/docs/Schema/flow/transactionEnvelopeSignatures.md +++ b/docs/Schema/flow/transactionEnvelopeSignatures.md @@ -4,21 +4,6 @@ description: "Query Flow signatures data using Bitquery GraphQL API. Get envelop keywords: ["Flow API", "Flow Transaction Envelope Signatures", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transaction Envelope Signatures The Flow Transaction Envelope Signatures API provides details about envelope signatures of transaction from the Flow Blockchain. diff --git a/docs/Schema/flow/transactionPayloadSignatures.md b/docs/Schema/flow/transactionPayloadSignatures.md index 7b28845..1cbd488 100644 --- a/docs/Schema/flow/transactionPayloadSignatures.md +++ b/docs/Schema/flow/transactionPayloadSignatures.md @@ -4,21 +4,6 @@ description: "Query Flow signatures data using Bitquery GraphQL API. Get payload keywords: ["Flow API", "Flow Transaction Payload Signatures", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transaction Payload Signatures The Flow Transaction Payload Signatures API provides information about payload signatures of transaction from the Flow Blockchain. diff --git a/docs/Schema/flow/transactions.md b/docs/Schema/flow/transactions.md index 4eaeef7..c269175 100644 --- a/docs/Schema/flow/transactions.md +++ b/docs/Schema/flow/transactions.md @@ -4,21 +4,6 @@ description: "Query Flow transactions data using Bitquery GraphQL API. Get trans keywords: ["Flow API", "Flow Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Flow Transaction API provides information about transactions from the Flow Blockchain. diff --git a/docs/Schema/harmony/arguments.md b/docs/Schema/harmony/arguments.md index 36fec5c..2ae1532 100644 --- a/docs/Schema/harmony/arguments.md +++ b/docs/Schema/harmony/arguments.md @@ -4,21 +4,6 @@ description: "Query Harmony GraphQL arguments data using Bitquery GraphQL API. G keywords: ["Harmony API", "Harmony Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The Harmony Arguments API provides information about arguments of smart contract calls and events. diff --git a/docs/Schema/harmony/blocks.md b/docs/Schema/harmony/blocks.md index 3f8e017..454a9f4 100644 --- a/docs/Schema/harmony/blocks.md +++ b/docs/Schema/harmony/blocks.md @@ -4,21 +4,6 @@ description: "Query Harmony blocks data using Bitquery GraphQL API. Get block he keywords: ["Harmony API", "Harmony Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The Harmony Blocks API provides information about blocks from the Harmony Blockchain. diff --git a/docs/Schema/harmony/overview.md b/docs/Schema/harmony/overview.md index e69de29..664eab9 100644 --- a/docs/Schema/harmony/overview.md +++ b/docs/Schema/harmony/overview.md @@ -0,0 +1,9 @@ +--- +sidebar_position: 1 +title: "Harmony API — Blockchain Data Schema | Bitquery" +description: "Access Harmony blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, smart contracts, staking transactions, and more." +--- + +# Overview + +Bitquery indexes Harmony blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, smart contract calls and events, staking transactions, and related fields. diff --git a/docs/Schema/harmony/smartContractCalls.md b/docs/Schema/harmony/smartContractCalls.md index 616fcf9..047acff 100644 --- a/docs/Schema/harmony/smartContractCalls.md +++ b/docs/Schema/harmony/smartContractCalls.md @@ -4,21 +4,6 @@ description: "Query Harmony smart contract calls data using Bitquery GraphQL API keywords: ["Harmony API", "Harmony Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Calls The Harmony Smart Contract Calls API provides detailed information about smart contract calls made on the Harmony Blockchain. diff --git a/docs/Schema/harmony/smartContractEvents.md b/docs/Schema/harmony/smartContractEvents.md index a275f9b..fbf1f9a 100644 --- a/docs/Schema/harmony/smartContractEvents.md +++ b/docs/Schema/harmony/smartContractEvents.md @@ -4,21 +4,6 @@ description: "Query Harmony smart contract events data using Bitquery GraphQL AP keywords: ["Harmony API", "Harmony Smart Contract Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Events The Harmony Smart Contract Events API provides information about events emiited from smart contract on the Harmony Blockchain. diff --git a/docs/Schema/harmony/stakingTransactions.md b/docs/Schema/harmony/stakingTransactions.md index 16b646f..e5ab1b9 100644 --- a/docs/Schema/harmony/stakingTransactions.md +++ b/docs/Schema/harmony/stakingTransactions.md @@ -4,21 +4,6 @@ description: "Query Harmony staking data using Bitquery GraphQL API. Get staking keywords: ["Harmony API", "Harmony Staking Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Staking Transactions The Harmony Staking Transaction API provides details about staking transactions from the Harmony blockchain. diff --git a/docs/Schema/harmony/transactions.md b/docs/Schema/harmony/transactions.md index cb503c8..0fe0254 100644 --- a/docs/Schema/harmony/transactions.md +++ b/docs/Schema/harmony/transactions.md @@ -4,21 +4,6 @@ description: "Query Harmony transactions data using Bitquery GraphQL API. Get tr keywords: ["Harmony API", "Harmony Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Harmony Transactions API provides information about transaction form the Harmony blockchain. diff --git a/docs/Schema/harmony/transfers.md b/docs/Schema/harmony/transfers.md index 827f012..4be36c2 100644 --- a/docs/Schema/harmony/transfers.md +++ b/docs/Schema/harmony/transfers.md @@ -4,21 +4,6 @@ description: "Query Harmony transfers data using Bitquery GraphQL API. Get asset keywords: ["Harmony API", "Harmony Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The Harmony Transfers API provides information about token transfers from the Harmony Blockchain. diff --git a/docs/Schema/hedera/address.md b/docs/Schema/hedera/address.md index e810178..3470c8f 100644 --- a/docs/Schema/hedera/address.md +++ b/docs/Schema/hedera/address.md @@ -4,21 +4,6 @@ description: "Query Hedera address data using Bitquery GraphQL API. Get address keywords: ["Hedera API", "Hedera Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The Address API provides basic information about addresses on the Hedera Blockchain. It offers information about various aspects, including the balance of the native currency associated with the address, any available annotations, and more. diff --git a/docs/Schema/hedera/arguments.md b/docs/Schema/hedera/arguments.md index aff092c..f848f01 100644 --- a/docs/Schema/hedera/arguments.md +++ b/docs/Schema/hedera/arguments.md @@ -4,21 +4,6 @@ description: "Query Hedera GraphQL arguments data using Bitquery GraphQL API. Ge keywords: ["Hedera API", "Hedera Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The Arguments API provides you with information about event arguments. It offers valuable information about various aspects, such as the specific values of event arguments, their corresponding types, and even the transaction where the event originally occurred. diff --git a/docs/Schema/hedera/calls.md b/docs/Schema/hedera/calls.md index cbefbd2..159a24c 100644 --- a/docs/Schema/hedera/calls.md +++ b/docs/Schema/hedera/calls.md @@ -4,21 +4,6 @@ description: "Query Hedera calls data using Bitquery GraphQL API. Get contract o keywords: ["Hedera API", "Hedera Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Calls The Calls API provides you with information about calls made on Hedera Blockchain. It offers information about various aspects, such as call inputs, result of the calls, and much more. diff --git a/docs/Schema/hedera/coinpath.md b/docs/Schema/hedera/coinpath.md index 0ab3b94..91c01d6 100644 --- a/docs/Schema/hedera/coinpath.md +++ b/docs/Schema/hedera/coinpath.md @@ -4,21 +4,6 @@ description: "Query Hedera coinpath data using Bitquery GraphQL API. Get fund fl keywords: ["Hedera API", "Hedera Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The Coinpath API offers information related to the flow of funds on the Hedera Blockchain. diff --git a/docs/Schema/hedera/inputs.md b/docs/Schema/hedera/inputs.md index d65d9f0..7bc1288 100644 --- a/docs/Schema/hedera/inputs.md +++ b/docs/Schema/hedera/inputs.md @@ -4,21 +4,6 @@ description: "Query Hedera inputs data using Bitquery GraphQL API. Get transacti keywords: ["Hedera API", "Hedera Inputs", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Inputs The Inputs API provides information about transaction inputs on the Hedera Blockchain. diff --git a/docs/Schema/hedera/messages.md b/docs/Schema/hedera/messages.md index abfcd4c..7232907 100644 --- a/docs/Schema/hedera/messages.md +++ b/docs/Schema/hedera/messages.md @@ -4,21 +4,6 @@ description: "Query Hedera messages data using Bitquery GraphQL API. Get chain m keywords: ["Hedera API", "Hedera Messages", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Messages The Messages API provides information about blockchain messages on the Hedera Blockchain. diff --git a/docs/Schema/hedera/outputs.md b/docs/Schema/hedera/outputs.md index 185c552..7cad040 100644 --- a/docs/Schema/hedera/outputs.md +++ b/docs/Schema/hedera/outputs.md @@ -4,21 +4,6 @@ description: "Query Hedera outputs data using Bitquery GraphQL API. Get transact keywords: ["Hedera API", "Hedera Outputs", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Outputs The Outputs API provides information about transaction outputs on the Hedera Blockchain. diff --git a/docs/Schema/hedera/overview.md b/docs/Schema/hedera/overview.md index d3f77c3..7bc2ed9 100644 --- a/docs/Schema/hedera/overview.md +++ b/docs/Schema/hedera/overview.md @@ -5,21 +5,6 @@ description: "Access Hedera blockchain data through Bitquery's GraphQL API. Quer keywords: [Hedera API, Hedera GraphQL, Hedera blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Our API makes it easy to access different types of data from the Hedera blockchain, like addresses, arguments, calls, and more. diff --git a/docs/Schema/hedera/transactions.md b/docs/Schema/hedera/transactions.md index 18e0cf4..2e6c01d 100644 --- a/docs/Schema/hedera/transactions.md +++ b/docs/Schema/hedera/transactions.md @@ -4,21 +4,6 @@ description: "Query Hedera transactions data using Bitquery GraphQL API. Get tra keywords: ["Hedera API", "Hedera Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Transactions API offers insights into transactions on the Hedera Blockchain. diff --git a/docs/Schema/ripple/overview.md b/docs/Schema/ripple/overview.md index 40a9730..c4d28a7 100644 --- a/docs/Schema/ripple/overview.md +++ b/docs/Schema/ripple/overview.md @@ -5,21 +5,6 @@ description: "Access Ripple blockchain data through Bitquery's GraphQL API. Quer keywords: [Ripple API, Ripple GraphQL, Ripple blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery's Ripple APIs give you information on the XRP's blocks, transactions, addresses, offers, payments and so on. diff --git a/docs/Schema/solana/address.md b/docs/Schema/solana/address.md index be4617c..457ac32 100644 --- a/docs/Schema/solana/address.md +++ b/docs/Schema/solana/address.md @@ -4,21 +4,6 @@ description: "Query Solana address data using Bitquery GraphQL API. Get address keywords: ["Solana API", "Solana Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The Solana address API gives you information of the balance of a wallet in SOL. diff --git a/docs/Schema/solana/blockRewards.md b/docs/Schema/solana/blockRewards.md index 63df2c0..e5cfa1a 100644 --- a/docs/Schema/solana/blockRewards.md +++ b/docs/Schema/solana/blockRewards.md @@ -4,21 +4,6 @@ description: "Query Solana block rewards data using Bitquery GraphQL API. Get bl keywords: ["Solana API", "Solana Block Rewards", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Block Rewards The BlockRewards API returns information about rewards on the Solana network. Solana implements a proof of stake reward scheme for validator nodes. Rewards are paid every epoch. diff --git a/docs/Schema/solana/blocks.md b/docs/Schema/solana/blocks.md index 7c1611e..aa25599 100644 --- a/docs/Schema/solana/blocks.md +++ b/docs/Schema/solana/blocks.md @@ -4,21 +4,6 @@ description: "Query Solana blocks data using Bitquery GraphQL API. Get block hei keywords: ["Solana API", "Solana Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The Blocks API returns information about blocks on the Solana network. The fields in the schema include: diff --git a/docs/Schema/solana/coinpath.md b/docs/Schema/solana/coinpath.md index 8953548..4b32259 100644 --- a/docs/Schema/solana/coinpath.md +++ b/docs/Schema/solana/coinpath.md @@ -4,21 +4,6 @@ description: "Query Solana coinpath data using Bitquery GraphQL API. Get fund fl keywords: ["Solana API", "Solana Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The Solana Coinpath API allows you to get the money flow for an address on the Solana blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. diff --git a/docs/Schema/solana/instructionAccounts.md b/docs/Schema/solana/instructionAccounts.md index ee66e06..a1e45cb 100644 --- a/docs/Schema/solana/instructionAccounts.md +++ b/docs/Schema/solana/instructionAccounts.md @@ -4,21 +4,6 @@ description: "Query Solana instruction accounts data using Bitquery GraphQL API. keywords: ["Solana API", "Solana Instruction Accounts", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # InstructionAccounts This API returns information about the accounts involved in an instruction. An instruction is the smallest execution logic on Solana. One transaction can have 1 or more instructions. Below are the fields in the API: diff --git a/docs/Schema/solana/instructions.md b/docs/Schema/solana/instructions.md index bbc5fee..845ba7a 100644 --- a/docs/Schema/solana/instructions.md +++ b/docs/Schema/solana/instructions.md @@ -4,21 +4,6 @@ description: "Query Solana instructions data using Bitquery GraphQL API. Get pro keywords: ["Solana API", "Solana Instructions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Instructions The Solana instructions API allows you to query information about instructions that have been executed on the Solana blockchain. This information includes the program that executed the instruction, the accounts that were affected by the instruction, the data that was passed to the instruction, and the log message that was produced by the instruction. The schema includes the following fields: diff --git a/docs/Schema/solana/overview.md b/docs/Schema/solana/overview.md index 2aa07fd..05d9db0 100644 --- a/docs/Schema/solana/overview.md +++ b/docs/Schema/solana/overview.md @@ -5,21 +5,6 @@ description: "Access Solana blockchain data through Bitquery's GraphQL API. Quer keywords: [Solana API, Solana GraphQL, Solana blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery API offers access to indexed data from the Solana blockchain. This schema is specifically designed to enable blockchain data retrieval via GraphQL API for developers. diff --git a/docs/Schema/solana/transactions.md b/docs/Schema/solana/transactions.md index c1c2d05..c18dda5 100644 --- a/docs/Schema/solana/transactions.md +++ b/docs/Schema/solana/transactions.md @@ -4,21 +4,6 @@ description: "Query Solana transactions data using Bitquery GraphQL API. Get tra keywords: ["Solana API", "Solana Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Solana transactions API allows you to query for transactions on the Solana blockchain. You can use this API to get information about specific transactions, such as the signature, block, transaction fee, success, fee payer, inner instructions count, instructions count, signer, and transaction index. diff --git a/docs/Schema/solana/transfers.md b/docs/Schema/solana/transfers.md index 2a2d9da..9e2e341 100644 --- a/docs/Schema/solana/transfers.md +++ b/docs/Schema/solana/transfers.md @@ -4,21 +4,6 @@ description: "Query Solana transfers data using Bitquery GraphQL API. Get asset keywords: ["Solana API", "Solana Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The transfers API allows you to get a information on transfers that have occurred on the Solana blockchain.Below are the fields in the schema: diff --git a/docs/Schema/stellar/address.md b/docs/Schema/stellar/address.md index a031329..bc2f929 100644 --- a/docs/Schema/stellar/address.md +++ b/docs/Schema/stellar/address.md @@ -4,21 +4,6 @@ description: "Query Stellar address data using Bitquery GraphQL API. Get address keywords: ["Stellar API", "Stellar Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address Stellar Address API helps you get information on Address balance in the network. Below are the fields in the API: diff --git a/docs/Schema/stellar/addressStats.md b/docs/Schema/stellar/addressStats.md index 779c039..8e6e8e1 100644 --- a/docs/Schema/stellar/addressStats.md +++ b/docs/Schema/stellar/addressStats.md @@ -4,21 +4,6 @@ description: "Query Stellar address stats data using Bitquery GraphQL API. Get a keywords: ["Stellar API", "Stellar Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # AddressStats Stellar AddressStats API helps you get information on Addresses in the network. Below are the fields in the API: diff --git a/docs/Schema/stellar/balanceEffects.md b/docs/Schema/stellar/balanceEffects.md index 9407fdc..67041d4 100644 --- a/docs/Schema/stellar/balanceEffects.md +++ b/docs/Schema/stellar/balanceEffects.md @@ -4,21 +4,6 @@ description: "Query Stellar balance effects data using Bitquery GraphQL API. Get keywords: ["Stellar API", "Stellar Balance Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # BalanceEffects The Stellar BalanceEffects API allows you to get information about the balance changes of an account.Below are the fields in the API: diff --git a/docs/Schema/stellar/blocks.md b/docs/Schema/stellar/blocks.md index c39a209..ee7c5fd 100644 --- a/docs/Schema/stellar/blocks.md +++ b/docs/Schema/stellar/blocks.md @@ -4,21 +4,6 @@ description: "Query Stellar blocks data using Bitquery GraphQL API. Get block he keywords: ["Stellar API", "Stellar Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks Stellar Blocks API helps you get information on Blocks in the network. Below are the fields in the API: diff --git a/docs/Schema/stellar/claimableBalanceEffects.md b/docs/Schema/stellar/claimableBalanceEffects.md index f7ac87b..8dea61b 100644 --- a/docs/Schema/stellar/claimableBalanceEffects.md +++ b/docs/Schema/stellar/claimableBalanceEffects.md @@ -4,21 +4,6 @@ description: "Query Stellar claimable balance data using Bitquery GraphQL API. G keywords: ["Stellar API", "Stellar Claimable Balance Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Claimable BalanceEffects Claimable balance allows stellar wallets to send payments in parts.The claimable balance is recorded on the Stellar ledger. Read more [here](https://developers.stellar.org/docs/encyclopedia/claimable-balances) diff --git a/docs/Schema/stellar/coinpath.md b/docs/Schema/stellar/coinpath.md index 10e3f97..a83d343 100644 --- a/docs/Schema/stellar/coinpath.md +++ b/docs/Schema/stellar/coinpath.md @@ -4,21 +4,6 @@ description: "Query Stellar coinpath data using Bitquery GraphQL API. Get fund f keywords: ["Stellar API", "Stellar Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The Coinpath API allows you to get the money flow for an address on the Stellar blockchain. You can track any levels of fund movement with this API. This is a very useful API for crypto investigations. diff --git a/docs/Schema/stellar/effectArguments.md b/docs/Schema/stellar/effectArguments.md index 52f0fa8..24208cd 100644 --- a/docs/Schema/stellar/effectArguments.md +++ b/docs/Schema/stellar/effectArguments.md @@ -4,21 +4,6 @@ description: "Query Stellar effect arguments data using Bitquery GraphQL API. Ge keywords: ["Stellar API", "Stellar Effect Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Effects Arguments
Filtering Transfers
diff --git a/docs/Schema/stellar/effects.md b/docs/Schema/stellar/effects.md index f2f3ade..80b502c 100644 --- a/docs/Schema/stellar/effects.md +++ b/docs/Schema/stellar/effects.md @@ -4,21 +4,6 @@ description: "Query Stellar effects data using Bitquery GraphQL API. Get ledger keywords: ["Stellar API", "Stellar Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Effects According to the Stellar documentation, diff --git a/docs/Schema/stellar/liquidityPoolEffects.md b/docs/Schema/stellar/liquidityPoolEffects.md index 0ad6f5b..01e8177 100644 --- a/docs/Schema/stellar/liquidityPoolEffects.md +++ b/docs/Schema/stellar/liquidityPoolEffects.md @@ -4,21 +4,6 @@ description: "Query Stellar liquidity pool effects data using Bitquery GraphQL A keywords: ["Stellar API", "Stellar Liquidity Pool Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Liquidity PoolEffects Liquidity pools on Stellar support AMMs. Bitquery's LiquidityPoolEffects API gives you effects information regarding liquidity pools. The following are the fields in the schema: diff --git a/docs/Schema/stellar/liquidityPoolTradeEffects.md b/docs/Schema/stellar/liquidityPoolTradeEffects.md index 2a2a19a..a713c37 100644 --- a/docs/Schema/stellar/liquidityPoolTradeEffects.md +++ b/docs/Schema/stellar/liquidityPoolTradeEffects.md @@ -4,21 +4,6 @@ description: "Query Stellar liquidity pool data using Bitquery GraphQL API. Get keywords: ["Stellar API", "Stellar Liquidity Pool Trade Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Liquidity Pool Trade Effects Liquidity pools on Stellar support AMMs. Bitquery's Liquidity TradePoolEffects API gives you trade effects information regarding liquidity pools. The following are the fields in the schema: diff --git a/docs/Schema/stellar/operations.md b/docs/Schema/stellar/operations.md index 207000e..6a87d8f 100644 --- a/docs/Schema/stellar/operations.md +++ b/docs/Schema/stellar/operations.md @@ -4,21 +4,6 @@ description: "Query Stellar operations data using Bitquery GraphQL API. Get chai keywords: ["Stellar API", "Stellar Operations", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Operations An operation is a command that tells the Stellar network to do something, such as send money, or create an account. A transaction is a group of operations that are submitted to the Stellar network together. diff --git a/docs/Schema/stellar/overview.md b/docs/Schema/stellar/overview.md index 10171cc..d00d928 100644 --- a/docs/Schema/stellar/overview.md +++ b/docs/Schema/stellar/overview.md @@ -5,21 +5,6 @@ description: "Access Stellar blockchain data through Bitquery's GraphQL API. Que keywords: [Stellar API, Stellar GraphQL, Stellar blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery's Stellar APIs give you information on the network's blocks, transactions, addresses, operations, payments and so on. diff --git a/docs/Schema/stellar/payments.md b/docs/Schema/stellar/payments.md index ffec85c..1d6a49a 100644 --- a/docs/Schema/stellar/payments.md +++ b/docs/Schema/stellar/payments.md @@ -4,21 +4,6 @@ description: "Query Stellar payments data using Bitquery GraphQL API. Get paymen keywords: ["Stellar API", "Stellar Payments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Payments Stellar network is optimized for payments. Bitquery's Payments API will give you information on payments on the XRP ledger. Below are the fields in the schema: diff --git a/docs/Schema/stellar/tradeEffects.md b/docs/Schema/stellar/tradeEffects.md index 3e6a410..7936452 100644 --- a/docs/Schema/stellar/tradeEffects.md +++ b/docs/Schema/stellar/tradeEffects.md @@ -4,21 +4,6 @@ description: "Query Stellar trade effects data using Bitquery GraphQL API. Get t keywords: ["Stellar API", "Stellar Trade Effects", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Trade Effects When an offer is fully or partially fulfilled, a trade happens. Trade Effects capture the effects wrt trades. Below are the fields in the schema: diff --git a/docs/Schema/stellar/transactions.md b/docs/Schema/stellar/transactions.md index ca52a92..4659ef7 100644 --- a/docs/Schema/stellar/transactions.md +++ b/docs/Schema/stellar/transactions.md @@ -4,21 +4,6 @@ description: "Query Stellar transactions data using Bitquery GraphQL API. Get tr keywords: ["Stellar API", "Stellar Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions > Transactions comprise a bundle of between 1-100 operations and are diff --git a/docs/Schema/stellar/transfers.md b/docs/Schema/stellar/transfers.md index aeb5a4c..cc01d65 100644 --- a/docs/Schema/stellar/transfers.md +++ b/docs/Schema/stellar/transfers.md @@ -4,21 +4,6 @@ description: "Query Stellar transfers data using Bitquery GraphQL API. Get asset keywords: ["Stellar API", "Stellar Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers Bitquery's Stellar transfers API provides you the following information: diff --git a/docs/Schema/tezos/address.md b/docs/Schema/tezos/address.md index 5209ee1..b9671c5 100644 --- a/docs/Schema/tezos/address.md +++ b/docs/Schema/tezos/address.md @@ -4,21 +4,6 @@ description: "Query Tezos address data using Bitquery GraphQL API. Get address b keywords: ["Tezos API", "Tezos Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` API allows you to retrieve detailed information about addresses from the Tezos blockchain. diff --git a/docs/Schema/tezos/arguments.md b/docs/Schema/tezos/arguments.md index d034224..d8de141 100644 --- a/docs/Schema/tezos/arguments.md +++ b/docs/Schema/tezos/arguments.md @@ -4,21 +4,6 @@ description: "Query Tezos GraphQL arguments data using Bitquery GraphQL API. Get keywords: ["Tezos API", "Tezos Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The Arguments API provides you with information about arguments. diff --git a/docs/Schema/tezos/balanceUpdates.md b/docs/Schema/tezos/balanceUpdates.md index f25ae90..d1a94e5 100644 --- a/docs/Schema/tezos/balanceUpdates.md +++ b/docs/Schema/tezos/balanceUpdates.md @@ -4,21 +4,6 @@ description: "Query Tezos balance updates data using Bitquery GraphQL API. Get b keywords: ["Tezos API", "Tezos Balance Updates", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Balance Updates The balanceUpdates API allows you to retrieve information about balance updates for a specific address. diff --git a/docs/Schema/tezos/blocks.md b/docs/Schema/tezos/blocks.md index d2900af..9bea3d7 100644 --- a/docs/Schema/tezos/blocks.md +++ b/docs/Schema/tezos/blocks.md @@ -4,21 +4,6 @@ description: "Query Tezos blocks data using Bitquery GraphQL API. Get block heig keywords: ["Tezos API", "Tezos Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The Blocks API provides information about the blocks created on the Tezos blockchain. diff --git a/docs/Schema/tezos/coinpath.md b/docs/Schema/tezos/coinpath.md index 3751b4b..25b1964 100644 --- a/docs/Schema/tezos/coinpath.md +++ b/docs/Schema/tezos/coinpath.md @@ -4,21 +4,6 @@ description: "Query Tezos coinpath data using Bitquery GraphQL API. Get fund flo keywords: ["Tezos API", "Tezos Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The Coinpath API provides information about the movement of funds within the Tezos Blockchain. diff --git a/docs/Schema/tezos/operations.md b/docs/Schema/tezos/operations.md index 3b6ce29..c17b684 100644 --- a/docs/Schema/tezos/operations.md +++ b/docs/Schema/tezos/operations.md @@ -4,21 +4,6 @@ description: "Query Tezos operations data using Bitquery GraphQL API. Get chain keywords: ["Tezos API", "Tezos Operations", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Operations The Tezos Operations API provides information about operations from the Tezos Blockchain. diff --git a/docs/Schema/tezos/overview.md b/docs/Schema/tezos/overview.md index e69de29..9960106 100644 --- a/docs/Schema/tezos/overview.md +++ b/docs/Schema/tezos/overview.md @@ -0,0 +1,9 @@ +--- +sidebar_position: 1 +title: "Tezos API — Blockchain Data Schema | Bitquery" +description: "Access Tezos (XTZ) blockchain data through Bitquery's GraphQL API. Query blocks, transactions, transfers, operations, balances, and coin path analytics." +--- + +# Overview + +Bitquery indexes Tezos blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, operations, address balances, coin path, and related fields. diff --git a/docs/Schema/tezos/transactions.md b/docs/Schema/tezos/transactions.md index a59f6d6..3b5a91f 100644 --- a/docs/Schema/tezos/transactions.md +++ b/docs/Schema/tezos/transactions.md @@ -4,21 +4,6 @@ description: "Query Tezos transactions data using Bitquery GraphQL API. Get tran keywords: ["Tezos API", "Tezos Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions The Tezos Transactions API allows you to retrieve information about transactions on the Tezos blockchain. diff --git a/docs/Schema/tezos/transfers.md b/docs/Schema/tezos/transfers.md index f367dd4..99f92e7 100644 --- a/docs/Schema/tezos/transfers.md +++ b/docs/Schema/tezos/transfers.md @@ -4,21 +4,6 @@ description: "Query Tezos transfers data using Bitquery GraphQL API. Get asset t keywords: ["Tezos API", "Tezos Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers The Tezos Transfers API provides information about the transfers on the Tezos Blockchain. diff --git a/docs/Schema/tron/overview.md b/docs/Schema/tron/overview.md index 5d656bc..72af998 100644 --- a/docs/Schema/tron/overview.md +++ b/docs/Schema/tron/overview.md @@ -5,21 +5,6 @@ description: "Access Tron blockchain data through Bitquery's GraphQL API. Query keywords: [Tron API, Tron GraphQL, Tron blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Tron API Overview Bitquery's Tron API offers access to indexed data from the Tron network including shards, block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as shard information, transaction details, events, token transfers, and other relevant information. diff --git a/docs/Schema/velas/activeaddresses.md b/docs/Schema/velas/activeaddresses.md index f97a3a5..6d3d1af 100644 --- a/docs/Schema/velas/activeaddresses.md +++ b/docs/Schema/velas/activeaddresses.md @@ -4,21 +4,6 @@ description: "Query Velas active addresses data using Bitquery GraphQL API. Get keywords: ["Velas API", "Velas Active Addresses", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Active Addresses The `activeAddresses` field allows us to retrieve details about the active addresses from the velas blockchain. diff --git a/docs/Schema/velas/address.md b/docs/Schema/velas/address.md index ca5a908..a323e8a 100644 --- a/docs/Schema/velas/address.md +++ b/docs/Schema/velas/address.md @@ -4,21 +4,6 @@ description: "Query Velas address data using Bitquery GraphQL API. Get address b keywords: ["Velas API", "Velas Address", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address The `address` allows us to retrieve information about a specific address. diff --git a/docs/Schema/velas/addresstats.md b/docs/Schema/velas/addresstats.md index 3d4e664..b9d31d3 100644 --- a/docs/Schema/velas/addresstats.md +++ b/docs/Schema/velas/addresstats.md @@ -4,21 +4,6 @@ description: "Query Velas address stats data using Bitquery GraphQL API. Get agg keywords: ["Velas API", "Velas Address Stats", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Address Stats The `addressstats` field allows us to retrieves statistics related to blockchain addresses. diff --git a/docs/Schema/velas/arguments.md b/docs/Schema/velas/arguments.md index 5a7fe87..67aa0e7 100644 --- a/docs/Schema/velas/arguments.md +++ b/docs/Schema/velas/arguments.md @@ -4,21 +4,6 @@ description: "Query Velas GraphQL arguments data using Bitquery GraphQL API. Get keywords: ["Velas API", "Velas Arguments", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Arguments The `arguments` field allows us to fetch information about arguments of smart contract calls and evetns. diff --git a/docs/Schema/velas/blocks.md b/docs/Schema/velas/blocks.md index 42f8bd6..40c492a 100644 --- a/docs/Schema/velas/blocks.md +++ b/docs/Schema/velas/blocks.md @@ -4,21 +4,6 @@ description: "Query Velas blocks data using Bitquery GraphQL API. Get block heig keywords: ["Velas API", "Velas Blocks", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Blocks The `blocks` field allows us to retrieve information about the blocks from the velas blockchain. diff --git a/docs/Schema/velas/coinpath.md b/docs/Schema/velas/coinpath.md index a23856a..21d0937 100644 --- a/docs/Schema/velas/coinpath.md +++ b/docs/Schema/velas/coinpath.md @@ -4,21 +4,6 @@ description: "Query Velas coinpath data using Bitquery GraphQL API. Get fund flo keywords: ["Velas API", "Velas Coinpath", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Coinpath The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology. diff --git a/docs/Schema/velas/dextrades.md b/docs/Schema/velas/dextrades.md index 26b2950..bac724b 100644 --- a/docs/Schema/velas/dextrades.md +++ b/docs/Schema/velas/dextrades.md @@ -4,21 +4,6 @@ description: "Query Velas DEX trades data using Bitquery GraphQL API. Get DEX sw keywords: ["Velas API", "Velas DEX Trades", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # DEX Trades The `dexTrades` field allows us to retrieve dex trade data from Ethereum blockchain. diff --git a/docs/Schema/velas/overview.md b/docs/Schema/velas/overview.md index c3a4fd9..be24e38 100644 --- a/docs/Schema/velas/overview.md +++ b/docs/Schema/velas/overview.md @@ -5,21 +5,6 @@ description: "Access Velas blockchain data through Bitquery's GraphQL API. Query keywords: [Velas API, Velas GraphQL, Velas blockchain data, Bitquery] --- - - - - - - - - - - - - - - - # Overview Bitquery Velas API offers access to indexed data from the velas blockchain via GraphQL API for developers. diff --git a/docs/Schema/velas/references.md b/docs/Schema/velas/references.md index f07bd3b..9023926 100644 --- a/docs/Schema/velas/references.md +++ b/docs/Schema/velas/references.md @@ -4,21 +4,6 @@ description: "Query Velas schema references data using Bitquery GraphQL API. Get keywords: ["Velas API", "Velas References", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # References
diff --git a/docs/Schema/velas/smartcontractcalls.md b/docs/Schema/velas/smartcontractcalls.md index 89ee014..a6c48ad 100644 --- a/docs/Schema/velas/smartcontractcalls.md +++ b/docs/Schema/velas/smartcontractcalls.md @@ -4,21 +4,6 @@ description: "Query Velas smart contract calls data using Bitquery GraphQL API. keywords: ["Velas API", "Velas Smart Contract Calls", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Calls `smartContractCalls` type allows you to retrieve smart contract calls made to any smart contract on velas Blockchain. diff --git a/docs/Schema/velas/smartcontractevents.md b/docs/Schema/velas/smartcontractevents.md index 340a186..c261f0c 100644 --- a/docs/Schema/velas/smartcontractevents.md +++ b/docs/Schema/velas/smartcontractevents.md @@ -4,21 +4,6 @@ description: "Query Velas smart contract events data using Bitquery GraphQL API. keywords: ["Velas API", "Velas Smart Contract Events", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Smart Contract Events `smartContractEvents` type allows you to retrieve all events emitted by different smart contracts on velas Blockchain. diff --git a/docs/Schema/velas/transactions.md b/docs/Schema/velas/transactions.md index 80964cb..25069ec 100644 --- a/docs/Schema/velas/transactions.md +++ b/docs/Schema/velas/transactions.md @@ -4,21 +4,6 @@ description: "Query Velas transactions data using Bitquery GraphQL API. Get tran keywords: ["Velas API", "Velas Transactions", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transactions Bitquery `transactions` API allows you to retrieve all the blockchain transactions from velas Blockchain. diff --git a/docs/Schema/velas/transfers.md b/docs/Schema/velas/transfers.md index 29f4274..95077f6 100644 --- a/docs/Schema/velas/transfers.md +++ b/docs/Schema/velas/transfers.md @@ -4,21 +4,6 @@ description: "Query Velas transfers data using Bitquery GraphQL API. Get asset t keywords: ["Velas API", "Velas Transfers", "Bitquery", "GraphQL"] --- - - - - - - - - - - - - - - - # Transfers Bitquery `transfers` API allows you to retrieve currency or token transfers from velas Blockchain. diff --git a/docs/Use-Cases/crypto-ml-price-prediction.md b/docs/Use-Cases/crypto-ml-price-prediction.md index 21112ec..bd77bca 100644 --- a/docs/Use-Cases/crypto-ml-price-prediction.md +++ b/docs/Use-Cases/crypto-ml-price-prediction.md @@ -5,21 +5,6 @@ description: "Learn how to fetch historical DEX trading data with GraphQL from t keywords: [machine learning, cryptocurrency, GraphQL, Bitquery API, DEX, Python] --- - - - - - - - - - - - - - - - # Building an ML Model With Crypto Price Data Cryptocurrency markets are known for their volatility, making them a fascinating domain for data science and predictive modeling. In this tutorial, we'll explore how to use GraphQL to retrieve historical trading data and use machine learning with Python to build a simple cryptocurrency price prediction model. @@ -240,5 +225,5 @@ Thus, we have built an ML model with blockchain data using BitQuery DEX API to f - [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) - [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Use-Cases/multi-chain-portfolio-tracker.md b/docs/Use-Cases/multi-chain-portfolio-tracker.md index b162bc2..87b7abe 100644 --- a/docs/Use-Cases/multi-chain-portfolio-tracker.md +++ b/docs/Use-Cases/multi-chain-portfolio-tracker.md @@ -1,6 +1,18 @@ --- sidebar_position: 4 -description: In this tutorial, we'll see how to build a multi-chain portfolio tracker. +title: "Multi-Chain EVM Portfolio Tracker with Streamlit & Bitquery — Tutorial" +description: "Build a Streamlit dashboard that fetches wallet token balances and USD values across Ethereum, BSC, Polygon, Avalanche, and other EVM chains using the Bitquery GraphQL API." +keywords: + [ + Streamlit, + portfolio tracker, + multi-chain, + EVM, + Bitquery API, + wallet balances, + GraphQL, + cross-chain, + ] --- # How to Build Multichain Portfolio Tracker @@ -250,3 +262,11 @@ Once the user runs the script, Streamlit will launch a local web server, and the ![](/img/multichain_portfolio.gif) That's it! You've successfully built a Multichain EVM DeFi Portfolio Tracker using Streamlit and the Bitquery API. Feel free to customize the dashboard further to suit your needs or add additional features as per your requirements. + +## Related Resources + +- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) +- [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) diff --git a/docs/Use-Cases/react-example.md b/docs/Use-Cases/react-example.md index 99c8022..fb3d62f 100644 --- a/docs/Use-Cases/react-example.md +++ b/docs/Use-Cases/react-example.md @@ -5,21 +5,6 @@ description: "Build a React app that shows top DEX gainers and losers using hook keywords: [React, GraphQL, Bitquery API, DEX, Ethereum, JavaScript] --- - - - - - - - - - - - - - - - # Using Bitquery APIs with ReactJS to get Top Gainers and Losers Below is a step-by-step tutorial on how to create a React application that displays the top gainers and losers on a particular date using React hooks, async/await for fetching data, and Bitquery V1 APIs for price information. diff --git a/docs/Use-Cases/tradingview.md b/docs/Use-Cases/tradingview.md index 5e3d12c..595cafa 100644 --- a/docs/Use-Cases/tradingview.md +++ b/docs/Use-Cases/tradingview.md @@ -5,21 +5,6 @@ description: "Build candlestick charts for DEX token data using Bitquery GraphQL keywords: [TradingView, Lightweight Charts, Bitquery API, DEX, Ethereum, React, blockchain charts] --- - - - - - - - - - - - - - - - # Build a tradingview chart app for blockchain data This tutorial will help you build a TradingView chart app with blockchain data from Bitquery. diff --git a/docs/Use-Cases/wordpress-wpgetapi.md b/docs/Use-Cases/wordpress-wpgetapi.md index cc98dc7..f497119 100644 --- a/docs/Use-Cases/wordpress-wpgetapi.md +++ b/docs/Use-Cases/wordpress-wpgetapi.md @@ -5,21 +5,6 @@ description: "Connect WordPress to the Bitquery GraphQL endpoint with the WPGetA keywords: [WordPress, WPGetAPI, Bitquery API, GraphQL, blockchain, DEX] --- - - - - - - - - - - - - - - - # Step-by-step guide on using the Bitquery API with WPGetAPI on WordPress **Prerequisites:** @@ -137,5 +122,5 @@ Finally set - [Bitquery documentation home](https://docs.bitquery.io/v1/docs/intro) - [How to start with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/building-queries/FAQ.md b/docs/building-queries/FAQ.md index a27adc4..df0e536 100644 --- a/docs/building-queries/FAQ.md +++ b/docs/building-queries/FAQ.md @@ -4,21 +4,6 @@ description: "Answers to common Bitquery API questions: DEX maker/taker, transfe keywords: [Bitquery, FAQ, GraphQL API, DEX, token price, market cap] --- - - - - - - - - - - - - - - - # Glossary and Frequently Asked Questions ## What is a maker and taker in a DEX Trade? @@ -208,4 +193,4 @@ Note: In many cases token attributes shown as null in those cases you should fin - [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) - [Expressions overview](https://docs.bitquery.io/v1/docs/query-features/expressions/overview) - [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) diff --git a/docs/building-queries/basic-structure-of-a-query.md b/docs/building-queries/basic-structure-of-a-query.md index 2e7bff8..acc264e 100644 --- a/docs/building-queries/basic-structure-of-a-query.md +++ b/docs/building-queries/basic-structure-of-a-query.md @@ -5,24 +5,9 @@ description: "Learn how Bitquery models blockchain data as cubes with dimensions keywords: [Bitquery, GraphQL, cube, dimensions, metrics, query architecture] --- - - - - - - - - - - - - - - - # Basic Structure of A Query -Bitquery Architechture +Bitquery Architecture Let’s understand how we built our infrastructure to enable scalable analytical processing. In the simplest form, we are using Clickhouse (An OLAP database) at our data warehouse and built a GraphQL layer on top of it, and glued them together using a library called Activecube, which we have written from scratch and open-sourced. This library transforms GraphQL queries to Clickhouse queries. ![under the hood](/img/under-the-hood.jpeg) diff --git a/docs/building-queries/network-selection.md b/docs/building-queries/network-selection.md index 0fb7abb..1890c92 100644 --- a/docs/building-queries/network-selection.md +++ b/docs/building-queries/network-selection.md @@ -5,21 +5,6 @@ description: "Learn how to select blockchain networks in Bitquery API requests a keywords: [Bitquery, GraphQL, network selection, blockchain API, IDE] --- - - - - - - - - - - - - - - - # Network Selection When using Bitquery APIs, you can specify the network that you want to query. This is done by setting the network parameter in the request. diff --git a/docs/graphql-ide/account.md b/docs/graphql-ide/account.md index 60864c6..8b1beb1 100644 --- a/docs/graphql-ide/account.md +++ b/docs/graphql-ide/account.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Your Account Dashboard Account dashboard gives you details related to your account like your subscriptions plan, API usage, frequently used queries etc. Let's epxlore each section on the page. diff --git a/docs/graphql-ide/apikey.md b/docs/graphql-ide/apikey.md index 3ba8d4a..21f21d2 100644 --- a/docs/graphql-ide/apikey.md +++ b/docs/graphql-ide/apikey.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Getting the Access Token Update: We now use Access Token for both V1 and V2 APIs. You can access the token [here](https://account.bitquery.io/user/api_v2/access_tokens). diff --git a/docs/graphql-ide/errors.md b/docs/graphql-ide/errors.md index 5849bba..a08642a 100644 --- a/docs/graphql-ide/errors.md +++ b/docs/graphql-ide/errors.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Common Errors and What to Do This section will guide you through the interpretation of common error messages encountered within Bitquery APIs. It will help you decide when to escalate issues by filing a ticket at [Bitquery Support](https://support.bitquery.io/). diff --git a/docs/graphql-ide/how-to-start.md b/docs/graphql-ide/how-to-start.md index a74044e..f3559dd 100644 --- a/docs/graphql-ide/how-to-start.md +++ b/docs/graphql-ide/how-to-start.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Running your First Query Create and run your first query on Bitquery IDE by visiting [https://ide.bitquery.io/](https://ide.bitquery.io/). diff --git a/docs/graphql-ide/ide.md b/docs/graphql-ide/ide.md index ae48260..ac2e323 100644 --- a/docs/graphql-ide/ide.md +++ b/docs/graphql-ide/ide.md @@ -13,21 +13,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # How to use the IDE ? ## What is Bitquery IDE? diff --git a/docs/graphql-ide/points.md b/docs/graphql-ide/points.md index d147d85..cb4118e 100644 --- a/docs/graphql-ide/points.md +++ b/docs/graphql-ide/points.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # What are Points? At Bitquery we use points system to calculate the cost for a query. Each query will use different number of points, based on the complexity and size of the query requested. For a comprehensive understanding of the points system, please refer to [our detailed post](https://community.bitquery.io/t/introducing-points/874). diff --git a/docs/graphql-ide/query-builder.md b/docs/graphql-ide/query-builder.md index a9176e5..255c4d7 100644 --- a/docs/graphql-ide/query-builder.md +++ b/docs/graphql-ide/query-builder.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Query Builder ## What is Query Builder? @@ -59,4 +44,4 @@ Simplify your query creation process and access the data you need from various b - [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Supported blockchains](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) - [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) diff --git a/docs/graphql-ide/supported-blockchains.md b/docs/graphql-ide/supported-blockchains.md index a0f6355..7d6c9c6 100644 --- a/docs/graphql-ide/supported-blockchains.md +++ b/docs/graphql-ide/supported-blockchains.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Supported Blockchains and System Status Bitquery supports 40+ blockchains, including EVM-based blockchains like Ethereum, BSC, Polygon, along with other blockchains like Solana, Cosmos, and many more. Here is a list of the blockchains we support: @@ -50,5 +35,5 @@ To check the status of each blockchain service, you can visit the following link - [V1 vs V2 APIs — coverage and features](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) - [Network selection in queries](https://docs.bitquery.io/v1/docs/building-queries/network-selection) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/graphql-ide/use-it-in-your-application.md b/docs/graphql-ide/use-it-in-your-application.md index 2ed6cda..5043d38 100644 --- a/docs/graphql-ide/use-it-in-your-application.md +++ b/docs/graphql-ide/use-it-in-your-application.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Use it in Your Application You can write any API and use it any application built on any language.To get the code, simply write your query and on the right side, you will see a `````` symbol. diff --git a/docs/graphql-ide/v1-and-v2.md b/docs/graphql-ide/v1-and-v2.md index e9f3437..8c4fcca 100644 --- a/docs/graphql-ide/v1-and-v2.md +++ b/docs/graphql-ide/v1-and-v2.md @@ -12,21 +12,6 @@ keywords: ] --- - - - - - - - - - - - - - - - # Difference between Bitquery GraphQL V1 and V2 APIs Today we will explain the difference between our V1 and V2 APIs. Let’s start with naming; we call our V2 APIs as Streaming APIs. Additionally, there is also a difference in the endpoint. diff --git a/docs/intro.md b/docs/intro.md index a45cb35..375877c 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -13,24 +13,9 @@ keywords: ] --- - - - - - - - - - - - - - - - # Overview -Bitquery 's infrastructure provides you access to historical and real-time blockchain data through various interfaces such as GraphQL APIs. In this documentation +Bitquery's infrastructure provides you access to historical and real-time blockchain data through various interfaces such as GraphQL APIs. In this documentation we will show you how to get blockchain data from 40+ chains via graphQL. @@ -59,4 +44,4 @@ We highly encourage you to dig into our docs first; however, you can contact us - [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) - [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) diff --git a/docs/query-features/Metrics.md b/docs/query-features/Metrics.md index edaa948..514d17c 100644 --- a/docs/query-features/Metrics.md +++ b/docs/query-features/Metrics.md @@ -5,21 +5,6 @@ description: "Use the IDE metrics API and utilities metrics to inspect query cos keywords: [Bitquery, metrics, API usage, query cost, GraphQL] --- - - - - - - - - - - - - - - - # Metrics The IDE Builder provides a metrics API that you can use to get details on your usage. diff --git a/docs/query-features/aggregation/aggregation.md b/docs/query-features/aggregation/aggregation.md index db6c9d5..c17f7f3 100644 --- a/docs/query-features/aggregation/aggregation.md +++ b/docs/query-features/aggregation/aggregation.md @@ -5,21 +5,6 @@ description: "Group and aggregate blockchain data with sum, count, average, maxi keywords: [Bitquery, GraphQL, aggregation, calculate, sum, count] --- - - - - - - - - - - - - - - - # Aggregation in V1 Aggregation is a way to group data and calculate aggregate values. The API supports a variety of aggregation functions, including `sum`, `count`, `average`, `maximum`, and `minimum`. diff --git a/docs/query-features/aggregation/count.md b/docs/query-features/aggregation/count.md index 8b233d2..fca3491 100644 --- a/docs/query-features/aggregation/count.md +++ b/docs/query-features/aggregation/count.md @@ -5,21 +5,6 @@ description: "Use count and countBigInt in Bitquery queries for transactions, ev keywords: [Bitquery, GraphQL, count, countBigInt, aggregation] --- - - - - - - - - - - - - - - - # Count diff --git a/docs/query-features/aggregation/sum.md b/docs/query-features/aggregation/sum.md index 44be075..8ecab8b 100644 --- a/docs/query-features/aggregation/sum.md +++ b/docs/query-features/aggregation/sum.md @@ -5,21 +5,6 @@ description: "Calculate total amounts with sum and conditional criteria for tran keywords: [Bitquery, GraphQL, sum, aggregation, transfers, USD] --- - - - - - - - - - - - - - - - # Sum @@ -78,4 +63,4 @@ By mention the address as a sender or receiver we are calculating: - [Count aggregation](https://docs.bitquery.io/v1/docs/query-features/aggregation/count) - [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) - [Coinpath explained — overview](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) \ No newline at end of file +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) \ No newline at end of file diff --git a/docs/query-features/aliases.md b/docs/query-features/aliases.md index 5515a2b..8046532 100644 --- a/docs/query-features/aliases.md +++ b/docs/query-features/aliases.md @@ -5,21 +5,6 @@ description: "Rename GraphQL response fields with aliases in Bitquery queries fo keywords: [Bitquery, GraphQL, aliases, field renaming, DEX] --- - - - - - - - - - - - - - - - # Aliases diff --git a/docs/query-features/arguments/EVM_arguments.md b/docs/query-features/arguments/EVM_arguments.md index 363b980..49c0f08 100644 --- a/docs/query-features/arguments/EVM_arguments.md +++ b/docs/query-features/arguments/EVM_arguments.md @@ -5,21 +5,6 @@ description: "Query transaction and event arguments on Ethereum and EVM chains w keywords: [Bitquery, GraphQL, EVM, arguments, smart contract events] --- - - - - - - - - - - - - - - - # EVM Arguments You can use the `arguments` method with EVM chains to get arguments and values of transactions, trades and calls. diff --git a/docs/query-features/arguments/Other_Chains_arguments.md b/docs/query-features/arguments/Other_Chains_arguments.md index baf3e95..d9a8df3 100644 --- a/docs/query-features/arguments/Other_Chains_arguments.md +++ b/docs/query-features/arguments/Other_Chains_arguments.md @@ -5,21 +5,6 @@ description: "Examples of the arguments API on non-EVM chains including Algorand keywords: [Bitquery, GraphQL, arguments, Algorand, Hedera] --- - - - - - - - - - - - - - - - # Using Arguments on Other Chains Using arguments in other chains varies from one to another. @@ -97,5 +82,5 @@ query MyQuery { - [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) - [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) - [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) - [Introduction](https://docs.bitquery.io/v1/docs/intro) \ No newline at end of file diff --git a/docs/query-features/arguments/argument.md b/docs/query-features/arguments/argument.md index af0c73a..293414c 100644 --- a/docs/query-features/arguments/argument.md +++ b/docs/query-features/arguments/argument.md @@ -5,21 +5,6 @@ description: "Overview of the arguments query for smart contract method and even keywords: [Bitquery, GraphQL, arguments, smart contract, EVM] --- - - - - - - - - - - - - - - - # Arguments The arguments query method returns the arguments of a transaction or smart contract call. Currently arguments are supported on EVM, Algorand, Everscale, Conflux, Harmony, Hedera and Flow. diff --git a/docs/query-features/expressions/overview.md b/docs/query-features/expressions/overview.md index aa6e046..0d255d5 100644 --- a/docs/query-features/expressions/overview.md +++ b/docs/query-features/expressions/overview.md @@ -5,21 +5,6 @@ description: "Define custom calculated fields with expression() in Bitquery V1 G keywords: [Bitquery, GraphQL, expressions, expression(), calculated fields] --- - - - - - - - - - - - - - - - # Expressions **What is an Expression?** diff --git a/docs/query-features/filtering/fields.md b/docs/query-features/filtering/fields.md index c28d83a..65fe854 100644 --- a/docs/query-features/filtering/fields.md +++ b/docs/query-features/filtering/fields.md @@ -5,21 +5,6 @@ description: "Use method filters, date, time, uniq counts, and field combination keywords: [Bitquery, GraphQL, filters, fields, uniq, transactions] --- - - - - - - - - - - - - - - - # Fields Each method for every API will have different set of fields as filters. For example, the blocks method will have the following fields as filters: diff --git a/docs/query-features/filtering/limits.md b/docs/query-features/filtering/limits.md index 00d1097..6345e12 100644 --- a/docs/query-features/filtering/limits.md +++ b/docs/query-features/filtering/limits.md @@ -5,21 +5,6 @@ description: "Control result size with limit and limitBy options in Bitquery Gra keywords: [Bitquery, GraphQL, limit, limitBy, pagination] --- - - - - - - - - - - - - - - - # Limits You can limit of the number of results retrieved using the `limit` or `limitby` filter both of which work differently. diff --git a/docs/query-features/filtering/options.md b/docs/query-features/filtering/options.md index 6e853fa..5bc8390 100644 --- a/docs/query-features/filtering/options.md +++ b/docs/query-features/filtering/options.md @@ -5,21 +5,6 @@ description: "Combine limit, offset, ascending and descending sort in the option keywords: [Bitquery, GraphQL, options, limit, offset, sorting] --- - - - - - - - - - - - - - - - # Options The options filter contains most of the sorting and result limiting features as shown in the screenshot. diff --git a/docs/query-features/filtering/sorting.md b/docs/query-features/filtering/sorting.md index 7a11ab1..d22ce09 100644 --- a/docs/query-features/filtering/sorting.md +++ b/docs/query-features/filtering/sorting.md @@ -5,21 +5,6 @@ description: "Sort API results with asc, desc, and descByInteger options in Bitq keywords: [Bitquery, GraphQL, sorting, asc, desc, options] --- - - - - - - - - - - - - - - - # Sorting You can sort the results in ascending or descending order using two filters. diff --git a/docs/query-features/fragments/overview.md b/docs/query-features/fragments/overview.md index 746e7de..af31a5d 100644 --- a/docs/query-features/fragments/overview.md +++ b/docs/query-features/fragments/overview.md @@ -5,21 +5,6 @@ description: "Reuse query fragments for balance history and other patterns to re keywords: [Bitquery, GraphQL, fragments, reuse, queries] --- - - - - - - - - - - - - - - - # Fragments A fragment spread is a way to reuse a fragment definition in another fragment or query. This can be useful for reducing code duplication and making your queries more readable. diff --git a/docs/query-features/search/search.md b/docs/query-features/search/search.md index f838cda..1ac2b89 100644 --- a/docs/query-features/search/search.md +++ b/docs/query-features/search/search.md @@ -5,21 +5,6 @@ description: "Search addresses, tokens, and hashes across chains with the Bitque keywords: [Bitquery, GraphQL, search, address, multi-chain] --- - - - - - - - - - - - - - - - # Search The Search method allows you to identify the type of object that was found and the network that it belongs to by typing a string. You can for example type an address and to check which network the address belongs. Each result also has a `subject` field, which has a `__typename` subfield which tells you the type of the object found ( e.g. `Address`). diff --git a/docs/query-features/utilities/utilities.md b/docs/query-features/utilities/utilities.md index b5a5d4c..7a0d3a7 100644 --- a/docs/query-features/utilities/utilities.md +++ b/docs/query-features/utilities/utilities.md @@ -5,21 +5,6 @@ description: "Check account billing, points, and API usage metrics with the Bitq keywords: [Bitquery, GraphQL, utilities, API usage, billing, metrics] --- - - - - - - - - - - - - - - - # Utilities Utilities method helps understand your API consumption. It provides information on your account, such as your active period, billing day, and points remaining. It also provides metrics on your API usage, such as the number of SQL requests you have made and the cost of those requests. From c66c58772814bff021022bd7b16de20307f2ade0 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 22:07:01 +0530 Subject: [PATCH 04/14] Add redirect for Bitcoin examples hub casing mismatch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit File path is Examples/bitcoin/ but slug is /examples/Bitcoin. createRedirects handles /docs/Examples/bitcoin/index → /docs/examples/Bitcoin so old bookmarks and external links to the wrong-cased path still work. Made-with: Cursor --- docusaurus.config.js | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docusaurus.config.js b/docusaurus.config.js index 9e9c4fe..10ea52d 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -92,6 +92,15 @@ const config = { from: "/docs/category/Bitcoin", }, ], + // On case-sensitive hosts, also redirect /docs/Examples/bitcoin → /docs/examples/Bitcoin. + // Can't be a static redirect here (macOS build is case-insensitive); handle in nginx if needed. + createRedirects(existingPath) { + // Bitcoin hub: slug /examples/Bitcoin differs from file path Examples/bitcoin + if (existingPath === "/docs/examples/Bitcoin") { + return ["/docs/Examples/bitcoin/index"]; + } + return undefined; + }, }, ], ], From cca6fc29c59bd91f82dbde23bdce338ae4378857 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 22:20:04 +0530 Subject: [PATCH 05/14] Improve query headings across 67 Example pages for SEO MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Added chain names to generic headings (e.g. "Get Balance" → "Get Ethereum Address Balance") - Made headings specific to actual query content (checked query code for context) - Fixed grammar issues ("All transfers of a address", "Most Transfered") - Covers: bitcoin, Solana, Dogecoin, stellar, cosmos, algorand, ripple, tron, hedera, filecoin, dexTrades, Transactions, Staking, Beacon Chain, cross-chain, smartcontract calls/events, address, transfers, tokens, Input_Output Made-with: Cursor --- .../Beacon Chain Examples/eth2_examples.md | 8 ++--- docs/Examples/Dogecoin/get-latest-price.md | 2 ++ docs/Examples/Dogecoin/inflow-outflow.md | 2 ++ docs/Examples/Input_Output/IO_examples.md | 2 +- docs/Examples/Solana/address-api.md | 4 +-- docs/Examples/Solana/instructions.md | 6 ++-- docs/Examples/Solana/transactions-api.md | 4 +-- docs/Examples/Solana/transfers.md | 32 ++++++++--------- docs/Examples/Staking/stake_examples.md | 4 +-- .../Examples/Transactions/input-output-api.md | 2 +- docs/Examples/Transactions/transaction-api.md | 14 ++++---- docs/Examples/Transfers/transfer-api.md | 24 ++++++------- .../blockchain-active-addresses-api.md | 4 +-- .../Blockchain-Address-API-Examples.md | 18 +++++----- docs/Examples/address/specific-queries.md | 2 +- .../addressStats/address-stats-api.md | 2 ++ docs/Examples/algorand/address.md | 6 ++-- docs/Examples/algorand/blocks.md | 4 +-- docs/Examples/algorand/coinpath.md | 4 +-- docs/Examples/algorand/smartContractCalls.mdx | 8 ++--- docs/Examples/algorand/transactions.mdx | 12 +++---- docs/Examples/algorand/transfers.mdx | 4 +-- docs/Examples/bitcoin/Bitcoin-Blocks-API.md | 4 +-- docs/Examples/bitcoin/Bitcoin-Coinpath-API.md | 6 ++-- .../bitcoin/Bitcoin-Transaction-API.md | 6 ++-- docs/Examples/bitcoin/bitcoin-address-api.md | 10 +++--- docs/Examples/bitcoin/bitcoin-fee-api.md | 4 +-- docs/Examples/bitcoin/index.md | 14 ++++---- docs/Examples/cosmos/address.md | 8 ++--- docs/Examples/cosmos/attributes.md | 6 ++-- docs/Examples/cosmos/blocks.md | 6 ++-- docs/Examples/cosmos/coinpath.md | 6 ++-- docs/Examples/cosmos/messages.md | 6 ++-- docs/Examples/cosmos/transactions.md | 4 +-- docs/Examples/cosmos/transfers.md | 4 +-- docs/Examples/cross-chain/cross-chain-api.md | 24 ++++++------- docs/Examples/dexTrades/dex-pool-api.md | 2 +- .../dexTrades/dex-trading-data-api.md | 36 +++++++++---------- docs/Examples/dexTrades/ohlc.md | 4 +-- docs/Examples/filecoin/messages.md | 10 +++--- docs/Examples/hedera/hedera-address.md | 2 +- docs/Examples/hedera/hedera-io.md | 6 ++-- docs/Examples/hedera/hedera-messages.md | 2 +- docs/Examples/hedera/hedera-transactions.md | 8 ++--- docs/Examples/ripple/balances.mdx | 2 +- docs/Examples/ripple/nft_token_offers.md | 2 +- docs/Examples/ripple/payments.mdx | 4 +-- docs/Examples/ripple/trades.mdx | 2 +- docs/Examples/ripple/transfers.mdx | 6 ++-- .../smart-contract-calls-api.md | 14 ++++---- .../smart-contract-events-api.md | 10 +++--- docs/Examples/stellar/stellar-address-api.md | 2 +- docs/Examples/stellar/stellar-effects-api.md | 4 +-- .../stellar/stellar-liquiditypool-api.md | 4 +-- docs/Examples/stellar/stellar-payments-api.md | 2 +- .../stellar/stellar-tradeeffects-api.md | 4 +-- .../stellar/stellar-transactions-api.md | 4 +-- docs/Examples/tokens/token-api.md | 34 +++++++++--------- docs/Examples/tron/address.md | 8 ++--- docs/Examples/tron/arguments.md | 6 ++-- docs/Examples/tron/blocks.md | 6 ++-- docs/Examples/tron/coinpath.md | 4 +-- docs/Examples/tron/dexTrades.md | 4 +-- docs/Examples/tron/smartContractCalls.md | 6 ++-- docs/Examples/tron/smartContractEvents.md | 6 ++-- docs/Examples/tron/transaction.md | 4 +-- docs/Examples/tron/transfers.md | 8 ++--- 67 files changed, 249 insertions(+), 243 deletions(-) diff --git a/docs/Examples/Beacon Chain Examples/eth2_examples.md b/docs/Examples/Beacon Chain Examples/eth2_examples.md index 6114907..4498e04 100644 --- a/docs/Examples/Beacon Chain Examples/eth2_examples.md +++ b/docs/Examples/Beacon Chain Examples/eth2_examples.md @@ -9,7 +9,7 @@ sidebar_position: 1 Our ETH2 APIs provides extensive data on Beacon Chain. Let's look at some of the examples. -### Get Historical Validator Statuses +### Get Daily Ethereum Beacon Chain Validator Status Counts You can get the daily stats of validator statuses (active_exiting, active_ongoing, active_slashed, pending_queued and so on) using the below query. Access it on the [IDE](https://ide.bitquery.io/Validator-Counts-Daily-For-all-status) @@ -28,7 +28,7 @@ query MyQuery { ``` -### ETH2 Deposits +### List Largest Ethereum Beacon Chain Validator Deposits by Amount In ETH2, the validators are decided based on the amount they stake. The below example, gets top validators based on the amount deposited. @@ -81,7 +81,7 @@ This query returns: - The maximum date (end) on which the validator made a deposit. -### ETH2 Validator token unlock +### Track Ethereum Beacon Chain Validator Balance Changes Over Time The below returns a list of validator updates for a given validator index `$index`, sorted by ascending date. Each validator update includes the date of the update, the change in validator balance, and the maximum validator balance after the update. @@ -115,7 +115,7 @@ query ($network: Ethereum2Network!, $dateFormat: String!, $index: Int!, $from: I ``` -### Beacon Chain Attestor Slashings +### List Ethereum Beacon Chain Attester Slashings for a Validator Index The below query returns a list of attester slashings for a given validator index `$index`, sorted by ascending date. Each attester slashing includes the date of the slashing, the parent root hash, the ETH1 deposit count, the ETH1 deposit root hash, the ETH1 block hash, the state root hash, and the validator's public key and index. diff --git a/docs/Examples/Dogecoin/get-latest-price.md b/docs/Examples/Dogecoin/get-latest-price.md index 7822ef6..9b0fa5f 100644 --- a/docs/Examples/Dogecoin/get-latest-price.md +++ b/docs/Examples/Dogecoin/get-latest-price.md @@ -6,6 +6,8 @@ keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] # Get Latest Price of Doge Coin in USD +## Query Latest Dogecoin USD Price from Recent On-Chain Inputs + Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/dogecoin-price-in-use_1) query, we can get the latest price of Doge Coin in `USD`. ```graphql diff --git a/docs/Examples/Dogecoin/inflow-outflow.md b/docs/Examples/Dogecoin/inflow-outflow.md index 5437135..cc2b79f 100644 --- a/docs/Examples/Dogecoin/inflow-outflow.md +++ b/docs/Examples/Dogecoin/inflow-outflow.md @@ -6,6 +6,8 @@ keywords: [Dogecoin API examples, Dogecoin GraphQL queries, Bitquery] # Tranfers of an Address on DogeCoin Network +## Dogecoin Address Inbound and Outbound Coinpath Depth and Amounts + Doge Coin is one of the most famous meme coin in the cryptocurrency space. Using [this](https://ide.bitquery.io/zFB1y4MP5B) query, we can get the transfers of Doge Coin to a particular address. ```graphql diff --git a/docs/Examples/Input_Output/IO_examples.md b/docs/Examples/Input_Output/IO_examples.md index 84f58ff..3952d37 100644 --- a/docs/Examples/Input_Output/IO_examples.md +++ b/docs/Examples/Input_Output/IO_examples.md @@ -6,7 +6,7 @@ keywords: [inputs outputs API examples, GraphQL queries, Bitquery] # Inputs and Outputs -## Getting Spend Volume of a Token +## Aggregate FlowToken Daily Volumes from Flow Inputs and Outputs ``` query MyQuery { diff --git a/docs/Examples/Solana/address-api.md b/docs/Examples/Solana/address-api.md index dc492c2..a47e1a1 100644 --- a/docs/Examples/Solana/address-api.md +++ b/docs/Examples/Solana/address-api.md @@ -6,7 +6,7 @@ keywords: [Solana API examples, Solana GraphQL queries, Bitquery] # Solana Address API -## Latest Balance of an address +## Get Latest Solana Address Balance This below query will get you the latest balance of an address. You can run the query [here](https://ide.bitquery.io/address-balance-api). @@ -23,7 +23,7 @@ query MyQuery { } ``` -## Latest Balance of multiple addresses +## Query Multiple Solana Address Balances This below query will get you the latest balance of multiple addresses. You can specify any other addresses as well. And you can test the API with as many addresses as you like. You can run the query [here](https://ide.bitquery.io/latest-balances-of-multiple-addresses). diff --git a/docs/Examples/Solana/instructions.md b/docs/Examples/Solana/instructions.md index baae1ba..59d2828 100644 --- a/docs/Examples/Solana/instructions.md +++ b/docs/Examples/Solana/instructions.md @@ -6,7 +6,7 @@ keywords: [Solana API examples, Solana GraphQL queries, Bitquery] # Solana Instructions Data -## Recent Solana Instructions +## Recent Solana Instructions with Actions, Programs, and Logs The below query allows you to retrieve a set of instructions from the Solana blockchain network. These instructions form the building blocks of transactions and smart contracts on the network. The fields within the instructions `{}` specify the data that the query will return for each instruction. This includes details about the action, block, transaction, program, log, external action, external program, and raw data associated with each instruction. @@ -74,7 +74,7 @@ query ($network: SolanaNetwork!, $limit: Int!, $offset: Int!) { This will return the last 100 instructions from the Solana network on a particular day. You can adjust the limit and offset and period parameters as needed to retrieve different sets of instructions. -## Find Transactions based on Program +## Find Solana Instructions by Parsed Action Name The below query find all instructions, corresponding transactions and program logs for a specific program on the Solana blockchain. You can run the query [here](https://ide.bitquery.io/Solana-compactupdatevotestate-Action_4) @@ -139,7 +139,7 @@ query ($network: SolanaNetwork!, $limit: Int!, $offset: Int!) { "network": "solana" } ``` -## Recent Solana Transactions +## Recent Solana Transactions After Block Height with Fee and Signer The query provided retrieves the latest transactions on the Solana blockchain following block number `286563743` after the timestamp of `2024-12-18T06:30:00Z`. It details the count of instructions within each transaction, identifies the account that initiated the transaction, and lists the unique signature that distinguishes the transaction. Additionally, it specifies the number of inner instructions, which are instructions nested within other instructions, among other transaction-related information. You can run the query [here](https://ide.bitquery.io/Recent-Solana-Transactions_1) diff --git a/docs/Examples/Solana/transactions-api.md b/docs/Examples/Solana/transactions-api.md index c5f3f8e..7f6abed 100644 --- a/docs/Examples/Solana/transactions-api.md +++ b/docs/Examples/Solana/transactions-api.md @@ -6,7 +6,7 @@ keywords: [Solana API examples, Solana GraphQL queries, Bitquery] # Solana Transactions API -## Transactions in a specific timeperiod +## Get Solana Transactions by Date Range This below query will get you the transactions for a specific timeperiod. You can change the timeperiod values as per your need. You can run the query [here](https://ide.bitquery.io/transactions-in-a-specific-timeperiod). @@ -39,7 +39,7 @@ query MyQuery { ``` -## Transactions of an address for a specific timeperiod +## Get Solana Address Transactions by Date Range This below query will get you the transactions of an address for a specific timeperiod. You can change the address and timeperiod values as per your need. You can run the query [here](https://ide.bitquery.io/transactions-of-an-address-in-a-specific-timeperiod). diff --git a/docs/Examples/Solana/transfers.md b/docs/Examples/Solana/transfers.md index 0b43e8f..29bc236 100644 --- a/docs/Examples/Solana/transfers.md +++ b/docs/Examples/Solana/transfers.md @@ -52,7 +52,7 @@ Learn more about [WebSocket subscriptions](https://docs.bitquery.io/docs/subscri For streaming real-time data, check our [Solana Streaming API docs](https://docs.bitquery.io/v1/docs/examples/Solana) -## Recent transfers to/from a wallet address +## Recent Solana Transfers for a Wallet as Sender or Receiver This query retrieves the most recent 100 transfers involving a specific wallet address, showing both incoming and outgoing transactions. The `any` keyword allows us to search for transfers where the wallet is either the sender OR receiver in a single query. @@ -91,7 +91,7 @@ query MyQuery { } ``` -## Holding Period of a Token by a Wallet +## Solana Token Holding Period in Blocks for One Wallet This query calculates how long a wallet has been holding a specific token by looking at the first and last transfer block heights for that token into the wallet. It is useful for analyzing token holding behavior, vesting, or eligibility for airdrops and loyalty programs. @@ -120,7 +120,7 @@ query MyQuery { } ``` -## Get Pumpfun Token Created by a Wallet From Historical Data +## Historical Solana Pumpfun Tokens Minted by Wallet from Transfers [Run query](https://ide.bitquery.io/get-historical-created-token-and-creator) @@ -183,7 +183,7 @@ query MyQuery { } ``` -## Pumpfun Token Migrations on a specific date +## Solana Pumpfun Token Migrations on a Specific Calendar Date Below API retrieves pump fun token migrations on a specific date. @@ -254,7 +254,7 @@ Try the query [here](https://ide.bitquery.io/pumpfun-transfers-type-v1-to-pumpfu } ``` -## Check if a pump fun token was launched in Mayhem mode - Historical Query +## Detect Solana Pumpfun Mayhem Mode Launch by Mint Amount This query finds "Pump Fun" token launches in Mayhem mode by filtering for a transfer of exactly 1,000,000,000,000,000 units (1 Billion if adjusted to 6 decimal places) to the specified receiver and token mint. It returns currency info, amount, and transaction signature. In mayhem mode token, 1 Billion token supply is minted to `BwWK17cbHxwWBKZkUYvzxLcNQ1YVyaFezduWbtm2de6s` Mayhem Autonomous AI agent. Try out the API [here](https://ide.bitquery.io/check-if-a-pump-fun-token-was-in-mayhem-mode). @@ -282,7 +282,7 @@ query MyQuery { } ``` -## Currency Sent and Received by an address +## Solana Per-Token Sent, Received, and Balance for an Address Below API will give you details on the aggreated currency sent and received by an address. Try the API [here](https://ide.bitquery.io/currency-sent-and-received-by-an-address#). @@ -316,7 +316,7 @@ query ($address: String!) { } ``` -## Balance of an address on a specific date +## Solana Wallet Balances per Token Up to a Point in Time This query calculates the balance of a wallet at a specific date by fetching all transfers sent and received transactions up to that height. `received - sent` is the balance of the address. @@ -352,7 +352,7 @@ query ($address: String!, $date: ISO8601DateTime!) { } ``` -## Token holders +## Solana SPL Token Holders with Aggregated Balances This query returns all holders of a specific token with their balances. It aggregates transfers by receiver (holder) for the given token: each row is a wallet address that holds the token, with total received (`sum_in`), total sent (`sum_out`), and current balance (`sum_in - sum_out`). Results are sorted by balance descending and limited to the top 10,000 holders. Use `date: { since: "..." }` to compute balances from a given date onward. @@ -384,7 +384,7 @@ You can run the query [here](https://ide.bitquery.io/solana-holders_1). } ``` -## Token Transfers to a Specific Wallet (for Bubble Map) +## Solana Token Inflows to a Wallet for Bubble Map Charts This query retrieves all incoming transfers of a specific token (e.g., USDT) to a given Solana wallet on a particular date. It includes sender and receiver details, transaction signatures, block data, and transfer amounts in USD — useful for visualizing wallet inflows using a Bubble Map. @@ -442,7 +442,7 @@ query TransfersForBubbleMap($since: ISO8601DateTime!, $currency: String, $limit: } ``` -## Find the Sender of a Token to An Address +## List Solana Token Senders to a Specific Receiver Address This query identifies all senders who have transferred a specific token to a particular wallet address. This is useful for tracking token sources. @@ -484,7 +484,7 @@ query MyQuery { ``` -## Historical Inflow/Outflow from a Wallet +## Solana Wallet Inflow and Outflow Transfers at Block Height This query demonstrates how to analyze wallet activity at a specific block height by separating incoming (inflow) and outgoing (outflow) transfers. This is particularly useful for understanding wallet behavior during specific events or time periods. @@ -580,7 +580,7 @@ You can run the query [here](https://ide.bitquery.io/outflowinflow-of-an-address ``` -## Transfers of a wallet for a specific time period +## Solana Wallet Transfers Within a Start and End Time Range This query demonstrates how to retrieve transfers for a specific wallet within a defined time range. This is essential for time-based analysis, reporting, and compliance requirements. @@ -620,7 +620,7 @@ query MyQuery { } ``` -## Top Transfers of a token +## Largest Solana Token Transfers by Amount After a Date This query identifies the largest transfers for a specific token, sorted by transfer amount. This is useful for identifying significant token movements and whale activity. @@ -660,7 +660,7 @@ query MyQuery { ``` -## Historical Balance of a Wallet Address using transfers +## Solana Wallet Historical SOL and Stablecoin Balances via Transfers This query demonstrates how to calculate a wallet's historical balance by analyzing all incoming and outgoing transfers up to a specific point in time. The balance is calculated by subtracting total outgoing transfers from total incoming transfers, with amounts converted to USD for accurate valuation. @@ -702,7 +702,7 @@ Test the query [here](https://ide.bitquery.io/solana-money-sent-and-recieved-by- ``` -## Get Transaction details for a specific signature +## Solana Transfers for All Instructions in One Transaction Signature This query retrieves all transfer details contained within a specific transaction signature. This is essential for transaction analysis, debugging, and understanding the complete flow of a multi-transfer transaction. @@ -755,7 +755,7 @@ query MyQuery { } ``` -## Get transfers data for a specific time period +## Solana Network-Wide Transfers in a Narrow Time Window This query retrieves all transfers within a specific time window across the entire Solana network. This is useful for network-wide analysis, but requires careful time range selection due to the high volume of transfers on Solana. diff --git a/docs/Examples/Staking/stake_examples.md b/docs/Examples/Staking/stake_examples.md index 52b3cd5..98a1d88 100644 --- a/docs/Examples/Staking/stake_examples.md +++ b/docs/Examples/Staking/stake_examples.md @@ -28,7 +28,7 @@ query MyQuery { ``` -## Get Latest staked NFT on Ethereum +## Get Latest BSC StakeNFT Events From the YieldFarming Contract The query below retrieves the latest 10 transactions on the Ethereum blockchain which called the `StakeNFT` event on the `YieldFarming` smart contract address You can access the query [here](https://ide.bitquery.io/latest-Staked-NFT_1) @@ -58,7 +58,7 @@ You can access the query [here](https://ide.bitquery.io/latest-Staked-NFT_1) ``` -## Staking Rewards for every Block on Solana +## Get Recent Solana Staking Rewards per Block Sorted by Height The query below retrieves the staking rewards for every block on the Solana blockchain. The query limits the results to the 10 most recent blocks and sorts the results by `block height` in `descending` order. You can access the query [here](https://ide.bitquery.io/staking-rewards-on-solana) diff --git a/docs/Examples/Transactions/input-output-api.md b/docs/Examples/Transactions/input-output-api.md index c397959..4b2c0ee 100644 --- a/docs/Examples/Transactions/input-output-api.md +++ b/docs/Examples/Transactions/input-output-api.md @@ -12,7 +12,7 @@ keywords: [UTXO API examples, Bitcoin GraphQL queries, Bitquery] -## All inputs and outputs of a transaction +## List Bitcoin Transaction Inputs and Outputs With Scripts and Values To check all inputs and outputs of a Bitcoin transaction, you can use the following query. Additionally, there are filters like `inputScriptType` , `inputAddress`, `inputValue`, which you can use to get transactions based on your requirements. diff --git a/docs/Examples/Transactions/transaction-api.md b/docs/Examples/Transactions/transaction-api.md index ca35342..8830c9f 100644 --- a/docs/Examples/Transactions/transaction-api.md +++ b/docs/Examples/Transactions/transaction-api.md @@ -8,7 +8,7 @@ keywords: [transaction API examples, GraphQL queries, Bitquery] To get transactions from different blockchains, you can use our Transaction API. Let's see some examples. -## Bitcoin Transaction +## Get Recent Bitcoin Transactions With Fees Sizes and In Out Values Let' see an example to get transactions from the Bitcoin blockchain. @@ -51,7 +51,7 @@ Let' see an example to get transactions from the Bitcoin blockchain. } ``` -## Ethereum Transaction API +## Get Recent Ethereum Transactions With Gas Nonce and Recipients Let's see another example on how to get transactions from Ethereum blockchain. @@ -103,7 +103,7 @@ Let's see another example on how to get transactions from Ethereum blockchain. } ``` -## Transaction in a block +## List Ethereum Transactions Inside One Block by Block Height To check transaction in a block use following query. You can use `in: ["block1","block2"]` if you want to get transactions from multiple blockchains. @@ -155,7 +155,7 @@ To check transaction in a block use following query. You can use `in: ["block1", } ``` -## Transaction for a user +## Get Ethereum Transactions To From or Creating One User Address To get transactions for a user, you can use the following query. As you can see, we are using the `any` operator, which is basically how you add OR conditions in filters. @@ -212,7 +212,7 @@ To get transactions for a user, you can use the following query. As you can see, } ``` -## Get Daily Transaction Count on Solana +## Get Daily Solana Transaction Counts for the Last Ten Days [Access the query here](https://ide.bitquery.io/Get-daily-Solana-transaction-volume-for-the-last-10-days) @@ -232,7 +232,7 @@ query get_per_day_transaction_count_of_solana_for_last_ten_days{ } ``` -## Get Cronos-Bridged and Crypto.org Transactions +## Get Cronos or Crypto.org Chain Transaction Details by Hash The below query gets complete information on Cronos or Crypto.org transaction using the `hash`. You can find the query [here](https://ide.bitquery.io/Cronos-Bridged-Tx-Info) @@ -272,7 +272,7 @@ query ($network: CosmosNetwork!, $hash: String!) { The `rawTx` field contains complete information encoded including Source Channel,Receiver Address,Memo,auth_info,signer and so on. -## Get Daily Unique Senders/ Receivers +## Count Unique Ethereum Transaction Senders and Receivers on One Date In the below query , we are querying for the distinct count of senders and receivers who made transactions on a specific date by using the `uniq` filter and aliasing `uniq: senders` and `uniq: receivers`. diff --git a/docs/Examples/Transfers/transfer-api.md b/docs/Examples/Transfers/transfer-api.md index d749dd6..daa6d9d 100644 --- a/docs/Examples/Transfers/transfer-api.md +++ b/docs/Examples/Transfers/transfer-api.md @@ -9,7 +9,7 @@ sidebar_position: 1 Transfer API is available for all blockchains that have smart contract capabilities, especially EVMs. This api helps you get token (native or non-native) transfers. Let's see a few examples. -## All transfers for a token +## Get All WBNB Token Transfers on BNB Chain To get all transfers for a token, you can use the following api. In this API, we are mentioning WBNB token transfer, and for that, we are mentioning its token address 0xbb4cdb9cbd36b01bd1cbaebf2de08d9173bc095c. You can get transfers for more than one currency by mentioning their address using `{in: ["currency1", "currency2"…]}` instead of using `{is: "currency"}`. Additionally to get transfers for the native token, you need to use its symbol directly for example, in case of a BNB chain `BNB` is the native token, therefore you can just mention its symbol like `{is: "BNB"}`. @@ -53,7 +53,7 @@ To get all transfers for a token, you can use the following api. In this API, we } ``` -## Transfers sent by an address +## Track WBNB Transfers Sent by a BNB Chain Address To check all transfers sent by an address you can following query. @@ -98,7 +98,7 @@ To check all transfers sent by an address you can following query. } ``` -## Transfers received by address +## Get WBNB Transfers Received by a BNB Chain Address To check all transfers received by an address use following query. @@ -143,7 +143,7 @@ To check all transfers received by an address use following query. } ``` -## All transfers of a address +## Query All WBNB Transfers Sent and Received by an Address We can use `any` filter, which is basically an `OR` condition to get all transfers sent and received by an address. @@ -191,7 +191,7 @@ We can use `any` filter, which is basically an `OR` condition to get all transfe } ``` -## Biggest transfers of a token +## Fetch Largest WBNB Transfers on BNB Chain by Amount To check the biggest transfers of a token, you can use the following query. In this query, we are ordering results based on the transfer amount. @@ -235,7 +235,7 @@ To check the biggest transfers of a token, you can use the following query. In t } ``` -## Transfers of a transaction +## Get All Transfers Inside a BNB Chain Transaction To check all transfers in a transaction use following query. @@ -279,7 +279,7 @@ To check all transfers in a transaction use following query. } ``` -## All transfers in a block +## Query All Transfers in a Specific BNB Chain Block To check all transfers in a block use following query. @@ -318,7 +318,7 @@ To check all transfers in a block use following query. } ``` -## All internal transfers +## Query Internal-Only Transfers in a BNB Chain Block Internal transfers are triggered by smart contract and using the following query you can check only internal transfers by using filter `external : false`. @@ -355,7 +355,7 @@ Internal transfers are triggered by smart contract and using the following query } ``` -## Summary of token received by a wallet +## Aggregate Tokens Received by a BNB Chain Wallet Since a Date Our GraphQL APIs are very good for aggregation. For example, in the following query, we are getting all currencies with the amount received by address on the Binance chain since 1st Jan 2023. Note: As the BNB chain has a huge amount of data, therefore to optimize the query you should use date and try not to query data over 1 year, otherwise it might not return results. @@ -381,7 +381,7 @@ https://ide.bitquery.io/Summary-of-tokens-received-by-an-address } ``` -## Latest Filecoin Transfers +## Get Latest Filecoin Blocks Sorted by Height The query below allows gets the latest Filecoin transfers made on the Filecoin network ordered by descending order of block height and limited to 10 responses between the two dates `from` and `till` @@ -419,7 +419,7 @@ The query below allows gets the latest Filecoin transfers made on the Filecoin n } ``` -## SPL (Solana Program Library ) Token Transfers +## Get SPL Token Transfers on Solana Excluding Native SOL This query is used to fetch the SPL token transfers on the Solana network within a specific time frame. It excludes SOL transfers and only considers those transactions where the transferred amount is greater than zero. @@ -471,7 +471,7 @@ query ($network: SolanaNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date } ``` -## Celo NFT Transfers +## Fetch GANG and CeloPunks NFT Transfers on Celo Mainnet The below query gets transfers for ChinChilla Gang (GANG) NFT and CeloPunks NFT collection on Celo network by mentioning the curency smart contract in the ` currency: {in:}` filter. You can use it to retrieve the most recent transfers for specific NFT collections You can find the query [here](https://ide.bitquery.io/Celo-NFT-Transfers) diff --git a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md index 29e5cd6..87ebd3d 100644 --- a/docs/Examples/activeAddresses/blockchain-active-addresses-api.md +++ b/docs/Examples/activeAddresses/blockchain-active-addresses-api.md @@ -10,7 +10,7 @@ Use our activeAddresses API to get active address for any blockchain, currency, -## Active addresses for blockchain +## Get Active Ethereum Addresses Count Since a Date To get active addresses for the complete blockchain, you can use the following query. In the following query, we re getting active addresses since 1st Jan 2023. Also, using date will optimize the api and produce results quickly. @@ -27,7 +27,7 @@ To get active addresses for the complete blockchain, you can use the following q ``` -## Active addresses for currencies +## Query Active Ethereum Addresses for USDT Token Activity You can also get active addresses for specific currencies. In the following example we are getting active addresses for [USDT](https://explorer.bitquery.io/ethereum/token/0xdac17f958d2ee523a2206206994597c13d831ec7) diff --git a/docs/Examples/address/Blockchain-Address-API-Examples.md b/docs/Examples/address/Blockchain-Address-API-Examples.md index 0cd5ab7..19ea813 100644 --- a/docs/Examples/address/Blockchain-Address-API-Examples.md +++ b/docs/Examples/address/Blockchain-Address-API-Examples.md @@ -10,7 +10,7 @@ sidebar_position: 1 Our APIs can provide all sorts of details for any address on the blockchain. Let's see some examples. -## Transactions of an Address +## Get All Transactions for an Ethereum Address To check transactions sent and received by an address, you can use following API. You can get same data for multiple addresses, just use `{in: ["address1", "address2"]}` instead of `{is: "address"}`. [Open this query on IDE](https://ide.bitquery.io/ethereum-transactions-of-an-address) @@ -45,7 +45,7 @@ To check transactions sent and received by an address, you can use following API ``` -## Transfers of an Address +## Get Ethereum Token Transfers Sent and Received by an Address To get token transfers of addresses use following API, in this example we are showing all sent and received token transfers of an address. @@ -87,7 +87,7 @@ To get token transfers of addresses use following API, in this example we are sh ``` -## Transfers sent by multiple addresses +## Track Transfers Sent by Multiple Ethereum Addresses You can transfers for multiple addresses, for example in the following query we are getting transfers sent by two addresses (0xa106c1a6c0e46826fbb4e82b9337bb880c3e2575 & 0x93ff65b50b2f12387bc448d5ee17c1600cd66626). You can use upto 100 addresses in a query. @@ -133,7 +133,7 @@ You can transfers for multiple addresses, for example in the following query we ``` -## Trades of an Address +## Query DEX Trades for an Ethereum Address To check trades of an address you can use our DEX trade API. @@ -174,7 +174,7 @@ To check trades of an address you can use our DEX trade API. ``` -## Balance of an Address +## Query Address Balances on Polygon and Bitcoin Networks To check balance of an address use our balance API. @@ -222,7 +222,7 @@ For UTXO based blockchains such as Bitcoin, Litcoin, dogecoin, you can get input ``` -## Balance history of an Address +## Track USDT Balance History for an Ethereum Address You can also get balance history of any address using our v1 APIs. Additionly in V2 we have created [`BalanceUpdates`](https://docs.bitquery.io/docs/examples/balances/balance-api/) API, which extend this capabilities. [Open this query on IDE](https://ide.bitquery.io/usdt-balance-history-template_1) @@ -258,7 +258,7 @@ You can also get balance history of any address using our v1 APIs. Additionly in } ``` -## Smart Contract calls of an address +## Get Smart Contract Calls for a Polygon Address TO get smart contract call of an address use our SmartContractCalls API. [Open this query on IDE](https://ide.bitquery.io/query/XVYLusoNeGcYm5b3) @@ -299,7 +299,7 @@ TO get smart contract call of an address use our SmartContractCalls API. ``` -## Source of funds from an address +## Trace Inbound ETH Sources to an Ethereum Address with Coinpath To check the source of funds for any address you can use our Coinpath APIs. @@ -349,7 +349,7 @@ To check the source of funds for any address you can use our Coinpath APIs. ``` -## Destination of funds from an address +## Track Outbound ETH Destinations from an Ethereum Address with Coinpath Coinpath API also helpful to get the destination of funds. Check following example. diff --git a/docs/Examples/address/specific-queries.md b/docs/Examples/address/specific-queries.md index d755705..0e45767 100644 --- a/docs/Examples/address/specific-queries.md +++ b/docs/Examples/address/specific-queries.md @@ -7,7 +7,7 @@ sidebar_position: 2 # Specific Queries on Address and Balances -## Get Native and Token Balance for a Matic Address +## Get Native MATIC and Token Balances on Polygon for an Address This is a query that retrieves the native balance and token balances for an Ethereum address on the Matic network. The native balance is the balance of the account in its native currency, which is MATIC in this case. The token balances are the balances of the account in other currencies. diff --git a/docs/Examples/addressStats/address-stats-api.md b/docs/Examples/addressStats/address-stats-api.md index 0de6150..de251a7 100644 --- a/docs/Examples/addressStats/address-stats-api.md +++ b/docs/Examples/addressStats/address-stats-api.md @@ -7,6 +7,8 @@ keywords: [address stats API examples, GraphQL queries, Bitquery] # Address Stats API +## Get Balance, Transfers, and Transaction Stats for an Ethereum Address + The Address Stats API provides comprehensive statistical data for a specific Ethereum address. In the below qeurey we are getting information for `0x21a31ee1afc51d94c2efccaa2092ad1028285549` by specifiying it in `address` filter. ``` { diff --git a/docs/Examples/algorand/address.md b/docs/Examples/algorand/address.md index a36b020..1b9ab62 100644 --- a/docs/Examples/algorand/address.md +++ b/docs/Examples/algorand/address.md @@ -8,7 +8,7 @@ keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] Our Algorand Address API provides all details regarding any address on Algorand Blockchain. If given address is a smart contract, API also provides details of that smart contract too. Below are some examples of `address` API: -## Get Balance of An Address +## Get Algorand Address Balance ``` { @@ -27,7 +27,7 @@ Our Algorand Address API provides all details regarding any address on Algorand Replace `ADDRESS_HERE` with the actual Algorand address you want to query. This query will return the balance of the address in the Algorand blockchain along with the address itself. The `is` operator is used to filter for a single specific address, ensuring that only data related to that exact address is returned. -## Get Balance of Multiple Addresses +## Get Algorand Balances for Multiple Addresses ``` { @@ -44,7 +44,7 @@ Replace `ADDRESS_HERE` with the actual Algorand address you want to query. This Replace addresses in the array with the actual Algorand addresses you want to query. This query will retrieve the balances of these addresses from the Algorand blockchain. The `in` operator allows you to filter multiple addresses at once by specifying a list of addresses to retrieve their information. -## Get Bytecode & Source of Smart Contract +## Get Algorand Smart Contract Bytecode and Source ``` { diff --git a/docs/Examples/algorand/blocks.md b/docs/Examples/algorand/blocks.md index 4c074cd..ca124c1 100644 --- a/docs/Examples/algorand/blocks.md +++ b/docs/Examples/algorand/blocks.md @@ -8,7 +8,7 @@ keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] Pur Alogrand Blocks API provides all details regarding blocks generated on Algorand Blockchain. Below are some examples of `blocks` API: -## Get Latest Blocks by A Proposer +## Get Latest Algorand Blocks by Proposer Address ``` { @@ -36,7 +36,7 @@ Pur Alogrand Blocks API provides all details regarding blocks generated on Algor Replace `PROPOSER_ADDRESS_HERE` with the actual Algorand address of the proposer you want to query. This query will return the details of the 10 latest blocks from the Algorand blockchain, produced by the specified proposer address after the date "2023-08-05". The retrieved block information includes block height, hash, current protocol version, proposer address, reward, seed, and timestamp. -## Get Total Reward Earned By Proposer +## Sum Algorand Block Rewards for a Proposer ``` { diff --git a/docs/Examples/algorand/coinpath.md b/docs/Examples/algorand/coinpath.md index d02348c..0afe0fb 100644 --- a/docs/Examples/algorand/coinpath.md +++ b/docs/Examples/algorand/coinpath.md @@ -8,7 +8,7 @@ keywords: [Algorand API examples, Algorand GraphQL queries, Bitquery] Our Algorand Coinpath API provides detailed information about money flow of addresses on the Algorand Blockchain. -## Get Transactions for Sender after Date +## Get Algorand Coinpath Transactions for Sender After Date ``` { @@ -43,7 +43,7 @@ Our Algorand Coinpath API provides detailed information about money flow of addr Replace `SENDER_ADDRESS_HERE` with the actual Algorand address of the sender you want to query. This query will return detailed information about the latest 10 coinpath transactions from the Algorand blockchain. The transactions will be filtered to include only those where the specified sender address sent tokens after the date "2023-08-05". The query will fetch the amount of tokens involved, the timestamp of the block where each transaction occurred, the currency address and name, the depth of each transaction, the receiver's address, and the transaction hash and value. -## Get Count of Coinpath Transactions for Receiver after Date +## Count Algorand Coinpath Transactions Received by Address After Date ``` { diff --git a/docs/Examples/algorand/smartContractCalls.mdx b/docs/Examples/algorand/smartContractCalls.mdx index ff7512a..a5ba14d 100644 --- a/docs/Examples/algorand/smartContractCalls.mdx +++ b/docs/Examples/algorand/smartContractCalls.mdx @@ -4,7 +4,7 @@ Our Algorand Smart Contract Calls API provides detailed information about smart import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Count of Smart Contract Calls in Latest Block +## Count Unique Algorand Smart Contract Calls in Latest Block The query retrieves the latest block and provides the count of unique smart contract calls made within that block. @@ -28,7 +28,7 @@ You can check the query [here](https://ide.bitquery.io/Get-Count-of-Smart-Contra } ``` -## Get Latest Created Assets on Algorand +## Get Latest Algorand Asset Config Transactions Creating New Assets The query retrieves information about the latest 10 smart contract calls on the Algorand blockchain with the transaction type "acfg" including the timestamp of the block, the smart contract address, the transaction hash, the sender's address, and the transaction type. `acfg` stands for asset config here. @@ -64,7 +64,7 @@ You can find the query [here](https://ide.bitquery.io/Track-latest-assets-create ``` -# Get Count of each transaction type since Genesis Block +## Count Algorand Smart Contract Calls by Transaction Type Since Genesis The query retrieves the number of times each txn type has been called since the genesis block (first block) of Algorand Mainnet. You can find the query [here](https://ide.bitquery.io/Count-of-each-trxn-type-called-till-now-on-Algorand-network#). @@ -81,7 +81,7 @@ query MyQuery { ``` -## Get Latest Smart Contract Calls with Transaction Type +## Get Latest Algorand Smart Contract Calls Filtered by Transaction Type The query retrieves information about the latest 10 smart contract calls on the Algorand blockchain with the transaction type "pay," including the timestamp of the block, the smart contract address, the transaction hash, the sender's address, and the transaction type. diff --git a/docs/Examples/algorand/transactions.mdx b/docs/Examples/algorand/transactions.mdx index 84847de..013b58c 100644 --- a/docs/Examples/algorand/transactions.mdx +++ b/docs/Examples/algorand/transactions.mdx @@ -4,7 +4,7 @@ Our Algorand Transaction API provides detailed information about Algorand Transa import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Latest Transactions +## Get Latest Algorand Transactions with Block and Fee Details The query retrieves the latest 10 transactions from the Algorand blockchain, providing details such as the block height, timestamp, currency address and name, fee, group, transaction hash, index, sender's address, subtype, and type of each transaction. @@ -39,7 +39,7 @@ The query retrieves the latest 10 transactions from the Algorand blockchain, pro } ``` -## Get all the transactions in a specific timeframe +## Get Algorand Transactions in a Specific Date Range This query retrieves all the transactions in a specific date range on Algorand network using Bitquery Transactions API. You can find the query [here](https://ide.bitquery.io/All-Transactions-on-Algorand#). @@ -87,7 +87,7 @@ query MyQuery { ``` -## Get Daily Transaction Count of Algorand network +## Get Daily Algorand Transaction Counts for Recent Days This query retrieves the number of transactions happened each day in the last 10 days on Algorand network using Bitquery Transactions API. You can find the query [here](https://ide.bitquery.io/Daily-Transaction-Count-for-last-10-days#). @@ -106,7 +106,7 @@ query MyQuery { ``` -## Get Daily Unique Senders of Transactions on Algorand network +## Count Unique Algorand Transaction Senders for a Single Day This query retrieves the number of unique senders of transactions on date `2024-07-08` using this filter `(date: {is: "2024-07-08"})` on Algorand network using Bitquery Transactions API. You can find the query [here](https://ide.bitquery.io/Daily-Unique-Txn-Senders-on-algorand#). @@ -122,7 +122,7 @@ query MyQuery { ``` -## Get Count of Transactions by a Particular Address +## Count Algorand Transactions Sent from a Specific Address The query retrieves the count of all transactions sent by the specified Algorand address ("ADDRESS_HERE") from the Algorand blockchain. @@ -138,7 +138,7 @@ The query retrieves the count of all transactions sent by the specified Algorand } ``` -## Get Information about a Particular Transaction +## Get Algorand Transaction Details by Transaction Hash The query retrieves details of a specific transaction with the given transaction hash ("TXN_HASH_HERE") from the Algorand blockchain, including the block height, timestamp, currency address and name, sender's address, subtype, and type of the transaction. diff --git a/docs/Examples/algorand/transfers.mdx b/docs/Examples/algorand/transfers.mdx index 3948ac0..a48c3d7 100644 --- a/docs/Examples/algorand/transfers.mdx +++ b/docs/Examples/algorand/transfers.mdx @@ -4,7 +4,7 @@ Our Algorand Transfers API provides detailed information about Algorand Transfer import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Transfers of a specific Asset on Algorand +## Get Algorand Transfers for a Specific Asset in a Date Range This query gives you the transfers of a specific Asset in a given timeframe on Algorand network. You can find the query [here](https://ide.bitquery.io/All-the-transfers-of-an-asset-on-Algorand-Mainnet-in-a-specific-timeframe). @@ -50,7 +50,7 @@ query MyQuery { } ``` -## Get transfers where sender/receiver of an asset is a particular address +## Get Algorand Transfers to or from an Address for a Specific Asset This query gives you the transfers of a specific Asset sent to or from a particular address in a given timeframe on Algorand network. You can find the query [here](https://ide.bitquery.io/traansfers-where-a-currency-is-sent-from-or-sent-to-a-particular-address). diff --git a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md index 2c14819..ce1c279 100644 --- a/docs/Examples/bitcoin/Bitcoin-Blocks-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Blocks-API.md @@ -8,7 +8,7 @@ keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] Our Bitcoin Blocks API provides all the information related to blocks produced on Bitcoin network. -## Retrieve the 10 Most Recent Blocks +## Retrieve Ten Most Recent Bitcoin Blocks with Height and Stats ``` query { @@ -30,7 +30,7 @@ query { This query retrieves details about the 10 most recent blocks on the Bitcoin blockchain. It includes information like block hash, height, difficulty, block size, and timestamp for each block. The results are ordered by block heights in descending order. -## Get the Blocks with maximum Transactions +## Get Top Bitcoin Blocks Ranked by Transaction Count ``` query { diff --git a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md index acbffb2..87e1c93 100644 --- a/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Coinpath-API.md @@ -8,7 +8,7 @@ keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] Our Bitcoin Coinpath API provides comprehensive information about money flow of addresses on the **Bitcoin** blockchain. -## Explore +## Explore Bitcoin Coinpath Flow from a Seed Address [Run API](https://ide.bitquery.io/Destination-of-Funds-from-a-Specific-Address-on-Bitcoin) @@ -45,7 +45,7 @@ Our Bitcoin Coinpath API provides comprehensive information about money flow of This query retrieves a list of coinpath transactions initiated from a specific initial address (bc1p4kufll9uhnpkgzuc65slcxd2qaw2hl9xecket3h8yyu4awglcsqslqaztd) after a certain date (2023-10-10). The query limits the results to 10 transactions and orders them by timestamp in descending order. For each transaction, it provides details such as the transferred amount in USD, block height, timestamp, currency information, sender and receiver addresses, transaction hash, and value. -## Get Money Flow With Particular Receiver Address +## Bitcoin Coinpath Inflows to a Specific Receiver Address ``` query ($network: BitcoinNetwork!) { @@ -76,7 +76,7 @@ query ($network: BitcoinNetwork!) { This query allows you to retrieve the money flow details where the receiver is a particular address (bc1p4kufll9uhnpkgzuc65slcxd2qaw2hl9xecket3h8yyu4awglcsqslqaztd) after October 10, 2023. The results are ordered in descending order based on block heights and are limited to the top 10 entries. -## Investigate Relationship Between Two Addresses +## Bitcoin Coinpath Between Initial and Receiver Addresses ``` query ($network: BitcoinNetwork!) { diff --git a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md index 1ce03e6..733d10e 100644 --- a/docs/Examples/bitcoin/Bitcoin-Transaction-API.md +++ b/docs/Examples/bitcoin/Bitcoin-Transaction-API.md @@ -6,7 +6,7 @@ keywords: [Bitcoin API examples, Bitcoin GraphQL queries, Bitquery] # Transaction API -## Get Latest Transaction +## Get Latest Bitcoin Transactions with Fees and Transfer Values ``` query ($network: BitcoinNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601DateTime, $till: ISO8601DateTime) { @@ -37,7 +37,7 @@ query ($network: BitcoinNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Dat The query retrieves the latest 10 transactions from the Bitcoin blockchain, providing details such as the block height, timestamp, currency address and name, fee, group, transaction hash, index, sender's address, subtype, and type of each transaction. -## Avg. Fee per transaction for each day +## Daily Bitcoin Transaction Count and Average Fee per Day ``` query ($network: BitcoinNetwork!, $dateFormat: String!, $from: ISO8601DateTime, $till: ISO8601DateTime) { @@ -57,7 +57,7 @@ query ($network: BitcoinNetwork!, $dateFormat: String!, $from: ISO8601DateTime, The query retrieves the latest 7 days average fee per transaction from the Bitcoin blockchain, providing details such as the average fee by per day for a week. -## Get Count of Transactions by a Particular Address +## List Bitcoin Transactions Sent from a Specific Address ``` query ($network: BitcoinNetwork!) { diff --git a/docs/Examples/bitcoin/bitcoin-address-api.md b/docs/Examples/bitcoin/bitcoin-address-api.md index f64d356..2513ef3 100644 --- a/docs/Examples/bitcoin/bitcoin-address-api.md +++ b/docs/Examples/bitcoin/bitcoin-address-api.md @@ -10,7 +10,7 @@ Our Input/Output APIs provides all the details regarding any address on Bitcoin ## Bitcoin Balance API -### Using Balance Cube +### Bitcoin Address Balance via addressStats [Run Query](https://ide.bitquery.io/Bitcoin-balance_5) @@ -39,7 +39,7 @@ Our Input/Output APIs provides all the details regarding any address on Bitcoin ``` -### Using Inputs and Outputs +### Bitcoin Address Balance via Inputs and Outputs ``` { @@ -70,7 +70,7 @@ Our Input/Output APIs provides all the details regarding any address on Bitcoin Try this API [here](https://ide.bitquery.io/Bitcoin-balance-using-input-outputs) -## Get Balance of Multiple Addresses +## Get Aggregated Bitcoin Balances for Multiple Addresses To get addresses of multiple bitcoin addresses just by providing them in the parameters. @@ -109,7 +109,7 @@ To get addresses of multiple bitcoin addresses just by providing them in the par Try API for getting balance of multiple bitcoin addresses [here].(https://ide.bitquery.io/BTC-balance-API-for-multiple-addresses) -## Get the age of the Address +## Get Bitcoin Address First and Last Active Timestamps To get the age of the bitcoin wallet, you can use the following API. @@ -138,7 +138,7 @@ query ($network: BitcoinNetwork!) { Replace ADDRESS_HERE with the desired Bitcoin Address you want to query. This query fetches the first and last date, time of the transaction of the wallet in different formats you would need. -## Get net inflow and outflow of bitcoin from an address +## Bitcoin Address Inputs and Outputs Over a Date Range To get inflows and outflow of a bitcoin address, use following API. diff --git a/docs/Examples/bitcoin/bitcoin-fee-api.md b/docs/Examples/bitcoin/bitcoin-fee-api.md index 7dc1f16..e6a0cb9 100644 --- a/docs/Examples/bitcoin/bitcoin-fee-api.md +++ b/docs/Examples/bitcoin/bitcoin-fee-api.md @@ -10,7 +10,7 @@ This Bitquery API allows you to query Bitcoin transaction fees using GraphQL. Yo import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Bitcoin Transactions and Fees of an Account +## List Bitcoin Transactions with Per-Tx Fees and USD Fees Below query will get you bitcoin transactions for a account along with the transaction fees. You can try out the query [here](https://ide.bitquery.io/bitcoin-trxn-fees-for-a-account_2). @@ -47,7 +47,7 @@ qquery MyQuery { } ``` -## Get Total fees paid by an account on Bitcoin network +## Sum Total Bitcoin Fees Paid by an Address on One Day Below query will get you total fees paid by an account on Bitcoin network. You can try out the query [here](https://ide.bitquery.io/Get-Total-fees-paid-by-an-account-on-Bitcoin-network). diff --git a/docs/Examples/bitcoin/index.md b/docs/Examples/bitcoin/index.md index 52be42d..20a89c4 100644 --- a/docs/Examples/bitcoin/index.md +++ b/docs/Examples/bitcoin/index.md @@ -9,31 +9,31 @@ slug: /examples/Bitcoin/ This section contains Bitcoin API/Streams examples and guides, organized into categories for easier navigation. This is not exhaustive; we will add more examples as users request different scenarios. Also available in real-time via [Bitquery Kafka Streams](https://docs.bitquery.io/docs/streams/protobuf/chains/Bitcoin-protobuf/). Please contact sales for trial credentials. -## Blocks +## Bitcoin Blocks API - [Blocks API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-blocks-api) -## Address +## Bitcoin Address API - [Address API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-address-api) -## Coinpath +## Bitcoin Coinpath Fund Tracking - [Coinpath API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-coinpath-api) -## Fees +## Bitcoin Fees API - [Fee API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-fee-api) -## Inputs and Outputs +## Bitcoin Inputs and Outputs API - [Inputs and Outputs API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-input-and-output-api) -## Omni Layer +## Bitcoin Omni Layer API - [OmniTransactions and OmniTransfers API](https://docs.bitquery.io/v1/docs/Examples/bitcoin/Bitcoin-OmniTransactions-and-OmniTransfers%20API) -## Transactions +## Bitcoin Transaction API - [Transaction API](https://docs.bitquery.io/v1/docs/examples/bitcoin/bitcoin-transaction-api) diff --git a/docs/Examples/cosmos/address.md b/docs/Examples/cosmos/address.md index 558d90b..d0f6548 100644 --- a/docs/Examples/cosmos/address.md +++ b/docs/Examples/cosmos/address.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Address API provides all the details regarding any address on Cosmos Blockchain. -## Get Balance of Address +## Get Cosmos Address Balance ``` { @@ -22,7 +22,7 @@ Our Cosmos Address API provides all the details regarding any address on Cosmos Replace `ADDRESS_HERE` with the desired Cosmos address you wish to query. This will return the balance of the native currency associated with the given Cosmos address. -## Get Balance of Address in USD +## Get Cosmos Address Balance in USD ``` { @@ -36,7 +36,7 @@ Replace `ADDRESS_HERE` with the desired Cosmos address you wish to query. This w Replace `ADDRESS_HERE` with the desired Cosmos address you want to query. This query will provide the balance of the native currency associated with the given Cosmos address, displayed in USD. The `in` operator is utilized to specify the desired currency for balance conversion. -## Get Balance of Multiple Addresses +## Get Cosmos Balances for Multiple Addresses ``` { @@ -54,7 +54,7 @@ Replace `ADDRESS_HERE` with the desired Cosmos addresses you want to query. This -## Delegated Tokens and Rewards by a Cosmos address +## Get Staking Rewards and Delegated Tokens for a Cosmos Address Use [this query](https://ide.bitquery.io/cosmos-staking-reward-and-delegation0_7) to get rewards and delegated data for cosmos address. diff --git a/docs/Examples/cosmos/attributes.md b/docs/Examples/cosmos/attributes.md index 8c04c83..44dce65 100644 --- a/docs/Examples/cosmos/attributes.md +++ b/docs/Examples/cosmos/attributes.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Attribtues API provides all the details regarding event attributes from Cosmos network. -## Get Attributes of Recent Events +## Get Recent Cosmos Event Attributes ``` { @@ -43,7 +43,7 @@ Our Cosmos Attribtues API provides all the details regarding event attributes fr The query retrieves event attribute information from the Cosmos blockchain, including attribute names, block height and timestamp, event types, message senders and types, transaction hash, signer's address, and attribute values. The results are sorted based on block timestamp in descending order. -## Filter Attributes by Event Type +## Filter Cosmos Event Attributes by Event Type ``` { @@ -81,7 +81,7 @@ The query retrieves event attribute details from the Cosmos blockchain, specific The query provides information about attribute names, block height, block timestamp, event type, message senders and types, transaction hash, signer's address, and attribute values. This offers insights into recent `proposal_vote` event attributes on the Cosmos network. -## Get Count of Attributes +## Count Cosmos Event Attributes ``` { diff --git a/docs/Examples/cosmos/blocks.md b/docs/Examples/cosmos/blocks.md index 5041ef1..f110ab6 100644 --- a/docs/Examples/cosmos/blocks.md +++ b/docs/Examples/cosmos/blocks.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Blocks API provides all the information related to blocks produced on Cosmos network. -## Retrieve the 10 Most Recent Blocks +## Get Ten Most Recent Cosmos Blocks ``` { @@ -34,7 +34,7 @@ Our Cosmos Blocks API provides all the information related to blocks produced on This query retrieves details about the 10 most recent blocks on the Cosmos blockchain. It includes information like block hash, header, height, metadata, block proposer's address, and timestamp for each block. The results are ordered by timestamp in descending order. -## Filter Blocks Based on Block Proposer +## Get Cosmos Blocks Filtered by Block Proposer ``` { @@ -59,7 +59,7 @@ This query retrieves details about the 10 most recent blocks on the Cosmos block This query fetches details about the 10 most recent blocks on the Cosmos blockchain. It specifically filters the results to include only blocks proposed by the address `13EE3F05F20C6AD8FD27CBEF33DD61D5F99ECF6F`. It retrieves information such as the block hash, block height, address of the block proposer, and timestamp for each of these filtered blocks. The results are sorted based on the timestamp in descending order. -## Count Blocks Associated with a Specific Block Proposer +## Count Cosmos Blocks by Block Proposer ``` { diff --git a/docs/Examples/cosmos/coinpath.md b/docs/Examples/cosmos/coinpath.md index 050e78d..1868f2c 100644 --- a/docs/Examples/cosmos/coinpath.md +++ b/docs/Examples/cosmos/coinpath.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Coinpath API provides comprehensive information about money flow of addresses on the Cosmos blockchain. -## Explore Destination of Funds from a Specific Address +## Trace Cosmos Coinpath Outflows from an Address ``` { @@ -46,7 +46,7 @@ Our Cosmos Coinpath API provides comprehensive information about money flow of a This query retrieves a list of coinpath transactions initiated from a specific initial address (`cosmos1ypejmkpfqrqmv5w7cscq874xf8rlggq7w44rsw`) after a certain date (`2023-08-07`). The query limits the results to 10 transactions and orders them by timestamp in descending order. For each transaction, it provides details such as the transferred amount in USD, block height, timestamp, currency information, sender and receiver addresses, transaction hash, and value. -## Investigate Relationship Between Two Addresses +## Trace Cosmos Coinpath Flow Between Two Addresses ``` { @@ -87,7 +87,7 @@ This query explores the relationship between two specific addresses (`initialAdd For each transaction, the query provides details like the transferred amount in USD, block height, timestamp, currency information, sender and receiver addresses, transaction hash, and value. By analyzing these transactions, users can gain insights into the flow of funds between the two addresses and understand their financial interactions. -## Retrieve Transactions Exceeding a Certain Value from a Specific Address +## Get Cosmos Coinpath Transfers Above Minimum Amount Between Addresses ``` { diff --git a/docs/Examples/cosmos/messages.md b/docs/Examples/cosmos/messages.md index 5476fb5..fb257b9 100644 --- a/docs/Examples/cosmos/messages.md +++ b/docs/Examples/cosmos/messages.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Messages API provides all the information related to messages generated on Cosmos Blockchain. -## Retrieve Messages within a Specific Block +## Get Cosmos Messages in a Specific Block ``` { @@ -32,7 +32,7 @@ Our Cosmos Messages API provides all the information related to messages generat This query retrieves messages from a specific block with the height of 16494924 in the Cosmos blockchain. It includes the index of the message, the JSON content of the message body, sender(s) of the message, success status of the associated transaction, the transaction hash, the address of the transaction signer, and the type of the message. -## Count Types of Messages Sent by a Specific Address +## Get Latest Cosmos Messages from a Transaction Signer ``` { @@ -66,7 +66,7 @@ This query retrieves messages from a specific block with the height of 16494924 This query retrieves messages from the Cosmos blockchain where transactions signed by the address "cosmos1alprdufsxvxauwcsh08hjpzsqc8elwlq3evztg". The query includes information such as the block height and timestamp, message index, JSON content of the message, sender(s) of the message, success status of the transaction, transaction hash, the address of the transaction signer, and the type of the message. The result is limited to the latest 10 messages. -## Explore Messages of a Specific Type +## Count Unique Cosmos Message Types in a Block ``` { diff --git a/docs/Examples/cosmos/transactions.md b/docs/Examples/cosmos/transactions.md index f2c0468..a309d3c 100644 --- a/docs/Examples/cosmos/transactions.md +++ b/docs/Examples/cosmos/transactions.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Transactions API provides information related to transactions created on Cosmos Blockchain. -## Retrieve Specific Transaction +## Get Cosmos Transaction by Transaction Hash ``` { @@ -41,7 +41,7 @@ Our Cosmos Transactions API provides information related to transactions created This query retrieves transaction details based on a specific transaction hash. It fetches information such as the block's height and timestamp where the transaction is included, the transaction fee, fee currency details including its name and address, gas used, index of the transaction, raw transaction data, signer's address, and the transaction type. -## Fetch Transactions from a Specific Address on a Given Date +## Get Cosmos Transactions by Signer and Date ``` { diff --git a/docs/Examples/cosmos/transfers.md b/docs/Examples/cosmos/transfers.md index 2d02215..73addfd 100644 --- a/docs/Examples/cosmos/transfers.md +++ b/docs/Examples/cosmos/transfers.md @@ -8,7 +8,7 @@ keywords: [Cosmos API examples, Cosmos GraphQL queries, Bitquery] Our Cosmos Transfers API provides all the information about token transfers happened on Cosmos Blockchain. -## Get Transfers by a Specific Signer, Arranged by Timestamp and Value +## Get Cosmos Transfers by Signer Sorted by Time and Value ``` { @@ -45,7 +45,7 @@ Our Cosmos Transfers API provides all the information about token transfers happ This query retrieves the latest transfers involving a specific transaction signer's address. It orders the results by both the timestamp and the value of the transfers in descending order, limiting the output to the top 10 transfers. For each transfer, it provides information such as the block height, timestamp, currency details, receiver's address, sender's address, transaction hash, transfer type, and transfer value. -## Fetch the Most Recent Transfer of a Specific Currency +## Get Recent Cosmos Transfers for a Specific Currency ``` { diff --git a/docs/Examples/cross-chain/cross-chain-api.md b/docs/Examples/cross-chain/cross-chain-api.md index 464186f..c57d4d9 100644 --- a/docs/Examples/cross-chain/cross-chain-api.md +++ b/docs/Examples/cross-chain/cross-chain-api.md @@ -10,14 +10,14 @@ In this section we see how to use Bitquery APIs to get information across multip # Table of Contents -1. [Balance of a Wallet](#balance-of-a-Wallet) -2. [Token Transfers](#token-transfers-tracking) -3. [Cross-Chain Trade Insights](#cross-chain-trade) -4. [Universal Token Tracking](#universal-token-tracking) +1. [Get Multi-Chain Wallet Balance Across Networks](#get-multi-chain-wallet-balance-across-networks) +2. [Track Token Transfers Across Multiple Chains](#track-token-transfers-across-multiple-chains) +3. [Get Multi-Chain DEX Trade Insights for One Wallet](#get-multi-chain-dex-trade-insights-for-one-wallet) +4. [Aggregate Multi-Chain USDT Transfer Metrics by Network](#aggregate-multi-chain-usdt-transfer-metrics-by-network) - + -## Balance of a Wallet +## Get Multi-Chain Wallet Balance Across Networks Use this query to retrieve address balances across multiple blockchains in one query. Set the wallet address in the `address` filter. @@ -230,9 +230,9 @@ query ($address: String!) { } ``` - + -## Token Transfers Tracking +## Track Token Transfers Across Multiple Chains With this query you can track token transfers across different chains for any address. Set the wallet whose movements you want to track in the `address` filter. Using the `any` clause, we get transfers were the address was either a sender or reciever. @@ -447,9 +447,9 @@ query ($address: String!) { } ``` - + -## Cross-Chain Trade Insights +## Get Multi-Chain DEX Trade Insights for One Wallet The below query gives you insights into token trades spanning various blockchains. Simply set the wallet address in the `address` parameter. Adjust the `from ` and `to` periods accordingly. @@ -579,9 +579,9 @@ fragment TradeInfo on EthereumDexTrades { ``` - + -## Universal Token Tracking +## Aggregate Multi-Chain USDT Transfer Metrics by Network The below query gives you stats on tokens across chains including sender/receiver count, first and last date of token transfers and the average amount transferred. diff --git a/docs/Examples/dexTrades/dex-pool-api.md b/docs/Examples/dexTrades/dex-pool-api.md index 55199c6..8059077 100644 --- a/docs/Examples/dexTrades/dex-pool-api.md +++ b/docs/Examples/dexTrades/dex-pool-api.md @@ -8,7 +8,7 @@ keywords: [DEX API examples, DEX GraphQL queries, Bitquery] In this section, we will look at some examples regarding DEX Pools data. -## Latest Pair Created +## List Latest Ethereum PairCreated Events With Token Zero Addresses The following GraphQL query retrieves data on the latest 50 PairCreated events on the Ethereum network, along with their associated block timestamp, token0 address and name. It uses the ethereum network and the arguments from the query above to filter events based on specific criteria. diff --git a/docs/Examples/dexTrades/dex-trading-data-api.md b/docs/Examples/dexTrades/dex-trading-data-api.md index 9a5d9ca..8d3644d 100644 --- a/docs/Examples/dexTrades/dex-trading-data-api.md +++ b/docs/Examples/dexTrades/dex-trading-data-api.md @@ -59,7 +59,7 @@ For example, Uniswap is an exchange and a protocol. Uniswap protocol deployed by If Bitquery index a protocol (ex - Uniswap v2 protocol), therefore any other exchange which is implemented this Uniswap V2, we have already indexed them. We might not be naming them, but you can get their trades using [**this API**](https://ide.bitquery.io/query/pzizr56shpq6wQrX), by simply replacing exchangeAddress with that exchange's factory address. -## Trades for a specific time on Ethereum +## Get Ethereum DEX Trades for a Full UTC Time Window To get trades from the Ethereum blockchain for a specific time, please use the following API. @@ -111,7 +111,7 @@ To get trades from the Ethereum blockchain for a specific time, please use the f } ``` -## Trades for an DEX Exchange +## Get Uniswap Ethereum DEX Trades by Factory Contract Addresses To get trades for specific exchange you can you use `exchangeName` (Not recommended) or `exchangeAddress` (recommended). In the following example we are getting, Uniswap's trades. To showcase, we have used both exchangeName and exchangeAddress. In exchange address we have entered factory address of Uniswap v1, v2 and V3 because Uniswap is one exchange with 3 different version deployemnt. @@ -172,7 +172,7 @@ To get trades for specific exchange you can you use `exchangeName` (Not recommen } ``` -## Trades for a protocol +## Get Ethereum DEX Trades for Uniswap v3 Protocol Across Exchanges Using `protocol` filter you can get trades for any protocol such as Uniswap v3. In the following query we are getting trades for Uniswap v3 protocol, regardless the exchange. In other words, we are getting trades from all exchange that are using Uniswap v3. @@ -226,7 +226,7 @@ Using `protocol` filter you can get trades for any protocol such as Uniswap v3. } ``` -## Price of multiple tokens in 1 API call +## Get Ethereum DEX Token Prices Against WETH in One Query If you want to get prices of multiple DEX tokens against a sell currency (ex - WETH) you can use follow query. ``` @@ -268,7 +268,7 @@ If you want to get prices of multiple DEX tokens against a sell currency (ex - W } ``` -## Trades of a wallet address +## Get Ethereum DEX Trades Where the Transaction Sender Is a Wallet You can use `txSender` to see the trades where transaction sender is specific address. @@ -331,7 +331,7 @@ You can use `txSender` to see the trades where transaction sender is specific ad } ``` -## Trade for a token +## Get Ethereum DEX Trades for the SHIB Token as Base Currency To get trades for a token you can either use buy/sell currency filter or base/quote currency filter. In the following example we are getting trades for [SHIB token](https://explorer.bitquery.io/ethereum/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce). @@ -394,7 +394,7 @@ https://ide.bitquery.io/Trades-for-SHIB-token } ``` -## All pairs of a token +## List Top Ethereum DEX Quote Pairs for WETH by Trade Count To get all pairs for a give token you can use following api. @@ -433,7 +433,7 @@ To get all pairs for a give token you can use following api. } ``` -## Trades for a trading pair +## Get Ethereum DEX Trades for WOJAK Versus WETH Currency Pair You can use both buy/sell or Base/Quote currency to get trades for a given currency pair. In the following example we are getting trades for [WOJAK](https://explorer.bitquery.io/ethereum/token/0x5026f006b85729a8b14553fae6af249ad16c9aab) / [WETH](https://explorer.bitquery.io/ethereum/token/0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2) currency pair. @@ -499,7 +499,7 @@ https://ide.bitquery.io/Trades-for-a-trading-pair-on-Ethereum } ``` -## Trades for a pair token (Pool token) +## Get Ethereum DEX Trades for a Liquidity Pool Contract Address To get trades for pair tokens, you should use buy/sell; in the case of using Base/Quote, it will replicate the result. For example, if there is a swap A <-> B, using Base/Quote, it will give two results in one A as the base currency and in another B as the quote currency. @@ -557,7 +557,7 @@ For example, if there is a swap A <-> B, using Base/Quote, it will give two resu } ``` -## Latest USD price of a token +## Derive Ethereum Token USD Price From Latest ERUTA Versus WETH Trade As we already know, USD doesn't exist on the blockchain. Additionally, there will be tokens that do not have pairs with USDT or other stablecoins. In this case, getting USD prices becomes [price index problem](https://bitquery.io/blog/dex-price-index). However, we have USD pricing for several tokens, and actually, you can derive the USD price of tokens using it. In the following example, we are getting the latest trade for ERUTA/WETH trading pair because the latest trade = latest price. In this case, we have the USD price of WETH. Therefore, we are deriving the ERUTA USD price by dividing `sell_amount_usd` by `buyAmount`. @@ -600,7 +600,7 @@ This is a very effective way to get the USD price for assets that are traded aga } ``` -## Latest Trading pairs of an exchange +## List New BSC PancakeSwap PairCreated Events From the Factory Contract To get latest pairs of an exchange, we can use Event APIs, let's get latest pairs by tracking `PairCreated` event from the [PancakeSwap factory contract](https://explorer.bitquery.io/bsc/smart_contract/0xbcfccbde45ce874adcb698cc183debcf17952812/events) on BNB chain. @@ -641,7 +641,7 @@ To get latest pairs of an exchange, we can use Event APIs, let's get latest pair } ``` -## Querying an exchange not listed on Bitquery +## Get BSC DEX Trades Using an Unlisted Exchange Factory Address To get an exchange which is not listed on Bitquery, you just need to use their factory address. In the following example, we do not have GIBX Swap listed on our explorer, but we do index GIBX, and you can get it's trade using GIBX Swap factory address. @@ -697,7 +697,7 @@ https://ide.bitquery.io/GIBX-trades } ``` -## Liquidity in a pool token +## Read Ethereum USDC and WETH Balances Inside a Uniswap Pool Contract To see liquidity in pair tokens, we need to know two things, @@ -734,7 +734,7 @@ Now we will use the balance API to get the balance of WETH and USDC tokens in ou } ``` -## Liquidity Removed and Added in a pool token +## Track Ethereum Mint and Burn Events for USDC WETH Pool Liquidity To track liquidity details for a pair token we can track `Mint` and `Burn` events. In the following example we are tracking lquidity add and remove for USDC/WETH token pair [0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640](https://explorer.bitquery.io/ethereum/smart_contract/0x88e6a0c2ddd26feeb64f039a2c41296fcb3f5640/events) @@ -784,7 +784,7 @@ To track liquidity details for a pair token we can track `Mint` and `Burn` event } ``` -## Currencies in pair token +## Resolve Buy and Sell Currencies for an Ethereum Pool Smart Contract To check currency pair in a Pool token, you can use following API. @@ -816,7 +816,7 @@ To check currency pair in a Pool token, you can use following API. } ``` -## Get Number of Trades for a Particular Uniswap Pool Above Certain Value +## Count Ethereum DEX Trades Above a USD Threshold for a Pool We can get number of trades for a uniswap pool above particular value using `count` field and passing value which we want to `tradeAmountUSD` filter along with address of that pools smart contract passed to `smartContractAddress` field. @@ -836,7 +836,7 @@ Check query [here](https://ide.bitquery.io/Ethereum-Get-Count-of-Trades-Above-Ce }``` ```` -## Get 24H Volume of a Uniswap Pool +## Get Rolling Twenty Four Hour Ethereum Pool Trade Volume We can get volume of Uniswap pool using `tradeAmount` field. It gives us trade amount in USD using `timeInterval` field we can set interval to 24H. We have also set limit to 30 days so we will get 24H volume for last 30 days. @@ -860,7 +860,7 @@ Check query [here](https://ide.bitquery.io/Ethereum-24H-Trading-Value-of-a-Pool- } ``` -## Total Unique Tokens Traded in a Day +## Count Unique Ethereum DEX Buy and Sell Tokens on One Date This query below will return the count of unique tokens bought and sold in all DEXs on the Ethereum network on a particular date. To achieve this we will be using the `uniq` filter and aliasing `count(uniq: buy_currency)` and `count(uniq: sell_currency)` diff --git a/docs/Examples/dexTrades/ohlc.md b/docs/Examples/dexTrades/ohlc.md index f64ae3b..b53cd44 100644 --- a/docs/Examples/dexTrades/ohlc.md +++ b/docs/Examples/dexTrades/ohlc.md @@ -10,7 +10,7 @@ Using our APIs, you can also get [OHLC](https://en.wikipedia.org/wiki/Open-high- The OHLC API allows you to retrieve OHLC data for a given asset pair and time period. -## OHLC Hourly Data for a Token Pair +## Get Ethereum DEX OHLC for DAI and Quote in Ten Minute Intervals This query gets OHLC data for the period from 5pm to 6pm UTC on July 9, 2023,, where the base currency is DAI (0xd0b3a986fff305854a7238a8e099cce1ced01a3d) and the quote currency is USDC (0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2) in 10 minute intervals. @@ -55,7 +55,7 @@ This query gets OHLC data for the period from 5pm to 6pm UTC on July 9, 2023,, w The `timeInterval` field indicates time interval for which the data is aggregated. -## Filtering Outliers in OHLC +## Get Uniswap Ethereum WETH USDT OHLC With Outlier Trade Filters In this example, we are getting OHLC prices by aggregating price data at run time. Additionally, we are using `priceAsymmetry` and `tradeAmountUsd` to filter out trades with abnormal prices. Read more about priceAsymmetry [here](https://docs.bitquery.io/v1/docs/building-queries/FAQ#how-to-use-priceasymmetry-to-filter-anomalies-and-outliers-in-trades-) diff --git a/docs/Examples/filecoin/messages.md b/docs/Examples/filecoin/messages.md index 4fc1513..8db7662 100644 --- a/docs/Examples/filecoin/messages.md +++ b/docs/Examples/filecoin/messages.md @@ -8,7 +8,7 @@ keywords: [Filecoin API examples, Filecoin GraphQL queries, Bitquery] In this section we will see some example queries that track different stages in a storae deal flow on Filecoin. For further details on Storage deals on Filecoin, refer to their [official documentation](https://docs.filecoin.io/storage-providers/filecoin-deals/storage-deals). -## PublishStorageDeals +## Count Filecoin PublishStorageDeals Messages to f05 in a Date Range `PublishStorageDeals` message is added to chain when a new set of storage deals are published. Query to track published storage deals within a specified date range: @@ -33,7 +33,7 @@ query ($network: FilecoinNetwork!) { (Run query here: [PublishStorageDeals](https://ide.bitquery.io/Weekly-PublishStorageDeals-Messages-Count)) -## Slashing +## List Filecoin Slashing Burn Transfers From a Storage Provider Slashing is "a set of penalties which are to be paid by storage providers if they fail to provide sector reliability or decide to voluntarily exit the network". Below is the query to retrieve storage slashing messages: @@ -68,7 +68,7 @@ Below is the query to retrieve storage slashing messages: (Run query here: [Slashings](https://ide.bitquery.io/Slashing-for-a-Provider-on-Filecoin)) -## RemoveExpiredAllocations: +## List Filecoin RemoveExpiredAllocations Burn Transfers From a Provider The below query helps track messages when expired DataCap allocations are removed and reclaim those DataCap tokens back to the client. @@ -102,7 +102,7 @@ The below query helps track messages when expired DataCap allocations are remove (Source: [RemoveExpiredAllocations](https://ide.bitquery.io/RemoveExpiredAllocations-Filecoin)) -## Storage Precommit +## List Filecoin PreCommit Sector Messages on a Calendar Date ``` query MyQuery { @@ -134,7 +134,7 @@ query MyQuery { (Source: [PreCommit-Storage](https://ide.bitquery.io/PreCommit-Storage-Messages--day)) -## Declarefaults +## List Filecoin DeclareFaults Messages for a Receiver Actor ``` query MyQuery { diff --git a/docs/Examples/hedera/hedera-address.md b/docs/Examples/hedera/hedera-address.md index 83cefab..5a3c2e2 100644 --- a/docs/Examples/hedera/hedera-address.md +++ b/docs/Examples/hedera/hedera-address.md @@ -8,7 +8,7 @@ keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] In this section we will see how to get information on wallets on Hedera. -## Latest Balance of an Address +## Get Latest Hedera Account Balance in HBAR This query retrieves the latest balance of an address on Hedera. diff --git a/docs/Examples/hedera/hedera-io.md b/docs/Examples/hedera/hedera-io.md index 7ba9418..27b1250 100644 --- a/docs/Examples/hedera/hedera-io.md +++ b/docs/Examples/hedera/hedera-io.md @@ -9,7 +9,7 @@ keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] In this section we will see some examples on tracing funds from/to an hedera address. -## Most Transfered Token +## Rank Hedera Inputs by Most Transferred Token Count You can run the query [here](https://ide.bitquery.io/Hedera-inputs) @@ -34,7 +34,7 @@ This will give you the top tokens based on the count of inputs by fetching the i ``` -## Latest Inputs to an Address +## List Latest Hedera Inputs to an Account With Fees and Memo To find the latest inputs (incoming transactions) to a specific Hedera address, you can use the following GraphQL query. It fetches the latest 10 inputs (transactions) to the address `0.0.6187183`, sorted by the most recent timestamp. @@ -80,7 +80,7 @@ query MyQuery { ``` -## Latest Outputs to an Address +## List Latest Hedera Outputs to an Account With Fees and Memo To find the latest outputs (outputs transactions) to a specific Hedera address, you can use the following GraphQL query. It fetches the latest 10 inputs (transactions) to the address `0.0.6187183`, sorted by the most recent timestamp. diff --git a/docs/Examples/hedera/hedera-messages.md b/docs/Examples/hedera/hedera-messages.md index 6ef3721..984b759 100644 --- a/docs/Examples/hedera/hedera-messages.md +++ b/docs/Examples/hedera/hedera-messages.md @@ -9,7 +9,7 @@ keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] In this section we will see how to get information on messages on Hedera. -## Latest Messages +## List Latest Hedera Consensus Service Messages on a Date This query retrieves the latest messages on the Hedera network. diff --git a/docs/Examples/hedera/hedera-transactions.md b/docs/Examples/hedera/hedera-transactions.md index c21e50e..f854baa 100644 --- a/docs/Examples/hedera/hedera-transactions.md +++ b/docs/Examples/hedera/hedera-transactions.md @@ -9,7 +9,7 @@ keywords: [Hedera API examples, Hedera GraphQL queries, Bitquery] In this section we will see how to get information on transactions on Hedera. -## Latest Transactions +## List Latest Hedera Consensus Transactions on a Calendar Date This query retrieves the latest transactions on the Hedera network. You can run the query [here](https://ide.bitquery.io/Latest-Hedera-Transactions) @@ -48,7 +48,7 @@ query MyQuery { ``` -## Latest Transactions From an Address +## List Latest Hedera Transactions Paid From a Payer Account This query retrieves the latest transactions from a specific address on the Hedera network. @@ -92,7 +92,7 @@ query MyQuery { ``` -## Top Transaction Failures on Hedera +## Rank Hedera Failed Transactions by Error Result Count This query retrieves the top transaction failures on the Hedera network and helps in identifying the most common reasons for transaction failures. @@ -120,7 +120,7 @@ query MyQuery { - **result.name**: Describes the error that caused the transaction to fail, such as "INSUFFICIENT_BALANCE". - **result.id**: The unique identifier for the error. -## Latest Smart Contract Calls on Hedera +## List Latest Hedera Smart Contract Calls With Memos Since a Date Smart contracts calls in Hedera help you identify the calls made during the transaction including details on whether the tx was a swap or transfer and so on. The `memo` field will have details about the transaction for example ` "memo": "HashPack swap DOVU to HBAR",` The below query gets the latest calls for a particular date. diff --git a/docs/Examples/ripple/balances.mdx b/docs/Examples/ripple/balances.mdx index 7bb1b40..9cb6793 100644 --- a/docs/Examples/ripple/balances.mdx +++ b/docs/Examples/ripple/balances.mdx @@ -4,7 +4,7 @@ Ripple Balance API provides all details regarding balances on Ripple Blockchain. import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Historical Balance of an address on Ripple +## Get Historical XRP Ledger Account Balances for a Ripple Address We are using the below query to get all historical balance of an address `rs9ineLqrCzeAGS1bxsrW8x2n3bRJYAh3Q` on Ripple Blockchain. You can find the query [here](https://ide.bitquery.io/historical-balances-of-a-ripple-address). diff --git a/docs/Examples/ripple/nft_token_offers.md b/docs/Examples/ripple/nft_token_offers.md index b876cd5..7958853 100644 --- a/docs/Examples/ripple/nft_token_offers.md +++ b/docs/Examples/ripple/nft_token_offers.md @@ -8,7 +8,7 @@ keywords: [Ripple API examples, XRP GraphQL queries, Bitquery] Ripple NFT Token Offers API provides all details regarding NFT Token offers on Ripple Blockchain. Below are some examples of `nftokenOffers` API: -## Get NFT Token Offers from a specific Transaction Sender +## Get XRP Ledger NFT Token Offers from a Specific Transaction Sender We are using the below query to get the NFT Token Offers from a particular address `rBEARbo4Prn33894evmvYcAf9yAQjp4VJF` on Ripple Blockchain. You can find the query [here](https://ide.bitquery.io/NFT-Token-offers-API-on-Ripple-blockchain). diff --git a/docs/Examples/ripple/payments.mdx b/docs/Examples/ripple/payments.mdx index f3c9f2d..de8ad09 100644 --- a/docs/Examples/ripple/payments.mdx +++ b/docs/Examples/ripple/payments.mdx @@ -4,7 +4,7 @@ Ripple Payments API provides all details regarding payments on Ripple Blockchain import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Latest Payments on Ripple +## Get Latest XRP Ledger Payments on the Ripple Network We are using the below query to get the latest payments on Ripple Blockchain. You can find the query [here](https://ide.bitquery.io/Latest-payments-on-ripple-blockchain). @@ -50,7 +50,7 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date } ``` -## Get Payments of an Address on Ripple +## Get XRP Ledger Payments Involving a Specific Ripple Address We are using the below query to get the payments of a specific address `rLR5BTsGcnMp5SwUzX1V9VCTbN1hayH61R` on Ripple Blockchain. You can find the query [here](https://ide.bitquery.io/Payments-of-an-address-on-ripple). diff --git a/docs/Examples/ripple/trades.mdx b/docs/Examples/ripple/trades.mdx index ae4a495..b915421 100644 --- a/docs/Examples/ripple/trades.mdx +++ b/docs/Examples/ripple/trades.mdx @@ -4,7 +4,7 @@ Ripple Trades API provides all details regarding trades on Ripple Blockchain. Be import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Trades for a currency on Ripple +## Get XRP Ledger DEX Trades for a Currency Pair on Ripple We are using the below query to get the trades for a specific currency `CNY`. You can find the query [here](https://ide.bitquery.io/trades-for-CNY-on-ripple). diff --git a/docs/Examples/ripple/transfers.mdx b/docs/Examples/ripple/transfers.mdx index 696aae9..31bcf92 100644 --- a/docs/Examples/ripple/transfers.mdx +++ b/docs/Examples/ripple/transfers.mdx @@ -4,7 +4,7 @@ Ripple Transfers API provides all details regarding transfers on Ripple Blockcha import VideoPlayer from "../../../src/components/HomepageFeatures/videoplayer.js"; -## Get Transfers for a currency on Ripple +## Get XRP Ledger Transfers for a Currency on the Ripple Network We are using the below query to get all types of transfers for a specific currency `CNY`. You can find the query [here](https://ide.bitquery.io/All-types-of-transfers-for-tokens). @@ -63,7 +63,7 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date } ``` -## Total Transfers done by a Ripple address +## Aggregate XRP Ledger Transfer Counts by Currency for a Ripple Address We are using the below query to get the total transfers done by a specific address `rs9ineLqrCzeAGS1bxsrW8x2n3bRJYAh3Q`. You can find the query [here](https://ide.bitquery.io/Total-transfers-done-by-a-ripple-address). @@ -107,7 +107,7 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date } ``` -## All Historical Transfers of an individual address +## Get Historical XRP Ledger Transfers for a Ripple Address We are using the below query to get all the historical transfers done by a specific address `rs9ineLqrCzeAGS1bxsrW8x2n3bRJYAh3Q`. You can find the query [here](https://ide.bitquery.io/All-historical-transfers-of-an-individual-address). diff --git a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md index 9eaca89..24dd04c 100644 --- a/docs/Examples/smartcontractCalls/smart-contract-calls-api.md +++ b/docs/Examples/smartcontractCalls/smart-contract-calls-api.md @@ -8,7 +8,7 @@ keywords: [smart contract API examples, GraphQL queries, Bitquery] Our Smart contract call API allows you access to parsed smart contract calls and arguments for all the blockchains we support. -## All Smart contract calls for a blockchain +## Get Recent Ethereum Smart Contract Calls with Callers and Arguments You can use our SmartContractCalls to get contract calls for any blockchain. In the following example, we are getting smart contract calls for Ethereum with details like arguments, transaction, caller, and [calldepth](https://community.bitquery.io/t/bitquery-trace-api/1556). @@ -55,7 +55,7 @@ You can use our SmartContractCalls to get contract calls for any blockchain. In } ``` -## All Smart contract call for a specific contract +## Get Ethereum Smart Contract Calls for One Contract Address [Open this query on IDE](https://ide.bitquery.io/Calls-for-a-specific-ethereum-smart-contract) @@ -94,7 +94,7 @@ You can use our SmartContractCalls to get contract calls for any blockchain. In } ``` -## List of calls of a smart contract +## List Latest Ethereum Smart Contract Calls Grouped by Method Name To check the list of methods (calls) done on a smart contract you can use following api. @@ -140,7 +140,7 @@ To check the list of methods (calls) done on a smart contract you can use follow } ``` -## Specific method call from a specific contract +## Get Ethereum getReserves Calls from a Specific Caller Contract To check the specific method call from a specific smart contract you can use the api below. @@ -183,7 +183,7 @@ To check the specific method call from a specific smart contract you can use the ``` -## Method calls by specific address +## Get Ethereum Smart Contract Calls Where One Address Is Caller To check method calls by a specific [smart contract address](https://explorer.bitquery.io/ethereum/smart_contract/0x1a0ad011913a150f69f6a19df447a0cfd9551054/calls_contracts), you can use following API. @@ -228,7 +228,7 @@ To check method calls by a specific [smart contract address](https://explorer.bi } ``` -## Smart contract arguments API +## List BSC Smart Contract Parsed Arguments by Block and Transaction ```graphql { @@ -312,7 +312,7 @@ To filter specific argument, please use following API. Our v1 APIs support Argument Filtering, however we would rather suggest using V2 APIs for this. They are much more powerful in arguments, allowing argument aggregation and filtering. -## Blacklist Calls on a Token +## Get Ethereum Blacklist Smart Contract Calls for a Token Contract To restrict certain addresses from performing specific actions within your smart contract, you can utilize the blacklist functionality. The query below utilizes the `smartContractMethod: {is: "blacklist"}` to fetch transactions where an address was blacklisted. You can run the query [here](https://ide.bitquery.io/PEPE-Blacklist-calls) diff --git a/docs/Examples/smartcontractEvents/smart-contract-events-api.md b/docs/Examples/smartcontractEvents/smart-contract-events-api.md index 7775634..891adcc 100644 --- a/docs/Examples/smartcontractEvents/smart-contract-events-api.md +++ b/docs/Examples/smartcontractEvents/smart-contract-events-api.md @@ -8,7 +8,7 @@ keywords: [smart contract API examples, GraphQL queries, Bitquery] Our Smart contract event API allows you access parsed smart contract events and arguments for all the blockchains we support. -## All Smart contract event for a blockchain +## Get Recent Ethereum Smart Contract Events with Parsed Arguments [Open this query on IDE](https://ide.bitquery.io/Smart-contract-event-API_1_1) @@ -50,7 +50,7 @@ Our Smart contract event API allows you access parsed smart contract events and } ``` -## All Smart contract event for a specific contract +## Get Ethereum Smart Contract Events for One Pool Contract Address To check specific smart contract events, you need to mention the smart contract address. For example, in the following query, we are getting [AAVE's V3 Pool smart contract](https://explorer.bitquery.io/ethereum/smart_contract/0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2/events) events. @@ -97,7 +97,7 @@ To check specific smart contract events, you need to mention the smart contract } ``` -## Specific Smart contract event from a contract +## Get Ethereum Repay Events from Aave V3 Pool Smart Contract We can also get specific event for a given smart contract using our SmartContractEvent API. For example in the following query are getting `Repay` event from the [AAVE's V3 Pool smart contract](https://explorer.bitquery.io/ethereum/smart_contract/0x87870bca3f3fd6335c3f4ce8392d69350b4fa4e2/events). @@ -145,7 +145,7 @@ We can also get specific event for a given smart contract using our SmartContrac } ``` -## Get Latest Uniswap V2 Factory contract PairCreated Events +## Get Latest Ethereum Uniswap V2 PairCreated Events from Factory Contract Using `smartContractEvents` API, we can filter `PairCreated` event emitted from Uniswap V2 Factory smart contract. [0x5C69bEe701ef814a2B6a3EDD4B1652CB9cc5aA6f](https://explorer.bitquery.io/ethereum/smart_contract/0x5c69bee701ef814a2b6a3edd4b1652cb9cc5aa6f) is Uniswap V2 Factory Contract. Here is [the query](https://ide.bitquery.io/Ethereum-Get-List-of-Pairs-Created-on-Uniswap) which you can check in the IDE. @@ -177,7 +177,7 @@ Using `smartContractEvents` API, we can filter `PairCreated` event emitted from To get events from Uniswap V2, we are filtering using address of the factory smart contract using `smartContractAddress` field. As we want to get `PairCreated` event, we used `smartContractEvent` field and passed name of the event to it. Lastly, we want latest event so we put those in desceding order uisng timestamp when event was emitted. -## Smart contract arguments API +## Get BSC PancakeSwap PairCreated Event Arguments from Factory Address We have an `arguments` API, which provides parsed smart contracts. Let's get the latest pair created from PancakeSwap by getting `PairCreated` events as shown below. Additionally, you can write another API in a different way using `any`; here is [an example](https://ide.bitquery.io/Latest-Pair-Created-on-Pancake-Swap_1_1_1). diff --git a/docs/Examples/stellar/stellar-address-api.md b/docs/Examples/stellar/stellar-address-api.md index 9a8b75e..07d1fdd 100644 --- a/docs/Examples/stellar/stellar-address-api.md +++ b/docs/Examples/stellar/stellar-address-api.md @@ -9,7 +9,7 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] This API allows you to retrieve detailed information about Stellar wallet addresses, including their balances and token holdings. -## Latest Balance of a Wallet +## Get Stellar Wallet Balance In the below query we will retrieve the latest balance of a specific Stellar wallet address. diff --git a/docs/Examples/stellar/stellar-effects-api.md b/docs/Examples/stellar/stellar-effects-api.md index 86bca6a..34c5eaa 100644 --- a/docs/Examples/stellar/stellar-effects-api.md +++ b/docs/Examples/stellar/stellar-effects-api.md @@ -8,7 +8,7 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] All changes on the ledger are recorded as effects including changes after transactions, trades and so on. In this section we will see how to use Bitquery API to get effects information. -## Latest Effects +## Get Latest Stellar Network Effects This query retrieves the latest effects from the Stellar ledger on a particular date. Effects represent state changes on the ledger and can include various types of operations, such as account creation, payments, and trades. @@ -40,7 +40,7 @@ query MyQuery { ``` -## Search a Particular Effect +## Filter Stellar Ledger Effects by Effect Type This query retrieves effects of a specific type using `effect: {is:}` , such as "account_credited", which indicates that an account was credited with an asset. You can run the query [here](https://ide.bitquery.io/Latest-Account-Credit-Effect-on-Stellar) diff --git a/docs/Examples/stellar/stellar-liquiditypool-api.md b/docs/Examples/stellar/stellar-liquiditypool-api.md index c6ea827..74fe030 100644 --- a/docs/Examples/stellar/stellar-liquiditypool-api.md +++ b/docs/Examples/stellar/stellar-liquiditypool-api.md @@ -8,7 +8,7 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] This API allows you to access and analyze effects from Stellar's liquidity pools. Effects are specific changes that occur within the ledger due to operations performed on the liquidity pools. -## Latest Pool Effects for a Particular Pool +## Get Latest Stellar Liquidity Pool Effects for One Pool The below query gets the latest effects for a specific liquidity pool, including details about the operation, the transaction, and the pool itself. @@ -45,7 +45,7 @@ query MyQuery { ``` -## Latest Liquidity Pool Deposits +## Get Latest Stellar Liquidity Pool Deposit Effects The query below fetches the most recent deposit effects into all liquidity pools. This query provides details about the deposit operation, including the amount, pool details, transaction hash, and currency. You can run the query [here](https://ide.bitquery.io/Latest-Pool-Deposits) diff --git a/docs/Examples/stellar/stellar-payments-api.md b/docs/Examples/stellar/stellar-payments-api.md index d693cb2..9592383 100644 --- a/docs/Examples/stellar/stellar-payments-api.md +++ b/docs/Examples/stellar/stellar-payments-api.md @@ -8,7 +8,7 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] This API enables you to access and analyze payment transactions on the Stellar network, providing detailed information about each payment, including amounts, currencies, issuers, timestamps, and paths. -## Latest Payments on Stellar +## Get Latest Stellar Payment Transactions Below is the query to get the latest payment transactions on the Stellar network. This query provides details about the amount transferred, the currency and issuer involved, sender and receiver addresses, and the transaction path. You can run the query [here](https://ide.bitquery.io/Latest-Payments-on-Stellar) diff --git a/docs/Examples/stellar/stellar-tradeeffects-api.md b/docs/Examples/stellar/stellar-tradeeffects-api.md index 98cae3e..633ee7a 100644 --- a/docs/Examples/stellar/stellar-tradeeffects-api.md +++ b/docs/Examples/stellar/stellar-tradeeffects-api.md @@ -21,7 +21,7 @@ New to Bitquery? Here's how to get started: Need help crafting a query or subscription? Message us on [support](https://t.me/Bloxy_info). -### Trades of a Token on Stellar +### Get Stellar Trade Effects for a Token by Buy Currency This query retrieves trade effects for a specific token on the Stellar network. The `priceAmount` field represents the sell asset per buy asset ratio, providing you with accurate pricing information for each trade. @@ -76,7 +76,7 @@ query { } ``` -### Latest Trade Effects on Stellar +### Get Latest Stellar Trade Effects with Full Trade Details This query retrieves the most recent trade effects on the Stellar network, providing comprehensive information about each trade including seller addresses, operation details, and complete currency information. diff --git a/docs/Examples/stellar/stellar-transactions-api.md b/docs/Examples/stellar/stellar-transactions-api.md index 795bba5..a3afb15 100644 --- a/docs/Examples/stellar/stellar-transactions-api.md +++ b/docs/Examples/stellar/stellar-transactions-api.md @@ -8,7 +8,7 @@ keywords: [Stellar API examples, Stellar GraphQL queries, Bitquery] This API enables you to access and analyze transactions on the Stellar network, providing detailed information about each transaction, including the fee, hash, sender, and timestamp. -## Latest Transactions +## Get Latest Stellar Transactions In this query we retrieve the latest transactions on the Stellar network, including details such as the transaction fee, hash, success status, sender's address, operation count, and timestamp. @@ -40,7 +40,7 @@ query MyQuery { ``` -## Latest Transactions by a Sender +## Get Latest Stellar Transactions by Sender In this query we retrieve the most recent transactions sent by a specific address, including transaction fee, hash, memos, success status, operation count, timestamp, and sequence number. diff --git a/docs/Examples/tokens/token-api.md b/docs/Examples/tokens/token-api.md index 2d4edc8..634115d 100644 --- a/docs/Examples/tokens/token-api.md +++ b/docs/Examples/tokens/token-api.md @@ -8,7 +8,7 @@ keywords: [token API examples, GraphQL queries, Bitquery] Bitquery's flexible GraphQL APIs will help you get all sorts of token related data. We will show example of USDT on Ethereum but you can actually use same APIs to get data for any token on all chains supported by Bitquery. -## Token Price API +## Get Latest Ethereum USDT per WETH DEX Price in USD Latest trade = Latest price. In the following example, we are getting the latest trade. However, to get the price in USD, we need to apply a trick. As you know, USD doesn't exist on the blockchain. Therefore, we need to derive it. Bitquery gets the USD price of tokens listed on centralized exchanges through its partner, Cryptorank. We save them on a historical basis at the 1-hour candle and provide USD conversion of buy/sell or base/quote amount by using this USD value. Now if you have USD price anywhere in the result, you can drive the USD value of other parameters using it, including price; please check the following query, for example. @@ -52,7 +52,7 @@ Latest trade = Latest price. In the following example, we are getting the latest ``` -## Token OHLC Price Data API +## Get Ethereum USDT Five-Minute OHLC Candles Against WETH To get OHLC(Open-High-Low-Close) data you can use our Dextrades api, following query shows an example of USDT ohlc price against WETH token. @@ -90,7 +90,7 @@ To get OHLC(Open-High-Low-Close) data you can use our Dextrades api, following q ``` -## Token Stats API +## Aggregate Ethereum USDT Transfer Medians Counts and Unique Parties Using transfers apis you can stats like `median transfer`, `average transfer`, `total transfer amount and count`, `Unique sender and receivers` using our transfer api. Let's see an example of [USDT token](https://explorer.bitquery.io/ethereum/token/0xdac17f958d2ee523a2206206994597c13d831ec7). @@ -124,7 +124,7 @@ Using transfers apis you can stats like `median transfer`, `average transfer`, ` } ``` -## Token Transaction API +## List Ethereum Transactions Sent to USDT Token Contract If you want to see all transactions sent to [USDT token](https://explorer.bitquery.io/ethereum/token/0xdac17f958d2ee523a2206206994597c13d831ec7) contract address, you can use following query. [Open this query on IDE](https://ide.bitquery.io/query/RNqa8PqNZ4CfQR9U) @@ -163,7 +163,7 @@ If you want to see all transactions sent to [USDT token](https://explorer.bitque } ``` -## Token Transaction Tracking API +## Trace Ethereum USDT Inbound and Outbound Coinpath by Address If you want to track source and destination of USDT funds from an address you can use our Coinpath API. @@ -258,7 +258,7 @@ If you want to track source and destination of USDT funds from an address you ca } ``` -## Token Transaction History API +## List Recent Ethereum USDT Transfers with Receiver and Success Flag To check the latest [USDT token](https://explorer.bitquery.io/ethereum/token/0xdac17f958d2ee523a2206206994597c13d831ec7) transfers, try following api. It can give historical USDT transactions too. [Open this query on IDE](https://ide.bitquery.io/USDT-Transaction-History-API-Template_1) @@ -297,7 +297,7 @@ To check the latest [USDT token](https://explorer.bitquery.io/ethereum/token/0xd } ``` -## Token supply +## Get Ethereum USDT Circulating Supply with Mint and Burn Totals To check the token supply, you can use the following API. It also calculates Mint and burn by checking the amount sent to the dead address. [Open this query on IDE](https://ide.bitquery.io/Total-Circulating-Supply-of-a-USDT-Template) @@ -342,7 +342,7 @@ To check the token supply, you can use the following API. It also calculates Min } ``` -## Token Conversion API +## Get Latest Ethereum DEX USDT Trade Price in USD You can get USD price of token using our DEXtrade API. @@ -383,7 +383,7 @@ You can get USD price of token using our DEXtrade API. ``` -## Token Pool API (Pairs of token) +## List Ethereum USDT DEX Pairs Quote Tokens and Pool Addresses To check all pairs of a token, you can use our DEXtrade API. It also provides the Pool addresses and exchange names with the protocol used by the exchange. In this query, we are using the [USDT token](https://explorer.bitquery.io/ethereum/token/0xdac17f958d2ee523a2206206994597c13d831ec7) as an example. [Open this query on IDE](https://ide.bitquery.io/query/xA8yam1LgfrPxNnP) @@ -427,7 +427,7 @@ To check all pairs of a token, you can use our DEXtrade API. It also provides th } ``` -## Token Balance API +## Get Ethereum Wallet USDT Balance for One Address To get the token balance of any address, you can use the following API. In our example, we are getting the USDT balance for this Ethereum address[0x28c6c06298d514db089934071355e5743bf21d60](https://explorer.bitquery.io/ethereum/address/0x28c6c06298d514db089934071355e5743bf21d60). @@ -446,7 +446,7 @@ To get the token balance of any address, you can use the following API. In our e ``` -## Token Trace API +## Get Ethereum Smart Contract Call Trace for One Transaction Hash You also get the smart contract call trace for any transaction using our API. Our V2 APIs have much better data on call trace. Check [here](https://docs.bitquery.io/docs/examples/calls/smartcontract/). [Open this query](https://ide.bitquery.io/Transaction-Call-Trace_1_1) @@ -486,7 +486,7 @@ You also get the smart contract call trace for any transaction using our API. Ou } ``` -## Token Wallet History API +## List Ethereum USDT Transfers for One Wallet in Date Range You can get transaction history for any token for any address using following api. [Open this query on IDE](https://ide.bitquery.io/USDT-Wallet-History-v1_1_1_1) @@ -527,7 +527,7 @@ You can get transaction history for any token for any address using following ap } ``` -## Token Transfer API +## List Ethereum USDT Transfers After a Date with Receivers You can check any token's transfers using our transfer API. [Open this query on IDE](https://ide.bitquery.io/USDT-Transfer-API-Template) @@ -566,7 +566,7 @@ You can check any token's transfers using our transfer API. ``` -## Token All Time High & Low Price API +## Get Ethereum USDT Yearly High and Low vs WETH on DEX You can use our DEXtrades api to get All time, low of high of any token. [Open this query on IDE](https://ide.bitquery.io/USDC-All-time-high-low-v1_1_1_1_1_1) @@ -599,11 +599,11 @@ You can use our DEXtrades api to get All time, low of high of any token. ``` -## Token Token Holder API +## Find Token Holders Using the V2 Token Holders API Check our V2 API, it has support for [token holder API](https://docs.bitquery.io/docs/examples/balances/tokenHolders-api/). -## Token Balance History API +## Get Ethereum USDT Balance History with Transfers per Block We can also provide balance history for any token for any address; check the following example. @@ -634,7 +634,7 @@ We can also provide balance history for any token for any address; check the fol ``` -## Token Approval Events API +## List Ethereum USDT Approval Events from Token Contract You can also track token approvals permissions using `Approval` event. [Open this query on IDE](https://ide.bitquery.io/Get-USDT-Approval-Events-Template) diff --git a/docs/Examples/tron/address.md b/docs/Examples/tron/address.md index 02a8d64..737bffd 100644 --- a/docs/Examples/tron/address.md +++ b/docs/Examples/tron/address.md @@ -8,7 +8,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Address API provides all details regarding any address on Tron Blockchain. If given address is a smart contract API also details of that smart contract too. -## Get Address Balance +## Get Tron Address TRX Balance in USD With Annotation ``` { @@ -26,7 +26,7 @@ Replace `ADDRESS_HERE` with the actual Tron address you want to query. This will Removing `in` argument will give you balance of TRX tokens for given Tron address. -## Get TRX Token Balance History of Address +## Get Tron TRX Balance History for an Address ``` { @@ -47,7 +47,7 @@ Removing `in` argument will give you balance of TRX tokens for given Tron addres Replace `ADDRESS_HERE` with the Tron address you want to query. This query will provide the change in balance of the given address for a selected currency. It allows you to obtain the balance history for a particular currency using a single query. -## Get Claimable Rewards of Address +## Get Tron Address Claimable Voting Rewards ``` { @@ -61,7 +61,7 @@ Replace `ADDRESS_HERE` with the Tron address you want to query. This query will Replace `ADDRESS_HERE` with the Tron address you want to query. This query will provide the claimable voting reward of the given Tron address. -## Get Smart Contract Details from Address +## Get Tron Smart Contract Metadata From an Address ``` { diff --git a/docs/Examples/tron/arguments.md b/docs/Examples/tron/arguments.md index 7c71b2b..908103d 100644 --- a/docs/Examples/tron/arguments.md +++ b/docs/Examples/tron/arguments.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Ton Arguments API provides all details regarding smart contract or event arguments on Tron Blockchain. -## Get Arguments For Latest Smart Contract Calls and Events +## List Latest Tron Smart Contract Events and Call Arguments ``` { @@ -44,7 +44,7 @@ Our Ton Arguments API provides all details regarding smart contract or event arg This query will return list of 10 latest arguments for smart contract calls from Tron Blockchain. -## Filter arguments by event name +## Filter Tron Arguments by Transfer Event Name ``` { @@ -80,7 +80,7 @@ This query will return list of 10 latest arguments for smart contract calls from This query will return the arguments where name of event is `Transfer`. -## Filter Arguments by Block Height +## Filter Tron Transfer Arguments After a Minimum Block Height ``` { diff --git a/docs/Examples/tron/blocks.md b/docs/Examples/tron/blocks.md index 78b7d2e..045f47a 100644 --- a/docs/Examples/tron/blocks.md +++ b/docs/Examples/tron/blocks.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron API provides all details regarding blocks from Tron Blockchain. -## Get Transaction Trie Root of Block +## List Tron Block Trie Roots, Witnesses, and Timestamps ``` { @@ -35,7 +35,7 @@ Our Tron API provides all details regarding blocks from Tron Blockchain. This query returns transaction trie root from the block. -## Filter by Parent Block Hash of Block +## Filter Tron Blocks by Parent Block Hash ``` { @@ -62,7 +62,7 @@ This query returns transaction trie root from the block. This query filter block data by parent block hash of that block. -## Filter by Witness address of the Block +## Filter Tron Blocks by Witness Address ``` { diff --git a/docs/Examples/tron/coinpath.md b/docs/Examples/tron/coinpath.md index dd727c4..61ae63c 100644 --- a/docs/Examples/tron/coinpath.md +++ b/docs/Examples/tron/coinpath.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Coinpath API provides comprehensive information about money flow of addresses on the Tron blockchain. -## Get Money Flow of Particular Address +## Trace Tron USDT Coinpath From Initial Sender After a Date ```graphql { @@ -53,7 +53,7 @@ Our Tron Coinpath API provides comprehensive information about money flow of add This query allows you to retrieve the money flow details originating from a particular address (TTd9qHyjqiUkfTxe3gotbuTMpjU8LEbpkN) for the Tron currency (TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t) after July 31, 2023. The results are ordered in descending order based on block timestamps and are limited to the top 5 entries. -## Get Money Flow With Particular Receiver Address +## Trace Tron USDT Coinpath To a Receiver Address After a Date ```graphql { diff --git a/docs/Examples/tron/dexTrades.md b/docs/Examples/tron/dexTrades.md index a2e4e73..45015fb 100644 --- a/docs/Examples/tron/dexTrades.md +++ b/docs/Examples/tron/dexTrades.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron DEX Trade API provides comprehensive information about DEX Trades from Tron blockchain. -## Get USDT Trade from Tron blockchain +## Get Recent Tron DEX USDT Trades in a Date Range ``` { @@ -68,7 +68,7 @@ Our Tron DEX Trade API provides comprehensive information about DEX Trades from This query retrieves the latest 10 decentralized exchange (DEX) trades on the Tron network that involve the base currency "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" and occurred between July 10, 2023, and July 11, 2023. The query includes trade timestamps, trade index, protocol used, exchange name and address, smart contract address with annotation, base and quote amounts and currencies, amounts in USD, maker and taker addresses, and transaction hashes. -## Get All Trading Pair for USDT on Tron blockchain +## List Tron USDT Quote Pairs and Trade Counts per Liquidity Pool ``` { diff --git a/docs/Examples/tron/smartContractCalls.md b/docs/Examples/tron/smartContractCalls.md index 8f2b553..bd4c22f 100644 --- a/docs/Examples/tron/smartContractCalls.md +++ b/docs/Examples/tron/smartContractCalls.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Smart Contract Calls API provides detailed information about smart contract calls executed on the Tron Blockchain. -## Get List of Latest Smart Contract Calls +## List Latest Tron Smart Contract Calls With Energy Usage and Methods ``` { @@ -48,7 +48,7 @@ Our Tron Smart Contract Calls API provides detailed information about smart cont This query retrieves the latest 10 smart contract calls on the Tron network that occurred after July 31, 2023, providing details such as call amount, arguments, block height and timestamp, energy usage, net usage, smart contract address, method name and signature, and transaction hash. -## Filter Smart Contract Calls By Contract Address +## Filter Tron Smart Contract Calls by USDT Contract Address ``` { @@ -91,7 +91,7 @@ This query retrieves the latest 10 smart contract calls on the Tron network that This query retrieves the latest 10 smart contract calls on the Tron network that occurred after July 31, 2023, for a specific smart contract address "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t". It provides details such as call amount, arguments, block height and timestamp, energy usage, net usage for the specified smart contract, smart contract address, method name and signature, and transaction hash. -## Filter Smart Contract Calls By Method Name +## Filter Tron USDT Contract Calls by transfer Method Name ``` { diff --git a/docs/Examples/tron/smartContractEvents.md b/docs/Examples/tron/smartContractEvents.md index 62a2772..20927c7 100644 --- a/docs/Examples/tron/smartContractEvents.md +++ b/docs/Examples/tron/smartContractEvents.md @@ -9,7 +9,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Smart Contract Events API provides detailed information about smart contract events executed made on Tron Blockchain. -## Get List of Latest Smart Contract Events +## List Latest Tron Smart Contract Events With Arguments and Block Details ``` { @@ -51,7 +51,7 @@ Our Tron Smart Contract Events API provides detailed information about smart con This query retrieves the latest 10 smart contract events on the Tron network that occurred after July 31, 2023, providing details such as event arguments, block height and timestamp, smart contract addresses, event name and signature, and transaction hash. Note that there is a duplicate entry for "smartContract" in the query, which could be removed for better optimization. -## Filter Smart Contract Events By Contract Address +## Filter Tron Smart Contract Events by USDT Contract Address ``` { @@ -88,7 +88,7 @@ This query retrieves the latest 10 smart contract events on the Tron network tha This query retrieves the latest 10 smart contract events on the Tron network that occurred after July 31, 2023, specifically for the smart contract "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t". It provides details such as event arguments and values, block height and timestamp, smart contract address, event name and signature, and transaction hash. -## Filter Smart Contract Events By List of Event Name +## Filter Tron USDT Events by Transfer or Approval Event Names ``` { diff --git a/docs/Examples/tron/transaction.md b/docs/Examples/tron/transaction.md index 58c5685..61876e4 100644 --- a/docs/Examples/tron/transaction.md +++ b/docs/Examples/tron/transaction.md @@ -8,7 +8,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Transaction API provides detailed information about transactions from Tron Blockchain. -## Get List Of Transaction In A Particular Block +## List Tron Transactions at Block Height With Fees Energy and Logs ``` { @@ -30,7 +30,7 @@ Our Tron Transaction API provides detailed information about transactions from T This query retrieves details of a specific Tron blockchain transaction at height 53420256, including energy fee, total energy usage, transaction fee, transaction hash, number of logs, net fee, net usage, transaction result, and transaction signatures. -## Get Count of Transaction In The Block +## Count Tron Transactions at a Specific Block Height ``` { diff --git a/docs/Examples/tron/transfers.md b/docs/Examples/tron/transfers.md index b03b3b3..fcd1778 100644 --- a/docs/Examples/tron/transfers.md +++ b/docs/Examples/tron/transfers.md @@ -8,7 +8,7 @@ keywords: [Tron API examples, Tron GraphQL queries, Bitquery] Our Tron Transfers API provides detailed information about token transfers made on the Tron blockchain. -## Get latest transfer for a token +## Get Latest Tron USDT Transfers After a Block Date ``` { @@ -42,7 +42,7 @@ Our Tron Transfers API provides detailed information about token transfers made This query retrieves the latest 10 transfers of a specific currency ("TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t") on the Tron network that occurred after July 31, 2023. It provides details such as transfer amount, block timestamp, currency address and name, receiver and sender addresses, and transaction hash. -## Get latest transfers by receivers +## Get Latest Tron USDT Transfers Received by a Specific Address In this query we use the `reciever` filter to get all transfers sent to an address on Tron. You can run it [here](https://ide.bitquery.io/tron-transactions-by-receiver) @@ -79,7 +79,7 @@ In this query we use the `reciever` filter to get all transfers sent to an addre This query retrieves the latest 10 transfers on the Tron network for the currency "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" that occurred after July 31, 2023, where the specified receiver address is "TShuppF9wx9Ddx7ih1E2o88QskXeqQpGKE". It provides details such as transfer amount, block timestamp, currency address and name, receiver address, sender address, and transaction hash. -## Filter transfers by block height +## List Tron Transfers at a Specific Block Height ``` { @@ -111,7 +111,7 @@ This query retrieves the latest 10 transfers on the Tron network for the currenc This query retrieves transfers on the Tron network that occurred at block height 53420256, providing details such as transfer amount, block timestamp, currency address and name, receiver address, sender address, and transaction hash. -## Tron Transfers Both Inflow and Outflow +## Sum Tron Address Inflow and Outflow Totals by Currency The following query is used to fetch the total incoming and outgoing transfers for a specific address on the Tron network. From 4f3cefe5fac1304f918573106763ff4cf4a44852 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Wed, 1 Apr 2026 22:26:26 +0530 Subject: [PATCH 06/14] Add SEO-MEASUREMENT.md and seo/ to .gitignore Made-with: Cursor --- .gitignore | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.gitignore b/.gitignore index 06a7bc9..66c58aa 100644 --- a/.gitignore +++ b/.gitignore @@ -16,6 +16,11 @@ .env.test.local .env.production.local +# Local SEO artifacts — do not commit +SEO-MEASUREMENT.md +seo/ +scripts/verify-static-seo-local.sh + npm-debug.log* yarn-debug.log* yarn-error.log* From e00a74f1b1b64840130e49102249026cb2a5e01f Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 11:10:31 +0530 Subject: [PATCH 07/14] SEO round 2: front matter for 15 .mdx files, unique descriptions for 55 Schema pages, fix Dogecoin title - Add title/description/keywords front matter to 15 .mdx example pages (Algorand, Avalanche, Bitcoin I/O, Hedera, Ripple, Velas) that had none - Rewrite 55 templated Schema descriptions to be chain-specific and unique (Cronos, Algorand, Cardano, Celo, Conflux, Cosmos, Elrond, EOS, Filecoin, Flow, Harmony, Hedera, Solana, Stellar, Tezos, Velas) - Fix duplicate "Dash Coinpath API" title on Dogecoin coinpath page - Add Related Resources to Harmony/Tezos overviews and Zcash example pages - Standardize Coinpath section headings to "Related Resources" with production URLs Made-with: Cursor --- docs/Examples/Zcash/address-api.md | 15 ++++++--------- docs/Examples/Zcash/zenzec-api.md | 14 ++++++-------- docs/Examples/algorand/smartContractCalls.mdx | 6 ++++++ docs/Examples/algorand/transactions.mdx | 6 ++++++ docs/Examples/algorand/transfers.mdx | 6 ++++++ docs/Examples/avalanche/avax-trades-api.mdx | 6 ++++++ .../bitcoin/Bitcoin-Input-and-Output API.mdx | 6 ++++++ docs/Examples/hedera/hedera-api-video.mdx | 6 ++++++ docs/Examples/ripple/balances.mdx | 6 ++++++ docs/Examples/ripple/payments.mdx | 6 ++++++ docs/Examples/ripple/trades.mdx | 6 ++++++ docs/Examples/ripple/transfers.mdx | 6 ++++++ docs/Examples/velas/calls.mdx | 6 ++++++ docs/Examples/velas/events.mdx | 6 ++++++ docs/Examples/velas/trades.mdx | 6 ++++++ docs/Examples/velas/transactions.mdx | 6 ++++++ docs/Examples/velas/transfers.mdx | 6 ++++++ docs/Schema/Cronos/address.md | 2 +- docs/Schema/Cronos/transactions.md | 2 +- docs/Schema/Dogecoin/coinpath.md | 18 +++++++++--------- docs/Schema/algorand/address.md | 2 +- docs/Schema/algorand/transactions.md | 2 +- docs/Schema/cardano/address.md | 2 +- docs/Schema/cardano/mints.md | 2 +- docs/Schema/cardano/transactions.md | 2 +- docs/Schema/celo/address.md | 2 +- docs/Schema/celo/transactions.md | 2 +- docs/Schema/celo/transfers.md | 2 +- docs/Schema/conflux/address.md | 2 +- docs/Schema/conflux/transactions.md | 2 +- docs/Schema/cosmos/address.md | 2 +- docs/Schema/cosmos/attributes.md | 2 +- docs/Schema/cosmos/messages.md | 2 +- docs/Schema/cosmos/transactions.md | 2 +- docs/Schema/elrond/address.md | 2 +- docs/Schema/elrond/blockvalidators.md | 2 +- docs/Schema/elrond/miniblocks.md | 2 +- docs/Schema/elrond/operations.md | 2 +- docs/Schema/elrond/transactions.md | 2 +- docs/Schema/eos/proposers.md | 2 +- docs/Schema/eos/transactions.md | 2 +- docs/Schema/eos/transfers.md | 2 +- docs/Schema/filecoin/address.md | 2 +- docs/Schema/filecoin/calls.md | 2 +- docs/Schema/filecoin/messages.md | 2 +- docs/Schema/flow/address.md | 2 +- docs/Schema/flow/collections.md | 2 +- docs/Schema/flow/events.md | 2 +- docs/Schema/flow/inputs.md | 2 +- docs/Schema/flow/outputs.md | 2 +- docs/Schema/flow/transactionAuthorizers.md | 2 +- .../flow/transactionEnvelopeSignatures.md | 2 +- .../flow/transactionPayloadSignatures.md | 2 +- docs/Schema/flow/transactions.md | 2 +- docs/Schema/harmony/overview.md | 9 +++++++++ docs/Schema/harmony/transactions.md | 2 +- docs/Schema/hedera/address.md | 2 +- docs/Schema/hedera/calls.md | 2 +- docs/Schema/hedera/inputs.md | 2 +- docs/Schema/hedera/messages.md | 2 +- docs/Schema/hedera/outputs.md | 2 +- docs/Schema/hedera/transactions.md | 2 +- docs/Schema/solana/address.md | 2 +- docs/Schema/solana/transactions.md | 2 +- docs/Schema/stellar/address.md | 2 +- docs/Schema/stellar/effects.md | 2 +- docs/Schema/stellar/operations.md | 2 +- docs/Schema/stellar/payments.md | 2 +- docs/Schema/stellar/transactions.md | 2 +- docs/Schema/tezos/address.md | 2 +- docs/Schema/tezos/operations.md | 2 +- docs/Schema/tezos/overview.md | 9 +++++++++ docs/Schema/tezos/transactions.md | 2 +- docs/Schema/velas/address.md | 2 +- docs/Schema/velas/transactions.md | 2 +- .../Fund Tracking/EVM_Chains.md | 6 +++--- .../Fund Tracking/Ledger_Based_Chains.md | 6 +++--- .../Fund Tracking/UTXO_Chains.md | 8 ++++---- .../How_to_read_coinpath_graph.md | 8 ++++---- .../Coinpath-Explained/Overview.md | 10 ++++++++++ 80 files changed, 208 insertions(+), 95 deletions(-) diff --git a/docs/Examples/Zcash/address-api.md b/docs/Examples/Zcash/address-api.md index 2abf66b..446e603 100644 --- a/docs/Examples/Zcash/address-api.md +++ b/docs/Examples/Zcash/address-api.md @@ -287,13 +287,10 @@ You can query multiple addresses at once by using `{in: ["address1", "address2", ::: -:::tip - -**Need More Zcash Data?** - -Check out our other Zcash examples: +## Related Resources -- [UTXO Input/Output API ➤](https://docs.bitquery.io/v1/docs/examples/Transactions/input-output-api) -- [Transaction API ➤](https://docs.bitquery.io/v1/docs/examples/Transactions/transaction-api) - -::: +- [UTXO Input/Output API Examples](https://docs.bitquery.io/v1/docs/examples/Transactions/input-output-api) +- [Transaction API Examples](https://docs.bitquery.io/v1/docs/examples/Transactions/transaction-api) +- [ZenZEC Token Trades API](https://docs.bitquery.io/v1/docs/examples/Zcash/zenzec-api) +- [Coinpath Money Flow API](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/Zcash/zenzec-api.md b/docs/Examples/Zcash/zenzec-api.md index a0641fd..83893a1 100644 --- a/docs/Examples/Zcash/zenzec-api.md +++ b/docs/Examples/Zcash/zenzec-api.md @@ -145,12 +145,10 @@ query LatestTrades {
-:::tip +## Related Resources -**Need More Solana Token Data?** - -Check out our other Solana examples: -- [Solana Transfers API ➤](https://docs.bitquery.io/v1/docs/examples/Solana/transfers) -- [Solana DEX Trades API ➤](https://docs.bitquery.io/v1/docs/examples/dexTrades/dex-trading-data-api) - -::: +- [Solana Transfers API Examples](https://docs.bitquery.io/v1/docs/examples/Solana/transfers) +- [DEX Trading Data API Examples](https://docs.bitquery.io/v1/docs/examples/dexTrades/dex-trading-data-api) +- [Zcash Address API Examples](https://docs.bitquery.io/v1/docs/examples/Zcash/address-api) +- [DEX OHLC API Examples](https://docs.bitquery.io/v1/docs/examples/dexTrades/ohlc) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/algorand/smartContractCalls.mdx b/docs/Examples/algorand/smartContractCalls.mdx index a5ba14d..4c9dd4b 100644 --- a/docs/Examples/algorand/smartContractCalls.mdx +++ b/docs/Examples/algorand/smartContractCalls.mdx @@ -1,3 +1,9 @@ +--- +title: "Algorand Smart Contract Calls API Examples — Bitquery GraphQL" +description: "Query Algorand smart contract calls with Bitquery GraphQL. Count calls per block, filter by transaction type (acfg, pay), and track newly created assets." +keywords: [Algorand, smart contract calls, acfg, asset config, Algorand API, Bitquery, GraphQL, transaction type] +--- + # Algorand Smart Contract Calls API Our Algorand Smart Contract Calls API provides detailed information about smart contract calls executed on the Algorand Blockchain. diff --git a/docs/Examples/algorand/transactions.mdx b/docs/Examples/algorand/transactions.mdx index 013b58c..f9fb7fe 100644 --- a/docs/Examples/algorand/transactions.mdx +++ b/docs/Examples/algorand/transactions.mdx @@ -1,3 +1,9 @@ +--- +title: "Algorand Transactions API Examples — Bitquery GraphQL" +description: "Query Algorand transactions with Bitquery GraphQL. Get latest transactions, filter by date range, count daily transactions, find unique senders, and look up by hash." +keywords: [Algorand, transactions, Algorand API, Bitquery, GraphQL, transaction count, sender, transaction hash] +--- + # Algorand Transactions API Our Algorand Transaction API provides detailed information about Algorand Transactions. Below are some examples of `transactions` API: diff --git a/docs/Examples/algorand/transfers.mdx b/docs/Examples/algorand/transfers.mdx index a48c3d7..e62a1cb 100644 --- a/docs/Examples/algorand/transfers.mdx +++ b/docs/Examples/algorand/transfers.mdx @@ -1,3 +1,9 @@ +--- +title: "Algorand Transfers API Examples — Bitquery GraphQL" +description: "Query Algorand token transfers with Bitquery GraphQL. Filter transfers by asset ID, date range, and sender or receiver address." +keywords: [Algorand, transfers, token transfers, Algorand API, Bitquery, GraphQL, ASA, asset transfer] +--- + # Algorand Transfers API Our Algorand Transfers API provides detailed information about Algorand Transfers. Below are some examples of `transfers` API: diff --git a/docs/Examples/avalanche/avax-trades-api.mdx b/docs/Examples/avalanche/avax-trades-api.mdx index 2cf1784..7c4ea7c 100644 --- a/docs/Examples/avalanche/avax-trades-api.mdx +++ b/docs/Examples/avalanche/avax-trades-api.mdx @@ -1,3 +1,9 @@ +--- +title: "Avalanche AVAX DEX Trades API Examples — Bitquery GraphQL" +description: "Query Avalanche DEX trades and AVAX token prices with Bitquery GraphQL. Get latest AVAX trades, OHLC candlestick data for AVAX/USDC, and trade volume." +keywords: [Avalanche, AVAX, DEX trades, OHLC, Bitquery, GraphQL, AVAX price, Avalanche API, USDC pair] +--- + # AVAX Trades API diff --git a/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx b/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx index be3511d..cdc1d6c 100644 --- a/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx +++ b/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx @@ -1,3 +1,9 @@ +--- +title: "Bitcoin Inputs & Outputs API Examples — Bitquery GraphQL" +description: "Query Bitcoin UTXO inputs and outputs with Bitquery GraphQL. Get historical BTC price, address balance at a block height, miner rewards, Cardano datum, and mining activity." +keywords: [Bitcoin, UTXO, inputs, outputs, Bitquery, GraphQL, miner rewards, BTC price, block height, Cardano datum] +--- + # Inputs and Outputs API In this section we will see examples to get details about inputs and outputs of a transaction from Bitcoin network. diff --git a/docs/Examples/hedera/hedera-api-video.mdx b/docs/Examples/hedera/hedera-api-video.mdx index 6940f25..ab3f8ef 100644 --- a/docs/Examples/hedera/hedera-api-video.mdx +++ b/docs/Examples/hedera/hedera-api-video.mdx @@ -1,3 +1,9 @@ +--- +title: "Hedera API Video Tutorial — Bitquery GraphQL" +description: "Watch a video tutorial on using Bitquery's GraphQL API for Hedera. Learn how to query real-time and historical Hedera blockchain data." +keywords: [Hedera, HBAR, Hedera API, Bitquery, GraphQL, video tutorial, Hedera blockchain] +--- + # Hedera APIs - Video Tutorial In this section, we will see examples of Hedera APIs and how you can get real-time and historical information on the same. diff --git a/docs/Examples/ripple/balances.mdx b/docs/Examples/ripple/balances.mdx index 9cb6793..9fb02da 100644 --- a/docs/Examples/ripple/balances.mdx +++ b/docs/Examples/ripple/balances.mdx @@ -1,3 +1,9 @@ +--- +title: "Ripple XRP Balance API Examples — Bitquery GraphQL" +description: "Query XRP Ledger account balances with Bitquery GraphQL. Get historical balance snapshots, multi-currency holdings, and balance changes for any Ripple address." +keywords: [Ripple, XRP, balance, XRP Ledger, Bitquery, GraphQL, account balance, Ripple API, historical balance] +--- + # Ripple Balance API Ripple Balance API provides all details regarding balances on Ripple Blockchain. Below are some examples of `balance` API: diff --git a/docs/Examples/ripple/payments.mdx b/docs/Examples/ripple/payments.mdx index de8ad09..276f08d 100644 --- a/docs/Examples/ripple/payments.mdx +++ b/docs/Examples/ripple/payments.mdx @@ -1,3 +1,9 @@ +--- +title: "Ripple XRP Payments API Examples — Bitquery GraphQL" +description: "Query XRP Ledger payments with Bitquery GraphQL. Get the latest payments on Ripple, filter by sender or receiver address, and retrieve payment amounts in USD." +keywords: [Ripple, XRP, payments, XRP Ledger, Bitquery, GraphQL, Ripple payments, Ripple API] +--- + # Ripple Payments API Ripple Payments API provides all details regarding payments on Ripple Blockchain. Below are some examples of `payments` API: diff --git a/docs/Examples/ripple/trades.mdx b/docs/Examples/ripple/trades.mdx index b915421..d54f336 100644 --- a/docs/Examples/ripple/trades.mdx +++ b/docs/Examples/ripple/trades.mdx @@ -1,3 +1,9 @@ +--- +title: "Ripple XRP DEX Trades API Examples — Bitquery GraphQL" +description: "Query XRP Ledger DEX trades with Bitquery GraphQL. Get on-ledger trades for any currency pair (e.g., CNY/XRP), with sender, receiver, and USD amounts." +keywords: [Ripple, XRP, DEX trades, XRP Ledger, Bitquery, GraphQL, Ripple trades, currency pair, on-ledger trading] +--- + # Ripple Trades API Ripple Trades API provides all details regarding trades on Ripple Blockchain. Below are some examples of `trades` API: diff --git a/docs/Examples/ripple/transfers.mdx b/docs/Examples/ripple/transfers.mdx index 31bcf92..e7ec1eb 100644 --- a/docs/Examples/ripple/transfers.mdx +++ b/docs/Examples/ripple/transfers.mdx @@ -1,3 +1,9 @@ +--- +title: "Ripple XRP Transfers API Examples — Bitquery GraphQL" +description: "Query XRP Ledger transfers with Bitquery GraphQL. Get token transfers by currency, aggregate transfer counts per address, and retrieve full transfer history." +keywords: [Ripple, XRP, transfers, XRP Ledger, Bitquery, GraphQL, Ripple transfers, token transfers, address history] +--- + # Ripple Transfers API Ripple Transfers API provides all details regarding transfers on Ripple Blockchain. Below are some examples of `transfers` API: diff --git a/docs/Examples/velas/calls.mdx b/docs/Examples/velas/calls.mdx index 4928e7d..2ac351b 100644 --- a/docs/Examples/velas/calls.mdx +++ b/docs/Examples/velas/calls.mdx @@ -1,3 +1,9 @@ +--- +title: "Velas Smart Contract Calls API Examples — Bitquery GraphQL" +description: "Query Velas smart contract calls with Bitquery GraphQL. Get the latest contract interactions, method signatures, gas usage, and call arguments on the Velas EVM network." +keywords: [Velas, smart contract calls, Velas API, Bitquery, GraphQL, EVM, contract interactions] +--- + # Velas Calls API In this section we will see how to get information on smart contract calls on Velas. diff --git a/docs/Examples/velas/events.mdx b/docs/Examples/velas/events.mdx index 7f2d8d5..271ef9a 100644 --- a/docs/Examples/velas/events.mdx +++ b/docs/Examples/velas/events.mdx @@ -1,3 +1,9 @@ +--- +title: "Velas Smart Contract Events API Examples — Bitquery GraphQL" +description: "Query Velas smart contract events with Bitquery GraphQL. Get the latest emitted events, event signatures, and transaction hashes on the Velas EVM network." +keywords: [Velas, smart contract events, Velas API, Bitquery, GraphQL, EVM, events, logs] +--- + # Velas Events API In this section we will see how to get information on Events on Velas. diff --git a/docs/Examples/velas/trades.mdx b/docs/Examples/velas/trades.mdx index f5ba1b1..40b3c57 100644 --- a/docs/Examples/velas/trades.mdx +++ b/docs/Examples/velas/trades.mdx @@ -1,3 +1,9 @@ +--- +title: "Velas DEX Trades API Examples — Bitquery GraphQL" +description: "Query Velas DEX trades with Bitquery GraphQL. Get latest trades, token pairs, exchange details, buy/sell amounts, and USD-quoted prices on the Velas EVM network." +keywords: [Velas, DEX trades, Velas API, Bitquery, GraphQL, EVM, decentralized exchange, token trading] +--- + # Velas Trades API In this section we will see how to get information on DEX Trades on Velas. diff --git a/docs/Examples/velas/transactions.mdx b/docs/Examples/velas/transactions.mdx index a3995cc..4773b29 100644 --- a/docs/Examples/velas/transactions.mdx +++ b/docs/Examples/velas/transactions.mdx @@ -1,3 +1,9 @@ +--- +title: "Velas Transactions API Examples — Bitquery GraphQL" +description: "Query Velas transactions with Bitquery GraphQL. Get the latest transactions with gas, nonce, sender, receiver, and currency details on the Velas EVM network." +keywords: [Velas, transactions, Velas API, Bitquery, GraphQL, EVM, gas, transaction data] +--- + # Velas Transactions API In this section we will see how to get information on Transactions on Velas. diff --git a/docs/Examples/velas/transfers.mdx b/docs/Examples/velas/transfers.mdx index 7c8f6b6..7d95272 100644 --- a/docs/Examples/velas/transfers.mdx +++ b/docs/Examples/velas/transfers.mdx @@ -1,3 +1,9 @@ +--- +title: "Velas Token Transfers API Examples — Bitquery GraphQL" +description: "Query Velas token transfers with Bitquery GraphQL. Get the latest transfers for any token contract, with sender, receiver, gas, and USD amounts on the Velas EVM network." +keywords: [Velas, transfers, token transfers, Velas API, Bitquery, GraphQL, EVM, VLX] +--- + # Velas Transfers API In this section we will see how to get information on Transfers on Velas. diff --git a/docs/Schema/Cronos/address.md b/docs/Schema/Cronos/address.md index a168a4b..d6b13db 100644 --- a/docs/Schema/Cronos/address.md +++ b/docs/Schema/Cronos/address.md @@ -1,6 +1,6 @@ --- title: "Cronos Address API" -description: "Query Cronos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Cronos EVM addresses on Bitquery: CRO balances, smart-contract token metadata (ERC-20), and human-readable annotations." keywords: ["Cronos API", "Cronos Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/Cronos/transactions.md b/docs/Schema/Cronos/transactions.md index cb01210..b019dec 100644 --- a/docs/Schema/Cronos/transactions.md +++ b/docs/Schema/Cronos/transactions.md @@ -1,6 +1,6 @@ --- title: "Cronos Transactions API" -description: "Query Cronos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Cronos EVM transactions: gas price, fee payer/ratio, sender and recipient, amounts, nonces, and block timestamps via Bitquery GraphQL." keywords: ["Cronos API", "Cronos Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/Dogecoin/coinpath.md b/docs/Schema/Dogecoin/coinpath.md index c73fade..b2febaf 100644 --- a/docs/Schema/Dogecoin/coinpath.md +++ b/docs/Schema/Dogecoin/coinpath.md @@ -1,25 +1,25 @@ --- -title: Dash Coinpath API -description: "Track fund flows up to any depth on Dogecoin with coinpath." +title: Dogecoin Coinpath API +description: "Track DOGE fund flows up to any depth on the Dogecoin blockchain using Coinpath technology via Bitquery GraphQL." --- - - - + + + - - + + - - + + The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology from Dash. diff --git a/docs/Schema/algorand/address.md b/docs/Schema/algorand/address.md index e944f3f..7ee0982 100644 --- a/docs/Schema/algorand/address.md +++ b/docs/Schema/algorand/address.md @@ -1,6 +1,6 @@ --- title: "Algorand Address API" -description: "Query Algorand address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Algorand account GraphQL: ALGO balance, pending and accrued rewards, participation round, status, and optional ASA contract info." keywords: ["Algorand API", "Algorand Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/algorand/transactions.md b/docs/Schema/algorand/transactions.md index 5f104f1..aec536e 100644 --- a/docs/Schema/algorand/transactions.md +++ b/docs/Schema/algorand/transactions.md @@ -1,6 +1,6 @@ --- title: "Algorand Transactions API" -description: "Query Algorand transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Algorand transaction index: fees (ALGO/USD), tx type and subtype, optional note, ASA token fields, block height, and GraphQL filters." keywords: ["Algorand API", "Algorand Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cardano/address.md b/docs/Schema/cardano/address.md index b348c7b..7337ce5 100644 --- a/docs/Schema/cardano/address.md +++ b/docs/Schema/cardano/address.md @@ -1,6 +1,6 @@ --- title: "Cardano Address API" -description: "Query Cardano address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Cardano address GraphQL: native multi-asset balances, staking stake and rewards, and controlled stake for Shelley-style addresses." keywords: ["Cardano API", "Cardano Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cardano/mints.md b/docs/Schema/cardano/mints.md index 1953b5a..2eabd23 100644 --- a/docs/Schema/cardano/mints.md +++ b/docs/Schema/cardano/mints.md @@ -1,6 +1,6 @@ --- title: "Cardano Mints API" -description: "Query Cardano mints data using Bitquery GraphQL API. Get mint events, policies, assets, and recipients." +description: "Cardano mint API: newly minted native token amounts with policy and asset IDs, plus block, time, and parent transaction hash and index." keywords: ["Cardano API", "Cardano Mints", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cardano/transactions.md b/docs/Schema/cardano/transactions.md index 62abdb1..180bd78 100644 --- a/docs/Schema/cardano/transactions.md +++ b/docs/Schema/cardano/transactions.md @@ -1,6 +1,6 @@ --- title: "Cardano Transactions API" -description: "Query Cardano transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Cardano UTXO transactions: input and output totals and counts, fees, validity ranges, mint and withdrawal counts, and block context." keywords: ["Cardano API", "Cardano Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/celo/address.md b/docs/Schema/celo/address.md index a88ff45..4637b4c 100644 --- a/docs/Schema/celo/address.md +++ b/docs/Schema/celo/address.md @@ -1,6 +1,6 @@ --- title: "Celo Address API" -description: "Query Celo address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Celo EVM addresses: CELO and stablecoin balances, ERC-20 contract metadata, balance history, and labels via Bitquery GraphQL." keywords: ["Celo API", "Celo Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/celo/transactions.md b/docs/Schema/celo/transactions.md index 944d3b3..2cc8bf2 100644 --- a/docs/Schema/celo/transactions.md +++ b/docs/Schema/celo/transactions.md @@ -1,6 +1,6 @@ --- title: "Celo Transactions API" -description: "Query Celo transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Celo EVM transactions: gas in CELO, token amounts, fee payer fields, sender and receiver annotations, and per-block ordering filters." keywords: ["Celo API", "Celo Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/celo/transfers.md b/docs/Schema/celo/transfers.md index 43aff0d..9217326 100644 --- a/docs/Schema/celo/transfers.md +++ b/docs/Schema/celo/transfers.md @@ -1,6 +1,6 @@ --- title: "Celo Transfers API" -description: "Query Celo transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +description: "Celo token transfers: filter ERC-20 and native flows by currency and date; amounts, parties, gas, and transaction hash via GraphQL." keywords: ["Celo API", "Celo Transfers", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/conflux/address.md b/docs/Schema/conflux/address.md index 738e4f4..1858794 100644 --- a/docs/Schema/conflux/address.md +++ b/docs/Schema/conflux/address.md @@ -1,6 +1,6 @@ --- title: "Conflux Address API" -description: "Query Conflux address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Conflux address API: native CFX balance and annotations on Conflux networks (e.g. Hydra) through Bitquery GraphQL." keywords: ["Conflux API", "Conflux Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/conflux/transactions.md b/docs/Schema/conflux/transactions.md index 0208b29..e46b08e 100644 --- a/docs/Schema/conflux/transactions.md +++ b/docs/Schema/conflux/transactions.md @@ -1,6 +1,6 @@ --- title: "Conflux Transactions API" -description: "Query Conflux transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Conflux transactions: CFX gas with USD conversion, success flag, contract-creation target, sender, currency, and block details." keywords: ["Conflux API", "Conflux Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cosmos/address.md b/docs/Schema/cosmos/address.md index 351dba5..740805f 100644 --- a/docs/Schema/cosmos/address.md +++ b/docs/Schema/cosmos/address.md @@ -1,6 +1,6 @@ --- title: "Cosmos Address API" -description: "Query Cosmos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Cosmos address field: native balance, annotations, and token holdings metadata for bech32 accounts via Bitquery GraphQL." keywords: ["Cosmos API", "Cosmos Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cosmos/attributes.md b/docs/Schema/cosmos/attributes.md index e873e79..6bb4836 100644 --- a/docs/Schema/cosmos/attributes.md +++ b/docs/Schema/cosmos/attributes.md @@ -1,6 +1,6 @@ --- title: "Cosmos Attributes API" -description: "Query Cosmos attributes data using Bitquery GraphQL API. Get event and message attributes for filtering and display." +description: "Cosmos SDK attributes from blocks: attribute keys and values, event types, linked messages and transactions, signers, and timestamps." keywords: ["Cosmos API", "Cosmos Attributes", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cosmos/messages.md b/docs/Schema/cosmos/messages.md index 01d5dc4..959642c 100644 --- a/docs/Schema/cosmos/messages.md +++ b/docs/Schema/cosmos/messages.md @@ -1,6 +1,6 @@ --- title: "Cosmos Messages API" -description: "Query Cosmos messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +description: "Cosmos SDK messages in GraphQL: JSON payloads, indices, senders, message types, and parent transaction hash and signer fields." keywords: ["Cosmos API", "Cosmos Messages", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/cosmos/transactions.md b/docs/Schema/cosmos/transactions.md index ba547dd..72da73e 100644 --- a/docs/Schema/cosmos/transactions.md +++ b/docs/Schema/cosmos/transactions.md @@ -1,6 +1,6 @@ --- title: "Cosmos Transactions API" -description: "Query Cosmos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Cosmos transactions API: result codes, fees and gas, signer, tx type, raw bytes, block index, and Tendermint block context." keywords: ["Cosmos API", "Cosmos Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/elrond/address.md b/docs/Schema/elrond/address.md index 5a65f51..16897e2 100644 --- a/docs/Schema/elrond/address.md +++ b/docs/Schema/elrond/address.md @@ -1,6 +1,6 @@ --- title: "Elrond Address API" -description: "Query Elrond address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "MultiversX (Elrond) account addresses: native EGLD balances, annotations, and on-chain account metadata via GraphQL." keywords: ["Elrond API", "Elrond Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/elrond/blockvalidators.md b/docs/Schema/elrond/blockvalidators.md index deb4bc2..6a71fae 100644 --- a/docs/Schema/elrond/blockvalidators.md +++ b/docs/Schema/elrond/blockvalidators.md @@ -1,6 +1,6 @@ --- title: "Elrond Block Validators API" -description: "Query Elrond validators data using Bitquery GraphQL API. Get validators associated with blocks and consensus roles." +description: "MultiversX block validators: consensus validator hex, shard, public key bitmap, block size, and tx counts per block hash." keywords: ["Elrond API", "Elrond Block Validators", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/elrond/miniblocks.md b/docs/Schema/elrond/miniblocks.md index 7c8bea4..46ee2b1 100644 --- a/docs/Schema/elrond/miniblocks.md +++ b/docs/Schema/elrond/miniblocks.md @@ -1,6 +1,6 @@ --- title: "Elrond Miniblocks API" -description: "Query Elrond miniblocks data using Bitquery GraphQL API. Get miniblock headers, shards, and ordering." +description: "MultiversX miniblocks for cross-shard flow: hashes, type, receiver shard/block hash, sender block epoch/height, and time." keywords: ["Elrond API", "Elrond Miniblocks", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/elrond/operations.md b/docs/Schema/elrond/operations.md index 921d373..e40e69f 100644 --- a/docs/Schema/elrond/operations.md +++ b/docs/Schema/elrond/operations.md @@ -1,6 +1,6 @@ --- title: "Elrond Operations API" -description: "Query Elrond operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +description: "MultiversX operations within transactions: indexed sender/receiver, type, action, data, message, and linked miniblock fields." keywords: ["Elrond API", "Elrond Operations", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/elrond/transactions.md b/docs/Schema/elrond/transactions.md index ac5d077..3c0e0ca 100644 --- a/docs/Schema/elrond/transactions.md +++ b/docs/Schema/elrond/transactions.md @@ -1,6 +1,6 @@ --- title: "Elrond Transactions API" -description: "Query Elrond transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "MultiversX transactions: cross-shard sender/receiver shards, EGLD value (USD), fees, status, signature, and action metadata." keywords: ["Elrond API", "Elrond Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/eos/proposers.md b/docs/Schema/eos/proposers.md index 8970a9b..2aa66f6 100644 --- a/docs/Schema/eos/proposers.md +++ b/docs/Schema/eos/proposers.md @@ -1,6 +1,6 @@ --- title: "EOS Proposers API" -description: "Query EOS proposers data using Bitquery GraphQL API. Get block proposers and producer metadata." +description: "EOSIO DPoS producers via blocks aggregate: producer account, blocks produced, min/max dates, height, hash, and timestamps." keywords: ["EOS API", "EOS Proposers", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/eos/transactions.md b/docs/Schema/eos/transactions.md index 47608b9..30e5be9 100644 --- a/docs/Schema/eos/transactions.md +++ b/docs/Schema/eos/transactions.md @@ -1,6 +1,6 @@ --- title: "EOS Transactions API" -description: "Query EOS transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "EOSIO transactions: CPU microseconds, net usage words, scheduled flag, success, block height/timestamp, and transaction hash." keywords: ["EOS API", "EOS Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/eos/transfers.md b/docs/Schema/eos/transfers.md index c6560ab..89df5bd 100644 --- a/docs/Schema/eos/transfers.md +++ b/docs/Schema/eos/transfers.md @@ -1,6 +1,6 @@ --- title: "EOS Transfers API" -description: "Query EOS transfers data using Bitquery GraphQL API. Get asset transfers, amounts, senders, receivers, and currencies." +description: "EOSIO token transfers: amounts, sender/receiver accounts with annotations, currency symbol/address, tx hash, and actors." keywords: ["EOS API", "EOS Transfers", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/filecoin/address.md b/docs/Schema/filecoin/address.md index 33e8361..2cba3c7 100644 --- a/docs/Schema/filecoin/address.md +++ b/docs/Schema/filecoin/address.md @@ -1,6 +1,6 @@ --- title: "Filecoin Address API" -description: "Query Filecoin address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Filecoin actor addresses (f0/f1/f2…): FIL balance, annotation labels, and account lookup for storage and wallet actors." keywords: ["Filecoin API", "Filecoin Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/filecoin/calls.md b/docs/Schema/filecoin/calls.md index 00723d0..718786c 100644 --- a/docs/Schema/filecoin/calls.md +++ b/docs/Schema/filecoin/calls.md @@ -1,6 +1,6 @@ --- title: "Filecoin Calls API" -description: "Query Filecoin calls data using Bitquery GraphQL API. Get contract or system calls, inputs, and results." +description: "Filecoin actor method calls and FIL moves: sender/receiver types, method ids/names, call path/hash, message method, success." keywords: ["Filecoin API", "Filecoin Calls", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/filecoin/messages.md b/docs/Schema/filecoin/messages.md index fb18dcf..56fad2e 100644 --- a/docs/Schema/filecoin/messages.md +++ b/docs/Schema/filecoin/messages.md @@ -1,6 +1,6 @@ --- title: "Filecoin Messages API" -description: "Query Filecoin messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +description: "Filecoin messages between actors: sender/receiver accounts and types, signature type, signed hash, and execution-ordered state." keywords: ["Filecoin API", "Filecoin Messages", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/address.md b/docs/Schema/flow/address.md index e38bd78..b8d1f5d 100644 --- a/docs/Schema/flow/address.md +++ b/docs/Schema/flow/address.md @@ -1,6 +1,6 @@ --- title: "Flow Address API" -description: "Query Flow address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Flow account addresses: native FLOW balance and annotations for Cadence wallets, contracts, and filtered address lookups." keywords: ["Flow API", "Flow Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/collections.md b/docs/Schema/flow/collections.md index 61e6fc2..95e434e 100644 --- a/docs/Schema/flow/collections.md +++ b/docs/Schema/flow/collections.md @@ -1,6 +1,6 @@ --- title: "Flow Collections API" -description: "Query Flow collections data using Bitquery GraphQL API. Get NFT collections, IDs, and collection metadata." +description: "Flow collections: transaction batches in blocks—SHA3-256 id, block index, BLS collection-node signatures, and tx counts." keywords: ["Flow API", "Flow Collections", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/events.md b/docs/Schema/flow/events.md index 65eb1c2..b6e8d31 100644 --- a/docs/Schema/flow/events.md +++ b/docs/Schema/flow/events.md @@ -1,6 +1,6 @@ --- title: "Flow Events API" -description: "Query Flow events data using Bitquery GraphQL API. Get on-chain events, types, and payloads." +description: "Flow Cadence events: event type, smart contract address and method, block height, transaction id/index, and timestamps." keywords: ["Flow API", "Flow Events", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/inputs.md b/docs/Schema/flow/inputs.md index 31224b3..708c399 100644 --- a/docs/Schema/flow/inputs.md +++ b/docs/Schema/flow/inputs.md @@ -1,6 +1,6 @@ --- title: "Flow Inputs API" -description: "Query Flow inputs data using Bitquery GraphQL API. Get transaction inputs, authorizers, and signatures context." +description: "Flow transaction inputs: amounts, currencies, NFT entity ids, transfer reasons (fees/FT/NFT), and Cadence call linkage." keywords: ["Flow API", "Flow Inputs", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/outputs.md b/docs/Schema/flow/outputs.md index c951a8b..46c8f16 100644 --- a/docs/Schema/flow/outputs.md +++ b/docs/Schema/flow/outputs.md @@ -1,6 +1,6 @@ --- title: "Flow Outputs API" -description: "Query Flow outputs data using Bitquery GraphQL API. Get transaction outputs, amounts, and recipients." +description: "Flow transaction outputs: recipient addresses, amounts and decimals, currencies, NFT entity ids, types, and transfer reasons." keywords: ["Flow API", "Flow Outputs", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/transactionAuthorizers.md b/docs/Schema/flow/transactionAuthorizers.md index 75764c0..9c35f27 100644 --- a/docs/Schema/flow/transactionAuthorizers.md +++ b/docs/Schema/flow/transactionAuthorizers.md @@ -1,6 +1,6 @@ --- title: "Flow Transaction Authorizers API" -description: "Query Flow authorizers data using Bitquery GraphQL API. Get authorizers and payer roles for transactions." +description: "Flow authorizers: accounts authorizing state-mutating Cadence txs—payer, proposer, proposal keys, block, and collection id." keywords: ["Flow API", "Flow Transaction Authorizers", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/transactionEnvelopeSignatures.md b/docs/Schema/flow/transactionEnvelopeSignatures.md index 59388a3..4ba1b6c 100644 --- a/docs/Schema/flow/transactionEnvelopeSignatures.md +++ b/docs/Schema/flow/transactionEnvelopeSignatures.md @@ -1,6 +1,6 @@ --- title: "Flow Transaction Envelope Signatures API" -description: "Query Flow signatures data using Bitquery GraphQL API. Get envelope signatures and signing accounts." +description: "Flow envelope signatures: signer address and key id, raw signature bytes, plus block, collection, and transaction context." keywords: ["Flow API", "Flow Transaction Envelope Signatures", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/transactionPayloadSignatures.md b/docs/Schema/flow/transactionPayloadSignatures.md index 1cbd488..c067102 100644 --- a/docs/Schema/flow/transactionPayloadSignatures.md +++ b/docs/Schema/flow/transactionPayloadSignatures.md @@ -1,6 +1,6 @@ --- title: "Flow Transaction Payload Signatures API" -description: "Query Flow signatures data using Bitquery GraphQL API. Get payload signatures and signer keys." +description: "Flow payload signatures on the transaction body: signer address, key id, raw signature, block height, and collection id." keywords: ["Flow API", "Flow Transaction Payload Signatures", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/flow/transactions.md b/docs/Schema/flow/transactions.md index c269175..0badf7b 100644 --- a/docs/Schema/flow/transactions.md +++ b/docs/Schema/flow/transactions.md @@ -1,6 +1,6 @@ --- title: "Flow Transactions API" -description: "Query Flow transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Flow Cadence transactions: UTF-8 script, gas limit, status, proposer, payer, reference block, collection id, events count." keywords: ["Flow API", "Flow Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/harmony/overview.md b/docs/Schema/harmony/overview.md index 664eab9..db48a6f 100644 --- a/docs/Schema/harmony/overview.md +++ b/docs/Schema/harmony/overview.md @@ -7,3 +7,12 @@ description: "Access Harmony blockchain data through Bitquery's GraphQL API. Que # Overview Bitquery indexes Harmony blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, smart contract calls and events, staking transactions, and related fields. + +## Related Resources + +- [Harmony Transactions API](https://docs.bitquery.io/v1/docs/Schema/harmony/transactions) +- [Harmony Blocks API](https://docs.bitquery.io/v1/docs/Schema/harmony/blocks) +- [Harmony Transfers API](https://docs.bitquery.io/v1/docs/Schema/harmony/transfers) +- [Harmony Smart Contract Calls API](https://docs.bitquery.io/v1/docs/Schema/harmony/smartContractCalls) +- [Harmony Staking Transactions API](https://docs.bitquery.io/v1/docs/Schema/harmony/stakingTransactions) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Schema/harmony/transactions.md b/docs/Schema/harmony/transactions.md index 0fe0254..a3f4325 100644 --- a/docs/Schema/harmony/transactions.md +++ b/docs/Schema/harmony/transactions.md @@ -1,6 +1,6 @@ --- title: "Harmony Transactions API" -description: "Query Harmony transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Harmony ONE transfers: shardId, cross-shard toShardId, gas, value in atto, success, block height—Bitquery GraphQL." keywords: ["Harmony API", "Harmony Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/address.md b/docs/Schema/hedera/address.md index 3470c8f..38b1548 100644 --- a/docs/Schema/hedera/address.md +++ b/docs/Schema/hedera/address.md @@ -1,6 +1,6 @@ --- title: "Hedera Address API" -description: "Query Hedera address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Hedera HBAR & HTS: native balance, fungible/NFT tokenBalances, annotations—EVM or shard.realm.num IDs—GraphQL." keywords: ["Hedera API", "Hedera Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/calls.md b/docs/Schema/hedera/calls.md index 159a24c..b0c0141 100644 --- a/docs/Schema/hedera/calls.md +++ b/docs/Schema/hedera/calls.md @@ -1,6 +1,6 @@ --- title: "Hedera Calls API" -description: "Query Hedera calls data using Bitquery GraphQL API. Get contract or system calls, inputs, and results." +description: "Hedera smart contract calls: callInput, callResult, gas, payer & node accounts, consensusTimestamp—GraphQL." keywords: ["Hedera API", "Hedera Calls", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/inputs.md b/docs/Schema/hedera/inputs.md index 7bc1288..86fb644 100644 --- a/docs/Schema/hedera/inputs.md +++ b/docs/Schema/hedera/inputs.md @@ -1,6 +1,6 @@ --- title: "Hedera Inputs API" -description: "Query Hedera inputs data using Bitquery GraphQL API. Get transaction inputs, authorizers, and signatures context." +description: "Hedera transfer inputs: amount, currency, payerAccount, nodeAccount, consensus time, transaction hash—GraphQL." keywords: ["Hedera API", "Hedera Inputs", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/messages.md b/docs/Schema/hedera/messages.md index 7232907..7bb8741 100644 --- a/docs/Schema/hedera/messages.md +++ b/docs/Schema/hedera/messages.md @@ -1,6 +1,6 @@ --- title: "Hedera Messages API" -description: "Query Hedera messages data using Bitquery GraphQL API. Get chain messages, actors, and method calls." +description: "Hedera Consensus Service messages: payload, entity, topicRunningHash, payer, node—Bitquery GraphQL." keywords: ["Hedera API", "Hedera Messages", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/outputs.md b/docs/Schema/hedera/outputs.md index 7cad040..afc2a7e 100644 --- a/docs/Schema/hedera/outputs.md +++ b/docs/Schema/hedera/outputs.md @@ -1,6 +1,6 @@ --- title: "Hedera Outputs API" -description: "Query Hedera outputs data using Bitquery GraphQL API. Get transaction outputs, amounts, and recipients." +description: "Hedera transfer outputs: amount, currency, transferEntity, fees, consensusTimestamp, validStart—GraphQL." keywords: ["Hedera API", "Hedera Outputs", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/hedera/transactions.md b/docs/Schema/hedera/transactions.md index 2e6c01d..d6ec609 100644 --- a/docs/Schema/hedera/transactions.md +++ b/docs/Schema/hedera/transactions.md @@ -1,6 +1,6 @@ --- title: "Hedera Transactions API" -description: "Query Hedera transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Hedera transactions: transactionType, memo, fees, payer/node accounts, transactionBytes, success—GraphQL." keywords: ["Hedera API", "Hedera Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/solana/address.md b/docs/Schema/solana/address.md index 457ac32..85b75a3 100644 --- a/docs/Schema/solana/address.md +++ b/docs/Schema/solana/address.md @@ -1,6 +1,6 @@ --- title: "Solana Address API" -description: "Query Solana address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Solana wallet SOL balance and account annotations—query addresses on Solana with Bitquery GraphQL." keywords: ["Solana API", "Solana Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/solana/transactions.md b/docs/Schema/solana/transactions.md index c18dda5..cd794cc 100644 --- a/docs/Schema/solana/transactions.md +++ b/docs/Schema/solana/transactions.md @@ -1,6 +1,6 @@ --- title: "Solana Transactions API" -description: "Query Solana transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Solana txs: signature, fee & feePayer, signer, instruction counts, inner instructions, block slot—GraphQL." keywords: ["Solana API", "Solana Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/stellar/address.md b/docs/Schema/stellar/address.md index bc2f929..6fb079a 100644 --- a/docs/Schema/stellar/address.md +++ b/docs/Schema/stellar/address.md @@ -1,6 +1,6 @@ --- title: "Stellar Address API" -description: "Query Stellar address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Stellar accounts: native XLM plus multi-asset tokenBalances (issuer, code, type) and annotations—GraphQL." keywords: ["Stellar API", "Stellar Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/stellar/effects.md b/docs/Schema/stellar/effects.md index 80b502c..92c7793 100644 --- a/docs/Schema/stellar/effects.md +++ b/docs/Schema/stellar/effects.md @@ -1,6 +1,6 @@ --- title: "Stellar Effects API" -description: "Query Stellar effects data using Bitquery GraphQL API. Get ledger effects, operations, and asset movements." +description: "Stellar effects: ledger-side deltas from operations—detail JSON, op & tx links, addresses—Bitquery GraphQL." keywords: ["Stellar API", "Stellar Effects", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/stellar/operations.md b/docs/Schema/stellar/operations.md index 6a87d8f..4d4a930 100644 --- a/docs/Schema/stellar/operations.md +++ b/docs/Schema/stellar/operations.md @@ -1,6 +1,6 @@ --- title: "Stellar Operations API" -description: "Query Stellar operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +description: "Stellar operations inside transactions: type, source account, success, index, block—Bitquery GraphQL." keywords: ["Stellar API", "Stellar Operations", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/stellar/payments.md b/docs/Schema/stellar/payments.md index 1d6a49a..5213343 100644 --- a/docs/Schema/stellar/payments.md +++ b/docs/Schema/stellar/payments.md @@ -1,6 +1,6 @@ --- title: "Stellar Payments API" -description: "Query Stellar payments data using Bitquery GraphQL API. Get payment operations and path payments." +description: "Stellar payments & path swaps: currencyFrom/To, path hops, sender/receiver, amounts—DEX-ready—GraphQL." keywords: ["Stellar API", "Stellar Payments", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/stellar/transactions.md b/docs/Schema/stellar/transactions.md index 4659ef7..c02c195 100644 --- a/docs/Schema/stellar/transactions.md +++ b/docs/Schema/stellar/transactions.md @@ -1,6 +1,6 @@ --- title: "Stellar Transactions API" -description: "Query Stellar transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Stellar signed bundles: fee, memos, timeBounds, operationCount, sender, success—multi-op txs—GraphQL." keywords: ["Stellar API", "Stellar Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/tezos/address.md b/docs/Schema/tezos/address.md index b9671c5..ac19b17 100644 --- a/docs/Schema/tezos/address.md +++ b/docs/Schema/tezos/address.md @@ -1,6 +1,6 @@ --- title: "Tezos Address API" -description: "Query Tezos address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Tezos tz addresses: balance (available, staking, delegated), annotations—XTZ account data—Bitquery GraphQL." keywords: ["Tezos API", "Tezos Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/tezos/operations.md b/docs/Schema/tezos/operations.md index c17b684..ab0dff0 100644 --- a/docs/Schema/tezos/operations.md +++ b/docs/Schema/tezos/operations.md @@ -1,6 +1,6 @@ --- title: "Tezos Operations API" -description: "Query Tezos operations data using Bitquery GraphQL API. Get chain operations, types, and operation details." +description: "Tezos operations: kind, internal/external, protocol, source, contents—bakes, delegations—Bitquery GraphQL." keywords: ["Tezos API", "Tezos Operations", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/tezos/overview.md b/docs/Schema/tezos/overview.md index 9960106..5f83852 100644 --- a/docs/Schema/tezos/overview.md +++ b/docs/Schema/tezos/overview.md @@ -7,3 +7,12 @@ description: "Access Tezos (XTZ) blockchain data through Bitquery's GraphQL API. # Overview Bitquery indexes Tezos blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, operations, address balances, coin path, and related fields. + +## Related Resources + +- [Tezos Transactions API](https://docs.bitquery.io/v1/docs/Schema/tezos/transactions) +- [Tezos Blocks API](https://docs.bitquery.io/v1/docs/Schema/tezos/blocks) +- [Tezos Operations API](https://docs.bitquery.io/v1/docs/Schema/tezos/operations) +- [Tezos Transfers API](https://docs.bitquery.io/v1/docs/Schema/tezos/transfers) +- [Tezos Coinpath API](https://docs.bitquery.io/v1/docs/Schema/tezos/coinpath) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Schema/tezos/transactions.md b/docs/Schema/tezos/transactions.md index 3b5a91f..1b6be32 100644 --- a/docs/Schema/tezos/transactions.md +++ b/docs/Schema/tezos/transactions.md @@ -1,6 +1,6 @@ --- title: "Tezos Transactions API" -description: "Query Tezos transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Tezos transfers: XTZ amount, fee, gas & storage, burn, sender/receiver, internal flag—Bitquery GraphQL." keywords: ["Tezos API", "Tezos Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/velas/address.md b/docs/Schema/velas/address.md index a323e8a..34881e6 100644 --- a/docs/Schema/velas/address.md +++ b/docs/Schema/velas/address.md @@ -1,6 +1,6 @@ --- title: "Velas Address API" -description: "Query Velas address data using Bitquery GraphQL API. Get address balances, annotations, and related activity." +description: "Velas EVM addresses: VLX balance, smart contract metadata, balance history—ethereum(network: velas)—GraphQL." keywords: ["Velas API", "Velas Address", "Bitquery", "GraphQL"] --- diff --git a/docs/Schema/velas/transactions.md b/docs/Schema/velas/transactions.md index 25069ec..40d1bf0 100644 --- a/docs/Schema/velas/transactions.md +++ b/docs/Schema/velas/transactions.md @@ -1,6 +1,6 @@ --- title: "Velas Transactions API" -description: "Query Velas transactions data using Bitquery GraphQL API. Get transactions, fees, statuses, and included operations." +description: "Velas EVM txs: gas, gasCurrency, feeRatio, txType, sender/to—query ethereum(network: velas)—GraphQL." keywords: ["Velas API", "Velas Transactions", "Bitquery", "GraphQL"] --- diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md index aabedc8..fa06d68 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md @@ -82,10 +82,10 @@ Track where funds went from an address over 2 hops on Ethereum: } ``` -## Related +## Related Resources - [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [UTXO Fund Tracking](./UTXO_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) -- [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) -- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) +- [Ethereum Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md index e8a0c2d..2e740da 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md @@ -46,10 +46,10 @@ To address these challenges, the Coinpath graph for ledger-based chains differs | Trade visibility | All transfers explicit | Only **taker** side appears; maker side excluded from path | | Pre-processing | Minimal | Extracts implicit transfers from raw tx data | -## Related +## Related Resources - [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [EVM Fund Tracking](./EVM_Chains) | [UTXO Fund Tracking](./UTXO_Chains) -- [Ripple schema reference](/docs/Schema/ripple/overview) -- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) +- [Ripple schema reference](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md index bed7dd1..122b54b 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md @@ -87,11 +87,11 @@ Track where BTC moved from an address over 2 hops: } ``` -## Related +## Related Resources - [Coinpath Overview](../Overview) — what Coinpath is and cross-chain comparison. - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [EVM Fund Tracking](./EVM_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) -- [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) -- [Bitcoin Coinpath API examples](/docs/Examples/bitcoin/Bitcoin-Coinpath-API) -- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) +- [Bitcoin Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Bitcoin Coinpath API examples](https://docs.bitquery.io/v1/docs/examples/bitcoin/Bitcoin-Coinpath-API) +- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) diff --git a/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md b/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md index 0502e00..cd85f7b 100644 --- a/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md +++ b/docs/building-queries/Coinpath-Explained/How_to_read_coinpath_graph.md @@ -301,10 +301,10 @@ query ($network: EthereumNetwork!, $outboundDepth: Int!, $limit: Int!, $currency --- -## Next Steps +## Related Resources - [Coinpath Overview](./Overview) — what Coinpath is and why it matters. - **Fund Tracking by chain type:** [EVM](./Fund%20Tracking/EVM_Chains) | [UTXO](./Fund%20Tracking/UTXO_Chains) | [Ledger-based](./Fund%20Tracking/Ledger_Based_Chains) -- [Coinpath Money Flow API — query cookbook](/docs/Examples/coinpath/money-flow-api) -- [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) -- [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) +- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Bitcoin Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Ethereum Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) diff --git a/docs/building-queries/Coinpath-Explained/Overview.md b/docs/building-queries/Coinpath-Explained/Overview.md index ee0b821..99f7a33 100644 --- a/docs/building-queries/Coinpath-Explained/Overview.md +++ b/docs/building-queries/Coinpath-Explained/Overview.md @@ -56,3 +56,13 @@ Jump straight into example queries: - [Bitcoin Coinpath API examples](/docs/Examples/bitcoin/Bitcoin-Coinpath-API) - [Bitcoin Coinpath schema reference](/docs/Schema/bitcoin/coinpath) - [Ethereum Coinpath schema reference](/docs/Schema/ethereum/coinpath) + +## Related Resources + +- [How to Read a Coinpath Graph](./How_to_read_coinpath_graph) +- [Coinpath for EVM Networks](./Fund%20Tracking/EVM_Chains) +- [Coinpath for UTXO Networks](./Fund%20Tracking/UTXO_Chains) +- [Coinpath for Ledger-Based Networks](./Fund%20Tracking/Ledger_Based_Chains) +- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Bitcoin Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Ethereum Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) From 47261d2b0481c64dd93fbed8d3c520ec132ac5ca Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 11:35:09 +0530 Subject: [PATCH 08/14] Add deprecation notices for unsupported chains and revert Zcash zenzec-api changes - Add :::caution Deprecated admonition to Harmony, Tezos, Elrond, Conflux, EOS, and Velas overview pages (no longer supported by Bitquery) - Revert zenzec-api.md to main branch version Made-with: Cursor --- docs/Examples/Zcash/zenzec-api.md | 14 ++++++++------ docs/Schema/conflux/overview.md | 4 ++++ docs/Schema/elrond/overview.md | 4 ++++ docs/Schema/eos/overview.md | 4 ++++ docs/Schema/harmony/overview.md | 4 ++++ docs/Schema/tezos/overview.md | 4 ++++ docs/Schema/velas/overview.md | 4 ++++ 7 files changed, 32 insertions(+), 6 deletions(-) diff --git a/docs/Examples/Zcash/zenzec-api.md b/docs/Examples/Zcash/zenzec-api.md index 83893a1..3e32509 100644 --- a/docs/Examples/Zcash/zenzec-api.md +++ b/docs/Examples/Zcash/zenzec-api.md @@ -145,10 +145,12 @@ query LatestTrades {
-## Related Resources +:::tip -- [Solana Transfers API Examples](https://docs.bitquery.io/v1/docs/examples/Solana/transfers) -- [DEX Trading Data API Examples](https://docs.bitquery.io/v1/docs/examples/dexTrades/dex-trading-data-api) -- [Zcash Address API Examples](https://docs.bitquery.io/v1/docs/examples/Zcash/address-api) -- [DEX OHLC API Examples](https://docs.bitquery.io/v1/docs/examples/dexTrades/ohlc) -- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) +**Need More Solana Token Data?** + +Check out our other Solana examples: +- [Solana Transfers API ➤](https://docs.bitquery.io/docs/Examples/Solana/transfers) +- [Solana DEX Trades API ➤](https://docs.bitquery.io/docs/Examples/dexTrades/) + +::: diff --git a/docs/Schema/conflux/overview.md b/docs/Schema/conflux/overview.md index 6c4c791..b82d942 100644 --- a/docs/Schema/conflux/overview.md +++ b/docs/Schema/conflux/overview.md @@ -7,6 +7,10 @@ keywords: [Conflux API, Conflux GraphQL, Conflux blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the Conflux blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Bitquery provides APIs to access Conflux data. You can get info on the conflux chain which uses the Tree-Graph consensus, a consensus method with parallel-processing to reach distributed consensus. Bitquery supports conflux_hydra, conflux_tethys and conflux_oceanus. diff --git a/docs/Schema/elrond/overview.md b/docs/Schema/elrond/overview.md index a245984..8116eb7 100644 --- a/docs/Schema/elrond/overview.md +++ b/docs/Schema/elrond/overview.md @@ -7,6 +7,10 @@ keywords: [Elrond API, Elrond GraphQL, Elrond blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the Elrond (MultiversX) blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + MultiversX API offers access to indexed data from the MultiversX network including shards, block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as shard information, transaction details, events, token transfers, and other relevant information. To retrieve data from the elrond blockchain, you need to provide the `elrond` argument with the value `elrond` as shown below: diff --git a/docs/Schema/eos/overview.md b/docs/Schema/eos/overview.md index cc2995f..b864b0e 100644 --- a/docs/Schema/eos/overview.md +++ b/docs/Schema/eos/overview.md @@ -7,6 +7,10 @@ keywords: [EOS API, EOS GraphQL, EOS blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the EOS blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + EOS is a open-source blockchain network focused on building high-performance blockchain platforms on top of the network. Bitquery's EOS API provides you data on proposers, smart contract calls, transactions and tokens on the network. diff --git a/docs/Schema/harmony/overview.md b/docs/Schema/harmony/overview.md index db48a6f..031eab8 100644 --- a/docs/Schema/harmony/overview.md +++ b/docs/Schema/harmony/overview.md @@ -6,6 +6,10 @@ description: "Access Harmony blockchain data through Bitquery's GraphQL API. Que # Overview +:::caution Deprecated +Bitquery has stopped supporting the Harmony blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Bitquery indexes Harmony blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, smart contract calls and events, staking transactions, and related fields. ## Related Resources diff --git a/docs/Schema/tezos/overview.md b/docs/Schema/tezos/overview.md index 5f83852..dc03e08 100644 --- a/docs/Schema/tezos/overview.md +++ b/docs/Schema/tezos/overview.md @@ -6,6 +6,10 @@ description: "Access Tezos (XTZ) blockchain data through Bitquery's GraphQL API. # Overview +:::caution Deprecated +Bitquery has stopped supporting the Tezos blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Bitquery indexes Tezos blockchain data for GraphQL queries. Use the schema pages in this section for blocks, transactions, transfers, operations, address balances, coin path, and related fields. ## Related Resources diff --git a/docs/Schema/velas/overview.md b/docs/Schema/velas/overview.md index be24e38..d2d8cb4 100644 --- a/docs/Schema/velas/overview.md +++ b/docs/Schema/velas/overview.md @@ -7,6 +7,10 @@ keywords: [Velas API, Velas GraphQL, Velas blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the Velas blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Bitquery Velas API offers access to indexed data from the velas blockchain via GraphQL API for developers. The Velas schema contains various types of queries, including block, transaction, event, transactions, transfers, and more. These queries can be used to retrieve blockchain data, such as block information, transaction details, events, token transfers, and other relevant information. From 8b842ea8624349c7c603879159c60d617e2afa0a Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 11:48:44 +0530 Subject: [PATCH 09/14] Expand 31 thin high-impact pages with queryable fields and use-case guidance - Add "What You Can Query" and "Common Use Cases" sections to 19 Schema overview pages (Bitcoin, Ethereum, BSC, Solana, Polygon, Tron, Ripple, Avalanche, Cardano, Cosmos, Stellar, Algorand, Cronos, Celo, Dash, Dogecoin, Flow, Filecoin, Beacon Chain) - Add "When to Use" / "Practical Tips" sections to 12 query-features and IDE guide pages (sorting, options, arguments, search, aliases, fragments, aggregation, expressions, utilities, network selection, app integration) Made-with: Cursor --- docs/Schema/Avalanche/overview.md | 17 +++++++++++++++++ docs/Schema/Cronos/overview.md | 17 +++++++++++++++++ docs/Schema/Dash/overview.md | 16 ++++++++++++++++ docs/Schema/Dogecoin/overview.md | 16 ++++++++++++++++ docs/Schema/Polygon/overview.md | 18 ++++++++++++++++++ docs/Schema/algorand/overview.md | 16 ++++++++++++++++ docs/Schema/binance_smart_chain/overview.md | 18 ++++++++++++++++++ docs/Schema/bitcoin/overview.md | 17 +++++++++++++++++ docs/Schema/cardano/overview.md | 17 +++++++++++++++++ docs/Schema/celo/overview.md | 17 +++++++++++++++++ docs/Schema/cosmos/overview.md | 17 +++++++++++++++++ docs/Schema/ethereum/overview.md | 18 ++++++++++++++++++ docs/Schema/ethereum2/overview.md | 17 +++++++++++++++++ docs/Schema/filecoin/overview.md | 17 +++++++++++++++++ docs/Schema/flow/overview.md | 17 +++++++++++++++++ docs/Schema/ripple/overview.md | 18 ++++++++++++++++++ docs/Schema/solana/overview.md | 18 ++++++++++++++++++ docs/Schema/stellar/overview.md | 18 ++++++++++++++++++ docs/Schema/tron/overview.md | 18 ++++++++++++++++++ docs/building-queries/network-selection.md | 12 ++++++++++++ docs/graphql-ide/use-it-in-your-application.md | 12 ++++++++++++ docs/query-features/aggregation/sum.md | 10 ++++++++++ docs/query-features/aliases.md | 10 ++++++++++ .../arguments/Other_Chains_arguments.md | 12 ++++++++++++ docs/query-features/arguments/argument.md | 12 ++++++++++++ docs/query-features/expressions/overview.md | 10 ++++++++++ docs/query-features/filtering/options.md | 13 +++++++++++++ docs/query-features/filtering/sorting.md | 11 +++++++++++ docs/query-features/fragments/overview.md | 10 ++++++++++ docs/query-features/search/search.md | 11 +++++++++++ docs/query-features/utilities/utilities.md | 10 ++++++++++ 31 files changed, 460 insertions(+) diff --git a/docs/Schema/Avalanche/overview.md b/docs/Schema/Avalanche/overview.md index db4f4a9..784fa42 100644 --- a/docs/Schema/Avalanche/overview.md +++ b/docs/Schema/Avalanche/overview.md @@ -25,6 +25,23 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +Avalanche’s architecture is built around **subnets**; most developer-facing activity lives on the **Contract Chain (C-Chain)**, which is **EVM-compatible**, uses **AVAX** for gas, and hosts major **DeFi** venues such as **Trader Joe** and **Pangolin**. Bitquery indexes this EVM surface so you can query C-Chain blocks, contracts, and token flows alongside other networks. + +## What You Can Query + +- **Blocks** — heights, timestamps, miner or producer fields, block size, and transaction counts on the C-Chain +- **Transactions** — hashes, fees paid in AVAX, senders and recipients, finality or status, and gas usage +- **Transfers** — native AVAX and token movements with amounts, symbols or contract addresses, and USD values where available +- **Smart contracts** — deployments, calls, and contract-level activity in the same style as other EVM chains +- **DEX trades** — swap and liquidity events from integrated decentralized exchanges on Avalanche +- **Coinpath** — multi-hop tracing of how assets moved between addresses across several steps + +## Common Use Cases + +- **DeFi analytics** — rank pairs, volume, and liquidity events tied to ecosystems such as Trader Joe or Pangolin +- **Treasury and wallets** — aggregate AVAX and token balances and transfer history for custody or accounting +- **Investigations** — follow **coinpath** traces to explain how funds flowed through intermediaries on the C-Chain + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Cronos/overview.md b/docs/Schema/Cronos/overview.md index 1a63adf..0588d2e 100644 --- a/docs/Schema/Cronos/overview.md +++ b/docs/Schema/Cronos/overview.md @@ -23,6 +23,23 @@ query { Let's dive in and explore the cronos data available through Bitquery API. +Cronos is an EVM-compatible chain from Crypto.com, using **CRO** for gas and settlement. Its ecosystem spans DeFi protocols, DEXes, and bridged assets; Bitquery exposes the same Ethereum-style primitives (blocks, logs, transfers, DEX tables) under the `ethereum` root with `network: cronos`. + +## What You Can Query + +- **Blocks** — heights, timestamps, producers/validators where exposed, gas usage aggregates, and transaction counts +- **Transactions** — hashes, senders, status, gas used and price, and input data for contract calls +- **Transfers** — native CRO and ERC-20 movements with amounts, counterparties, and USD valuation where available +- **Smart contracts** — deployment and interaction surfaces via events and call-related fields +- **DEX trades** — swaps and liquidity events aligned with Bitquery’s DEX-oriented schemas for EVM chains +- **Coinpath** — graph-style tracing of token flows across addresses and contracts + +## Common Use Cases + +- **DeFi and DEX dashboards** — volume, liquidity, and pair-level activity on Cronos +- **Wallet and portfolio tracking** — histories and balances derived from transfer and transaction filters +- **Contract monitoring** — watch specific contracts or event signatures for protocol or treasury activity + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Dash/overview.md b/docs/Schema/Dash/overview.md index b828b57..b3318df 100644 --- a/docs/Schema/Dash/overview.md +++ b/docs/Schema/Dash/overview.md @@ -23,6 +23,22 @@ query { Let's dive in and explore the Dash data available through Bitquery API. +Dash is a privacy-oriented UTXO network known for optional coin-mixing (PrivateSend), fast-confirmation InstantSend locks, and a masternode layer that supports governance and services. InstantSend and PrivateSend appear as on-chain transaction types where applicable; Bitquery indexes the ledger so you can analyze blocks, transactions, addresses, and value flows like other Bitcoin-family chains. + +## What You Can Query + +- **Blocks** — heights, timestamps, sizes, difficulty, and the transactions included in each block +- **Transactions** — hashes, fees, version and locktime context, and UTXO inputs and outputs +- **Addresses** — receive and spend activity derived from script and address-level views of the UTXO set +- **Transfers** — movements of DASH between addresses with amounts and linkage to parent transactions +- **Coinpath** — multi-hop tracing of funds across addresses for flow and clustering-style analysis + +## Common Use Cases + +- **Network and masternode-era analytics** — monitor block intervals, fees, and throughput alongside transaction patterns +- **UTXO flow tracing** — use coinpath to follow value across several hops for investigations or risk scoring +- **Explorer and wallet services** — power address pages, transaction detail, and recent-block feeds for Dash users + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Dogecoin/overview.md b/docs/Schema/Dogecoin/overview.md index c447ae4..220ec96 100644 --- a/docs/Schema/Dogecoin/overview.md +++ b/docs/Schema/Dogecoin/overview.md @@ -23,6 +23,22 @@ query { Let's dive in and explore the Dogecoin data available through Bitquery API. +Dogecoin is a UTXO-based Litecoin-family chain widely used for tips, payments, and community transfers. Bitquery models it through the Bitcoin-style schema (`bitcoin` root) so you can query blocks, transactions, addresses, and coinpath-style flows without smart contracts on-chain. + +## What You Can Query + +- **Blocks** — heights, timestamps, sizes, and the transactions committed in each block +- **Transactions** — hashes, fees, inputs and outputs, and linkage to block context +- **Addresses** — aggregated activity and UTXO-derived views for Dogecoin addresses +- **Transfers** — DOGE movements between addresses with amounts tied to transaction outputs +- **Coinpath** — multi-hop tracing of funds across addresses for analytics and investigations + +## Common Use Cases + +- **Payment and tipping analytics** — measure transaction counts, fees, and value moved for merchant or creator use cases +- **Address monitoring** — alert on deposits, withdrawals, or large movements for hot wallets or treasuries +- **UTXO flow analysis** — follow coinpath hops for compliance or research on the Dogecoin graph + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Polygon/overview.md b/docs/Schema/Polygon/overview.md index 4746df9..15d4d63 100644 --- a/docs/Schema/Polygon/overview.md +++ b/docs/Schema/Polygon/overview.md @@ -33,6 +33,24 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T Let's dive in and explore the Polygon API in following chapters. +**Polygon** (historically **Matic**) operates as an **Ethereum-aligned** network—often described as a **sidechain** or **Layer 2** style scaling path—with **MATIC** used for fees and staking on Polygon PoS. **Low fees** and EVM compatibility made it a hub for **DeFi** venues such as **QuickSwap** and ported liquidity on **Aave** and similar protocols. Because Polygon is EVM-based, you query it through the **`ethereum` root type** with **`network: matic`**, and Bitquery provides **blocks**, **transactions**, **transfers**, **smart contracts**, **DEX trades**, **coinpath**, and **active addresses**—the same conceptual surface as Ethereum mainnet with Polygon-specific activity. + +## What You Can Query + +- **Blocks** — heights, timestamps, validators or producers as indexed, gas usage, and transaction counts on Polygon +- **Transactions** — hashes, senders, recipients, gas pricing, and success or failure for EVM execution +- **Transfers** — MATIC and ERC-20-style token movements with amounts and USD values where available +- **Smart contracts** — deployments and calls for Polygon-native and bridged protocols such as QuickSwap or Aave deployments +- **DEX trades** — swap and liquidity events from integrated DEX subgraphs or indexed contracts +- **Coinpath** — multi-hop flows across Polygon addresses, including bridge-related patterns when visible on-chain +- **Active addresses** — engagement metrics for wallets interacting with Polygon dApps + +## Common Use Cases + +- **Affordable DeFi analytics** — track DEX volume and lending protocol activity with mainnet-like fields at lower per-query cost on-chain +- **Cross-chain bridges** — relate Polygon **transfers** and **coinpath** results to bridge contracts and counterparties on other networks +- **Growth metrics** — use **active addresses** and transfer counts for ecosystem reporting and user-acquisition dashboards + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/algorand/overview.md b/docs/Schema/algorand/overview.md index c35fde7..3fe6e41 100644 --- a/docs/Schema/algorand/overview.md +++ b/docs/Schema/algorand/overview.md @@ -23,6 +23,22 @@ You can also fetch data from Algorand Betanet (`algorand_betanet`). Let's dive in and explore the Algorand data available through Bitquery API. +Algorand is a pure proof-of-stake layer 1 with fast finality, native **ALGO** transfers, and **ASA** (Algorand Standard Asset) tokens for fungible and non-fungible assets. Bitquery indexes blocks, payments-style activity, application (smart contract) calls, and asset movements for mainnet and Betanet. + +## What You Can Query + +- **Blocks** — round/height, timestamps, proposer context where indexed, and throughput-related fields +- **Transactions** — signatures, types, fees, and grouping of inner transactions where applicable +- **Transfers** — ALGO and ASA movements with asset IDs, amounts, senders, and receivers +- **Smart contract calls** — application (app) call transactions and related fields for on-chain program interaction +- **Coinpath** — chained asset flows across accounts for tracing and analytics + +## Common Use Cases + +- **ASA and ALGO treasury tracking** — monitor balances and transfer history for assets and accounts +- **dApp and DeFi analytics** — volume and participation around apps, pools, or known program IDs +- **Cross-account tracing** — use coinpath to follow ASA or ALGO through several hops + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/binance_smart_chain/overview.md b/docs/Schema/binance_smart_chain/overview.md index 2f4e9f6..6cfea0d 100644 --- a/docs/Schema/binance_smart_chain/overview.md +++ b/docs/Schema/binance_smart_chain/overview.md @@ -23,6 +23,24 @@ query { Let's dive in and explore the BNB data available through Bitquery API. +BNB Smart Chain (BSC) is an EVM-compatible network where **BNB** pays gas and anchors a large DeFi ecosystem (including major DEXes such as PancakeSwap). Queries use the `ethereum` root with `network: bsc`; Bitquery provides deep coverage of blocks, tokens, contracts, DEX activity, and address-level metrics. + +## What You Can Query + +- **Blocks** — heights, timestamps, validators/miners where exposed, gas usage, and transaction counts +- **Transactions** — hashes, from/to, status, gas, and calldata for contract interactions +- **Transfers** — BNB and BEP-20 movements with amounts, symbols, and USD values where available +- **Smart contracts** — creation, methods, and events surfaced through the EVM indexing model +- **DEX trades** — swaps, pairs, and volumes consistent with Bitquery’s DEX schemas on EVM chains +- **Coinpath** — token flow graphs across wallets and contracts +- **Active addresses** — engagement signals derived from indexed transfer and transaction activity + +## Common Use Cases + +- **DEX and token analytics** — pair volumes, liquidity events, and trader behavior on BSC-native markets +- **Whale and treasury monitoring** — large transfers, contract wallets, and recurring payout patterns +- **Ecosystem growth metrics** — active addresses, new contracts, and transfer counts over time + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/bitcoin/overview.md b/docs/Schema/bitcoin/overview.md index d05c517..e8163a8 100644 --- a/docs/Schema/bitcoin/overview.md +++ b/docs/Schema/bitcoin/overview.md @@ -23,6 +23,23 @@ query { Let's dive in and explore the Bitcoin data available through Bitquery API. +Bitcoin is the original UTXO blockchain; **BTC** moves only through transaction inputs and outputs (no native EVM contracts). Bitquery exposes the full UTXO graph view: blocks, transactions, inputs and outputs, addresses, coinpath tracing, and Omni Layer–related data where indexed for assets on Bitcoin. + +## What You Can Query + +- **Blocks** — heights, timestamps, difficulty, sizes, miner/coinbase hints, and transaction lists +- **Transactions** — hashes, fees, versions, locktime, and per-vin/vout detail +- **Inputs and outputs** — prevout references, script types, and values for each UTXO edge +- **Addresses** — activity and aggregates derived from output scripts and address encodings +- **Coinpath** — multi-hop flows across addresses for tracing and graph analytics +- **Omni Layer** — property/token-oriented fields where Omni-class transactions are represented in the schema + +## Common Use Cases + +- **Exchange and custody reconciliation** — match deposits and withdrawals to UTXO-level movements +- **Compliance and investigations** — follow coinpath across hops with block and tx context +- **Omni and colored-coin style analytics** — track legacy token layers that ride on Bitcoin transactions + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/cardano/overview.md b/docs/Schema/cardano/overview.md index 9ffa2ed..07a89e7 100644 --- a/docs/Schema/cardano/overview.md +++ b/docs/Schema/cardano/overview.md @@ -26,6 +26,23 @@ to fetch data from Algorand blockchain, you need to provide the `network` argume Let's dive in and explore the cardano data available through Bitquery API. +Cardano uses an **eUTXO** model: **ADA** and **native tokens** live in transaction outputs guarded by scripts; minting policies control token creation. Staking and certificates appear as specialized transaction components. Bitquery indexes blocks, transactions, addresses, transfers, mint events, and coinpath-style flows under the `cardano` root. + +## What You Can Query + +- **Blocks** — heights, slot and epoch context, timestamps, and embedded transactions +- **Transactions** — hashes, fees, metadata, certificates, and withdrawals where present in indexed data +- **Addresses** — stake and payment address activity derived from outputs and movements +- **Transfers** — ADA and native asset movements with quantities, policies, and asset names +- **Mints** — mint and burn events tied to minting policies and transactions +- **Coinpath** — chained movements across addresses for tracing and analytics + +## Common Use Cases + +- **Native asset (token) analytics** — issuance, circulation, and holder flows for policy-specific assets +- **Staking and delegation views** — combine transaction and certificate-related fields for participation metrics (where exposed) +- **Wallet and explorer backends** — address histories, UTXO/eUTXO-aware transfers, and recent blocks + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/celo/overview.md b/docs/Schema/celo/overview.md index 218652e..d40173d 100644 --- a/docs/Schema/celo/overview.md +++ b/docs/Schema/celo/overview.md @@ -25,6 +25,23 @@ query { Let's dive in and explore the Ethereum data available through Bitquery API. +Celo is a mobile-first EVM-compatible network with native stable-value assets such as **cUSD** and **cEUR**, plus **CELO** for governance and gas-related economics. Production and test networks (for example mainnet, Alfajores, Baklava) are selected via the `network` argument on the `ethereum` root. Bitquery surfaces blocks, transfers, contracts, DEX trades, and coinpath like other EVM chains. + +## What You Can Query + +- **Blocks** — heights, timestamps, validators where indexed, gas aggregates, and transaction inclusion +- **Transactions** — hashes, senders, recipients, status, gas, and contract call input data +- **Transfers** — CELO, ERC-20 stablecoins, and other tokens with amounts and counterparties +- **Smart contracts** — deployments and log-driven events for DeFi and mobile dApps +- **DEX trades** — swap-level records for on-chain DEX activity on Celo +- **Coinpath** — token flow tracing across addresses and protocols + +## Common Use Cases + +- **Stablecoin circulation** — track cUSD/cEUR (and related assets) mint, burn, and transfer patterns +- **Mobile and remittance analytics** — monitor high-volume payment contracts and wallet cohorts +- **DeFi monitoring** — DEX volumes, pool events, and protocol treasuries on Celo + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/cosmos/overview.md b/docs/Schema/cosmos/overview.md index a8ac31e..2d66886 100644 --- a/docs/Schema/cosmos/overview.md +++ b/docs/Schema/cosmos/overview.md @@ -29,6 +29,23 @@ Bitquery supports following networks: Let's dive in and explore the Cosmos data available through Bitquery API. +The **Cosmos** ecosystem is built on **Tendermint** consensus and the **IBC** interoperability protocol; **ATOM** secures the **Cosmos Hub**, but many zones define their own staking assets. Transactions are often **message-oriented**: a single transaction can batch multiple **messages** (send, delegate, IBC transfer, governance vote, and so on), and indexers surface **attributes** from events for filtering. Bitquery supports **Cosmos Hub**, **Heimdall** (Polygon’s verification network), and **Crypto.org** via the `network` argument, and exposes **blocks**, **transactions**, **transfers**, **messages**, **attributes**, and **coinpath**. + +## What You Can Query + +- **Blocks** — heights, timestamps, and proposer or validator context as indexed for each supported network +- **Transactions** — wrappers that contain one or more Cosmos SDK–style messages and their overall results +- **Messages** — individual state transitions inside a transaction (bank sends, staking, IBC packets, governance, etc.) +- **Attributes** — key–value pairs from chain events for precise filters on message outcomes and module-specific data +- **Transfers** — token movements including **ATOM** on the Hub and assets on **Crypto.org**, plus IBC-related flows where indexed +- **Coinpath** — multi-hop token tracing across Cosmos accounts for analytics and investigations + +## Common Use Cases + +- **Multi-network operations** — compare **Cosmos Hub**, **Heimdall**, and **Crypto.org** traffic using the same schema with different `network` values +- **Staking products** — aggregate delegate, undelegate, and reward **messages** for validators and delegators +- **IBC observability** — when indexing covers IBC, relate **transfers** and **messages** to cross-chain volume and corridor health + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/overview.md b/docs/Schema/ethereum/overview.md index ab5b86a..719575b 100644 --- a/docs/Schema/ethereum/overview.md +++ b/docs/Schema/ethereum/overview.md @@ -28,6 +28,24 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T Let's dive in and explore the Ethereum data available through Bitquery API. +**Ethereum** was the first widely adopted **smart contract** platform: **ETH** pays for gas, **ERC-20** tokens power DeFi and payments, and **ERC-721** (and related standards) anchor NFT markets. The ecosystem remains one of the largest on-chain economies. Bitquery’s **ethereum** schema exposes **blocks**, **transactions**, **transfers**, **smart contracts**, **DEX trades**, **coinpath**, and **active addresses** for both raw chain analytics and market intelligence. + +## What You Can Query + +- **Blocks** — number, timestamp, fee recipient under proof-of-stake, base fee under EIP-1559, gas used and limits +- **Transactions** — hashes, from and to, nonces, gas price or effective gas price, and success or revert status +- **Transfers** — ETH, ERC-20, and major NFT transfers with amounts, contract addresses, and USD pricing where available +- **Smart contracts** — creations, method calls, and internal transactions as indexed from execution traces +- **DEX trades** — swaps, pools, and volume from integrated decentralized exchanges +- **Coinpath** — graph-style tracing of assets across many hops and intermediate contracts +- **Active addresses** — engagement metrics derived from indexed sends, receives, and contract interactions + +## Common Use Cases + +- **DeFi and market data** — rank tokens, pools, and DEX volume for research terminals or trading products +- **Institutional reporting** — tie **transfers**, balances, and **active addresses** to treasury or compliance views +- **Investigations** — use **coinpath** to map how ETH or tokens moved through mixers, bridges, or nested contracts + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum2/overview.md b/docs/Schema/ethereum2/overview.md index eec52b5..bae8fbc 100644 --- a/docs/Schema/ethereum2/overview.md +++ b/docs/Schema/ethereum2/overview.md @@ -19,6 +19,23 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +The **Ethereum Beacon Chain** is the **proof-of-stake consensus layer**: it coordinates **validators**, **attestations**, block proposals, **deposits**, **voluntary exits**, and **slashings** (including **proposer slashings** where applicable). It is **not** the execution layer where user transactions and smart contracts run—that data lives in the **[ethereum](/docs/Schema/ethereum/overview)** schema. Bitquery’s Beacon APIs focus on this consensus-side lifecycle and staking behavior. + +## What You Can Query + +- **Beacon blocks** — slots, roots or identifiers, and linkage to the consensus timeline as exposed by the schema +- **Validators** — participation in staking, balances, and state changes such as activation or exit +- **Attestations** — votes that support checkpoints and chain head, for participation and finality-related analysis +- **Deposits** — staking deposits that connect the economic security model to validator onboarding +- **Slashings** — evidence of protocol violations, including proposer-related cases where indexed +- **Voluntary exits** — validator-initiated exits from active duty as recorded on the Beacon Chain + +## Common Use Cases + +- **Staking dashboards** — monitor validator counts, effective balances, and attestation participation over time +- **Risk and slashings** — surface slashings and unusual validator behavior for operations or research +- **Consensus research** — correlate deposits, exits, and beacon block progression without mixing in execution-layer DEX or NFT data + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/filecoin/overview.md b/docs/Schema/filecoin/overview.md index 0f841a0..79288cf 100644 --- a/docs/Schema/filecoin/overview.md +++ b/docs/Schema/filecoin/overview.md @@ -19,6 +19,23 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +**Filecoin** is a decentralized storage network: miners earn **FIL** by committing storage, and the chain records **storage deals** and proofs rather than a generic “world computer” model. On Filecoin, **actors** (not EVM-style contracts) implement protocol logic, and the ledger records **messages**—the primary unit of chain activity—rather than Ethereum-like “transactions” alone. Bitquery exposes this model as **blocks**, **messages**, **calls**, **transfers**, **addresses**, and **coinpath** for tracing flows. + +## What You Can Query + +- **Blocks** — heights, timestamps, and structural metadata for tipsets and chain progression +- **Messages** — Filecoin messages with senders, recipients, method names, and execution outcomes where indexed +- **Calls** — actor method invocations and related execution detail for storage, market, and payment actors +- **Transfers** — FIL movements between addresses, including fees and value associated with messages +- **Addresses** — activity and balance-oriented fields for miners, clients, and regular accounts as exposed in the schema +- **Coinpath** — multi-hop FIL flows for following value through intermediate addresses + +## Common Use Cases + +- **Storage economics** — relate message and call patterns to deal activity, miner behavior, and network utilization +- **Miner and client reporting** — summarize transfers and address-level flows for operational or financial reporting +- **Forensics** — use **coinpath** to reconstruct how FIL moved across wallets tied to deals or market actors + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/flow/overview.md b/docs/Schema/flow/overview.md index 8e8dbb7..4d8fdf8 100644 --- a/docs/Schema/flow/overview.md +++ b/docs/Schema/flow/overview.md @@ -17,6 +17,23 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +Flow targets consumer-scale apps: NFT collections (for example NBA Top Shot), games, and marketplaces, with smart contracts written in **Cadence**. On-chain state is often modeled around resources, collections, and events. Bitquery indexes blocks, transactions, transfers, events, and account input/output style fields plus coinpath for tracing value across accounts. + +## What You Can Query + +- **Blocks** — heights, timestamps, and the transactions executed in each sealed block +- **Transactions** — ids, status, payer and proposer context, and links to script interaction +- **Transfers** — FLOW and token movements between accounts with amounts and asset identifiers +- **Events** — emitted Cadence events for NFT mints, sales, deposits, and custom contract signals +- **Inputs and outputs** — account-level debits and credits aligned with Flow’s transaction model where indexed +- **Coinpath** — multi-hop tracing of FLOW and supported assets across accounts + +## Common Use Cases + +- **NFT and collection analytics** — monitor mints, transfers, and marketplace events for a contract or collection +- **Game and app telemetry** — aggregate user- or contract-driven events for retention and economy dashboards +- **Account flow tracing** — follow FLOW or tokens through several hops for treasury or compliance workflows + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ripple/overview.md b/docs/Schema/ripple/overview.md index c4d28a7..8ac4772 100644 --- a/docs/Schema/ripple/overview.md +++ b/docs/Schema/ripple/overview.md @@ -28,6 +28,24 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +The **XRP Ledger** (often called **Ripple** in market contexts) is **payment-centric**: **XRP** pays transaction fees and serves as a bridge asset, while the protocol includes a **built-in DEX**, **escrows**, **checks**, **payment channels**, and **NFTokens** for richer settlement patterns than simple one-hop sends. Bitquery exposes **blocks** (ledgers), **transactions**, **transfers**, **payments**, **balances**, **offers**, and **coinpath** for both XRP and issued assets. + +## What You Can Query + +- **Blocks** — ledger indexes, close times, and consensus-advanced ledger boundaries +- **Transactions** — types, outcomes, fees in XRP, and metadata for each validated transaction +- **Payments** — path payments, partial payments, and cross-currency settlement fields where the schema models them +- **Transfers** — XRP and issued-currency movements between accounts +- **Balances** — trust-line and reserve-related views as exposed for addresses and assets +- **Offers** — limit orders and liquidity on the ledger’s native decentralized exchange +- **Coinpath** — aggregated flows across intermediate steps for complex payment paths + +## Common Use Cases + +- **Remittance and payments** — analyze high-volume payment traffic and bridge use of XRP between corridors +- **DEX and liquidity** — monitor **offers**, fills, and trading-related transactions on the built-in order book +- **Advanced ledger features** — study escrows, checks, payment channels, or NFTokens when querying those transaction families + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/solana/overview.md b/docs/Schema/solana/overview.md index 05d9db0..cdc0a72 100644 --- a/docs/Schema/solana/overview.md +++ b/docs/Schema/solana/overview.md @@ -27,6 +27,24 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +**Solana** is optimized for **high throughput** and low latency: on-chain programs (often called **programs** rather than “contracts”) receive **instructions**, and each instruction references **instruction accounts** that define which accounts are read or written. **SPL tokens** behave like the chain’s fungible-token standard, and **block rewards** compensate validators for securing the network. Bitquery’s Solana schema surfaces **blocks**, **transactions**, **transfers**, **instructions**, **instruction accounts**, and **coinpath** for flow tracing. + +## What You Can Query + +- **Blocks** — slot-relative structure, block heights or identifiers, timestamps, and aggregates where available +- **Transactions** — signatures, fee payers, success or failure, and the list of instructions executed in one atomic batch +- **Instructions** — program IDs, discriminators or decoded types, and the logical operations inside each transaction +- **Instruction accounts** — per-instruction account metas (writable, signer, addresses) for deep program analytics +- **Transfers** — native SOL and **SPL token** movements with mints, amounts, and counterparties +- **Block rewards** — validator reward and fee distribution fields as indexed for staking and economics views +- **Coinpath** — multi-hop SOL and SPL flows across addresses for tracing funds + +## Common Use Cases + +- **Program analytics** — break down instruction mix and account usage for DeFi, NFT, or consumer programs +- **Wallet and SPL portfolios** — aggregate token balances and transfer history per owner or token mint +- **Validator economics** — combine **block rewards** with transaction fees for performance or yield reporting + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/stellar/overview.md b/docs/Schema/stellar/overview.md index d00d928..6193939 100644 --- a/docs/Schema/stellar/overview.md +++ b/docs/Schema/stellar/overview.md @@ -22,6 +22,24 @@ query{ } ``` +Stellar is a multi-asset ledger: **XLM** is the native asset, while anchors and issuers define trust lines, tokens, and the on-ledger **Stellar DEX**. Path payments, liquidity pools, and fine-grained **operations** and **effects** model how value moves. Bitquery exposes blocks, ledgers, transactions, operations, payments, effects, transfers, and coinpath for graph-style analysis. + +## What You Can Query + +- **Blocks / ledgers** — sequence, close times, and summary fields for network progress +- **Transactions** — hashes, sources, fees, memo fields, and envelopes linking to inner operations +- **Operations** — payment, path payment, manage buy/sell offer, liquidity pool, and other Stellar operation types +- **Payments** — payment-specific records with assets, amounts, and destination accounts +- **Effects** — ledger effects that describe balance and trust-line changes from operations +- **Transfers** — normalized movements of XLM and issued assets between accounts +- **Coinpath** — chained flows across accounts and assets for analytics and tracing + +## Common Use Cases + +- **SDEX and anchor analytics** — volumes, spreads, and offer books for on-ledger markets and issued assets +- **Cross-border payment monitoring** — path payments, corridor assets, and liquidity pool usage +- **Account and asset compliance** — reconstruct activity from operations, effects, and transfers + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/tron/overview.md b/docs/Schema/tron/overview.md index 72af998..0cd6ac7 100644 --- a/docs/Schema/tron/overview.md +++ b/docs/Schema/tron/overview.md @@ -29,6 +29,24 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T ::: +**Tron** uses **delegated proof-of-stake (DPoS)**; **TRX** is the native asset, and **TRC-20** tokens—especially **USDT**—drive a large share of stablecoin transfer volume on the network. Bitquery indexes **blocks**, **transactions**, **transfers**, **smart contracts**, **DEX trades**, **coinpath**, and **arguments** (decoded call parameters where available) so you can analyze both token flows and contract-level behavior. + +## What You Can Query + +- **Blocks** — heights, timestamps, witness or producer fields under DPoS, and transaction counts +- **Transactions** — hashes, bandwidth and energy consumption, fees in TRX, and execution results +- **Transfers** — TRX and TRC-20 (and related token types) with amounts and USD values where indexed +- **Smart contracts** — TVM contract deployments, internal calls, and interaction history +- **DEX trades** — swaps and trading-pair activity on integrated on-chain exchanges +- **Arguments** — structured parameters passed into contract calls when decoding is supported +- **Coinpath** — multi-hop tracing suited to high-volume stablecoin paths across exchanges and wallets + +## Common Use Cases + +- **Stablecoin analytics** — monitor USDT and other TRC-20 volume, counterparties, and corridors at scale +- **dApp monitoring** — track **DEX trades**, contract calls, and **arguments** for consumer or B2B dashboards +- **Compliance workflows** — combine **coinpath** with contract metadata to explain complex multi-hop flows + ## Related Resources - [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/building-queries/network-selection.md b/docs/building-queries/network-selection.md index 1890c92..f19e3f2 100644 --- a/docs/building-queries/network-selection.md +++ b/docs/building-queries/network-selection.md @@ -17,6 +17,18 @@ Click on any chain, and in the list, let' say for example ethereum, you will fin ![network](/img/ide/network_selection.gif) +## Practical Tips + +Network selection is the GraphQL argument that pins a subtree to one chain (or a defined set of networks for that field). In the IDE you pick the chain family first—**ethereum**, **bitcoin**, **solana**, and so on—then set the **network** enum on the field that requires it, for example narrowing **ethereum** to BSC, Polygon, or mainnet. The pattern repeats across families: the root type names the protocol, and **network** chooses the fork or live network that shares that schema shape. + +EVM-style **ethereum** queries use **network: bsc**, **network: matic**, or similar values from the schema’s enum list; UTXO and other families use the same idea with their own roots, such as **bitcoin** with **network: litecoin** when the schema exposes that network under the Bitcoin API surface. Always match **network** to the enum documented for that root—guessing a string that works in one product may not be valid in GraphQL. For multi-chain products, run separate operations or separate top-level fields per chain family, each with its own **network** argument, rather than assuming one query can span unrelated schemas without fragments and aliases. + +- **Pattern:** Chain root + **network** enum = which ledger your rows come from; build queries from the IDE list so enums stay valid. +- **EVM:** Under **ethereum**, **network** distinguishes mainnet and EVM-compatible chains that share the Ethereum schema. +- **Other families:** Under **bitcoin** (and analogous roots), **network** picks the specific coin or network variant that schema supports—e.g. Litecoin under Bitcoin-style fields when available. +- **Multi-chain apps:** Issue one query per family/network combination you need, or use aliases to fetch several networks in one document; align dashboards so each panel knows its **network** explicitly. +- **IDE discovery:** Use the network filter in the builder to see allowed values before hard-coding enums in client code. + ## Related Resources - [Understanding Bitquery query architecture](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/graphql-ide/use-it-in-your-application.md b/docs/graphql-ide/use-it-in-your-application.md index 5043d38..6fb0242 100644 --- a/docs/graphql-ide/use-it-in-your-application.md +++ b/docs/graphql-ide/use-it-in-your-application.md @@ -22,6 +22,18 @@ Click on the `````` symbol to view the code snippet tab. You can select the l ![language](/img/ide/code_dropdown.png) +## Practical Tips + +Integrating Bitquery into an application is mostly a GraphQL client exercise: finalize the query in the IDE, copy the generated snippet for your stack, then call the same HTTP endpoint your snippet uses with a valid access token. The IDE’s code generator is there to reduce boilerplate—headers, endpoint URL, and example variable wiring—so you can paste and adapt rather than hand-writing the first request. + +Typical stacks include browser and server JavaScript (fetch, axios, Apollo Client, urql), mobile clients that can issue HTTPS POST, and backend languages (Python, Go, Ruby, Java, .NET) using their HTTP or GraphQL libraries. Anything that can send a **POST** with a JSON body and an **Authorization** (or equivalent) header can run Bitquery; the snippet tab reflects common choices but the underlying contract is standard GraphQL over HTTP. + +Authentication is usually a bearer-style token you obtain from the account or API key documentation: your app stores it as a secret on the server or injects it at build time for private dashboards—avoid exposing long-lived keys in public frontends. Refresh or rotate tokens according to your workspace policy, handle 401 and rate-limit responses in one place, and keep query text version-controlled so production and the IDE stay in sync. + +- **Workflow:** Author and test in the IDE → copy snippet → replace placeholders with env-based token and variables → add error handling and timeouts. +- **Languages:** Use any HTTP-capable runtime; prefer official or well-maintained GraphQL clients when you need caching, subscriptions, or typed documents. +- **Security:** Keep API tokens on the server side when possible; proxy through your backend if the client must not hold secrets. +- **Consistency:** Treat the IDE as source of truth for the query string; regenerate snippets after substantive query changes to avoid drift. ## Related Resources diff --git a/docs/query-features/aggregation/sum.md b/docs/query-features/aggregation/sum.md index 8ecab8b..5072650 100644 --- a/docs/query-features/aggregation/sum.md +++ b/docs/query-features/aggregation/sum.md @@ -57,6 +57,16 @@ By mention the address as a sender or receiver we are calculating: - The total amount of ETH that was transferred into and out of the address, as `sum_in` and `sum_out` fields - The total amount of ETH that was transferred into and out of the address as the `sum_in_usd` and `sum_out_usd` fields +**Sum** is the aggregation you reach for when only the **total** matters: how much volume moved, how many tokens flowed in aggregate, or what fees added up over a window. It complements row-level listings: you might still use `limit` for samples, but `calculate: sum` answers headline KPIs in one response. Pairing sum with **filters** (time range, address, currency, amount thresholds) defines the population being totaled; pairing it with **grouping** at the query level (for example, per-currency transfer rows) yields subtotals per bucket instead of one global figure. + +## Practical Tips + +- **Trading and liquidity metrics**: Use sum on trade or transfer amount fields to report total volume, turnover, or notional over a period for a pair, pool, or protocol. +- **Treasury and flow analysis**: Combine sum with sender/receiver criteria (as in the example) to separate inflows, outflows, and USD equivalents for an address or contract. +- **Fees and costs**: When the schema exposes fee-related amounts, summing over a date range gives protocol revenue or user cost totals without exporting raw rows to a spreadsheet. +- **Filtered totals**: Apply the same predicates you use for listing events so the sum reflects only “large transfers,” “whitelisted tokens,” or other business rules—not the whole chain history. +- **Per-dimension subtotals**: When your query returns one row per currency, token, or day (depending on schema support), each row’s sum is that slice’s total; verify how your selection groups data so you do not misread a global aggregate as a per-asset one. + ## Related Resources - [Aggregation overview](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) diff --git a/docs/query-features/aliases.md b/docs/query-features/aliases.md index 8046532..7d4e443 100644 --- a/docs/query-features/aliases.md +++ b/docs/query-features/aliases.md @@ -59,6 +59,16 @@ Here's an example of a query with aliasing: } ``` +Aliases are not just cosmetic: they let the **same GraphQL response shape** carry multiple logically distinct values when the underlying schema repeats the same field name. In Bitquery, that matters whenever you request the same conceptual field more than once under different filters, arguments, or parent selections—something the GraphQL spec would forbid without renaming. Clear aliases also stabilize client code: your application can depend on stable JSON keys such as `buyer_address` instead of inferring meaning from nesting alone. + +## When to Use Aliases + +- **Same field, different meaning**: When two sibling selections both expose `address` (or similar) but one is a buyer, pool, or contract, aliases disambiguate them in one round trip without post-processing heuristics. +- **Multi-chain or multi-network patterns**: When you issue several root fields (for example, one per network) that share identical subfield names, aliases keep responses mergeable in a single JSON object without key collisions. +- **Readability for dashboards and APIs**: When you embed query results in products or reports, aliasing matches domain language (for example, `seller_address`) and reduces training cost for consumers of the data. +- **Composing queries from templates**: When you generate GraphQL from code, aliases let you parameterize “which side of the trade” or “which role” while reusing one fragment-shaped selection block. +- **Documentation through naming**: When sharing queries across a team, intentional aliases act as inline documentation for what each branch of the selection set represents. + ## Related Resources - [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/query-features/arguments/Other_Chains_arguments.md b/docs/query-features/arguments/Other_Chains_arguments.md index d9a8df3..8bb3dc3 100644 --- a/docs/query-features/arguments/Other_Chains_arguments.md +++ b/docs/query-features/arguments/Other_Chains_arguments.md @@ -77,6 +77,18 @@ query MyQuery { } ``` +## When to Use This + +On non-EVM chains, **arguments** still represent the inputs attached to contract- or application-level calls, but the parent type, field names, and nested shapes follow that chain’s schema—not the EVM log and ABI layout you may be used to from **ethereum**-style APIs. That means you choose the chain root (for example **algorand** or **hedera**), pass **network** and filters that match that schema, then read chain-specific fields alongside generic concepts like transaction hash, sender, and smart contract address. + +The value of this API is forensic and analytical: you can see what was passed into a program call (indices, payloads, notes, or structured values depending on the chain), tie arguments to a block or consensus time, and relate them to the calling account and contract. EVM queries often lean on **arguments** with decoded ABI types; on Algorand, Hedera, and similar chains you rely on the documented fields for that protocol—**value**, **note**, **txType**, Hedera accounts and timestamps, and so on—to reconstruct intent and parameters. + +- **Cross-chain mental model:** Treat **arguments** as “call inputs + context” per chain; expect different column sets than EVM and validate against the schema for that network. +- **Parameter inspection:** Use **arguments** when you need what was supplied to a smart contract or application call, not just that a transfer occurred. +- **Filtering by call site:** Combine **arguments** with transaction hash, sender, or contract address filters to zoom in on one invocation or a small set. +- **Ordering results:** Use **options** with **desc** on block height or consensus time so recent activity appears first when exploring unknown traffic. +- **Exploration before deep queries:** Skim field lists in the IDE for the chain you use so you know which parameters are first-class versus opaque blobs. + ## Related Resources - [Arguments overview](https://docs.bitquery.io/v1/docs/query-features/arguments/argument) diff --git a/docs/query-features/arguments/argument.md b/docs/query-features/arguments/argument.md index 293414c..70eb80b 100644 --- a/docs/query-features/arguments/argument.md +++ b/docs/query-features/arguments/argument.md @@ -17,6 +17,18 @@ For detailed examples check - [Other Chains](/docs/query-features/arguments/Other_Chains_arguments.md) +In practice, **arguments** are the decoded parameters that accompany a contract method call or an emitted event. They correspond to what you would see after ABI decoding: function inputs, event topics broken out into named fields, and similar structured payloads. That makes the arguments query a direct bridge between raw on-chain calldata and human-readable contract interaction. + +Use arguments when you need to **analyze how contracts are used**—for example, which token amounts appear in swaps, which addresses are passed into governance calls, or which values show up in custom events—without re-decoding transaction input yourself. The shape and availability of fields still depend on the chain, the contract, and how the indexer exposes that contract, so you treat arguments as the indexed, decoded view of interaction data rather than a guarantee of every possible ABI layout. + +## When to Use Arguments + +- **Contract interaction analysis**: When you are studying how users or protocols call a specific method or emit a particular event, arguments let you filter and aggregate on parameter values instead of only on transaction hashes or addresses. +- **Decoded call data**: When your question is “what was passed into this function?” rather than “did this transaction succeed?”, arguments align with ABI-level semantics (parameter names and types as exposed by the API) rather than opaque hex input. +- **Cross-protocol comparisons**: When comparing similar patterns across contracts (for example, standard interfaces), consistent argument fields make it easier to build comparable metrics across deployments. +- **Narrowing large call sets**: When you already know the contract or method family, combining arguments with your schema’s filters helps you isolate relevant calls before pulling full transaction detail. +- **Validation against off-chain expectations**: When reconciling indexer output with known ABI definitions, argument fields are the right layer to spot mismatches or chain-specific encoding differences. + ## Related Resources - [EVM arguments](https://docs.bitquery.io/v1/docs/query-features/arguments/EVM_arguments) diff --git a/docs/query-features/expressions/overview.md b/docs/query-features/expressions/overview.md index 0d255d5..204b2f3 100644 --- a/docs/query-features/expressions/overview.md +++ b/docs/query-features/expressions/overview.md @@ -101,6 +101,16 @@ The `limitby` field can be used to limit the results of a query to a specific nu } ``` +Expressions shine when the metric you need is **not stored directly** but is a simple function of fields Bitquery already returns—ratios, spreads, net amounts, or scaled prices. Computing these in the query keeps sorting, limiting, and filtering aligned with the derived value (for example, ordering by a custom score) and avoids shipping raw columns to your app only to recompute the same arithmetic. They are especially useful for DEX-style analytics where “price” is naturally expressed from quantities or from min/max of a price series over a window. + +## When to Use Expressions + +- **Ratios and relative change**: When you need a return multiple, buy/sell imbalance, or close-over-open style metric, expressions combine existing aggregated or scalar fields without an extra round trip. +- **Percentages and normalization**: When you want to express a share of a total or rescale a metric, derive it with `expression()` so dashboards consume a single field. +- **Net flows**: When inflow minus outflow (or buy minus sell) answers the business question, expressions encode that definition next to the raw components for transparency. +- **Chained derived fields**: When one calculated value feeds another (as with a price expression then a multiple of that price), expressions document the dependency chain in the query itself. +- **Less post-processing**: When you would otherwise download rows and run Python or SQL again for simple arithmetic, moving it into Bitquery reduces pipeline code and keeps limits and `limitBy` behavior consistent with the computed sort keys. + ## Related Resources - [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) diff --git a/docs/query-features/filtering/options.md b/docs/query-features/filtering/options.md index 5bc8390..4e101f6 100644 --- a/docs/query-features/filtering/options.md +++ b/docs/query-features/filtering/options.md @@ -37,6 +37,19 @@ query ($network: EthereumNetwork!, $dateFormat: String!, $from: ISO8601DateTime, - The options filter is case-sensitive. - The limit and offset option must be a positive integer. +## Practical Tips + +The **options** argument is the main place you cap result size, skip pages of rows, and declare sort order in one object. Thinking in terms of “shape of the answer” (how many rows, in what order, starting where) keeps queries predictable and easier to cache on your side. + +Use **limit** and **offset** together when you are paginating through a stable sort: each page asks for the same **limit** and increases **offset** by that step. This pattern fits admin UIs and exports where users step through results; combine it with an explicit **asc** or **desc** on a unique or nearly unique field so pages do not shuffle between requests. For “give me only the top ten” style answers, set **limit** without **offset** and sort so the first rows are the ones you care about—for example highest amount or newest block. + +Performance-wise, tighter **limit** values reduce payload size and work on the API. Very large limits can still be heavy even when legal; prefer smaller pages or narrower time and filter ranges when latency matters. Remember that **options** is case-sensitive and that **limit** and **offset** must be positive integers, so validate or coerce variables before sending the request. + +- **Pagination:** Same **limit**, increasing **offset**, with a fixed sort key—ideal for sequential browsing when you do not need cursor-based APIs. +- **Top-N dashboards:** **limit** plus **desc** (or **descByInteger** when appropriate) returns a small leaderboard without post-sorting in your app. +- **Parameterized paging:** Pass **offset** (and optionally **limit**) as query variables so your client controls the page without duplicating query text. +- **Cost and latency:** Prefer reasonable **limit** values and sharper filters over one enormous pull; sort plus limit still scans according to your filters, so narrowing time and scope helps most. + ## Related Resources - [Sorting](https://docs.bitquery.io/v1/docs/query-features/filtering/sorting) diff --git a/docs/query-features/filtering/sorting.md b/docs/query-features/filtering/sorting.md index d22ce09..c0b6961 100644 --- a/docs/query-features/filtering/sorting.md +++ b/docs/query-features/filtering/sorting.md @@ -26,6 +26,17 @@ There's another flavour of this sorting option called `descbyInteger` which is n Here's an example of how you can use it ```options: {descByInteger: "tradeIndex"}``` +## When to Use This + +Choosing the right sort direction keeps your results aligned with how people read blockchain data: time-ordered feeds, leaderboards, or stable numeric ordering. Use **desc** when you want the newest or largest values first—common for latest blocks, most recent transfers, or highest-volume trades—because many schemas expose height, timestamps, or amounts as comparable fields. Use **asc** when you need chronological buildup from the genesis or from a start cursor, such as replaying events in order or walking forward through a range you already filtered. + +**descByInteger** helps when the field you sort on is stored or exposed in a way that sorts more reliably as an integer (for example dense numeric indices like trade or log positions). If plain **desc** or **asc** does not order the way you expect for a given field, **descByInteger** is worth trying before changing the query shape. + +- **Latest-first timelines:** Sort by block height or an equivalent time-like field with **desc** so the first row is the most recent activity in your window. +- **Oldest-first or range replay:** Use **asc** on the same field when you need strict forward order through a bounded interval. +- **Leaderboards and “top N”:** Pair **desc** with a limit in **options** (see the options doc) so the API returns the highest values without returning the full matching set. +- **Numeric indices:** Prefer **descByInteger** for fields that behave like integer sequence numbers when string or scalar sorting would mis-order values. + ## Related Resources - [Options filter](https://docs.bitquery.io/v1/docs/query-features/filtering/options) diff --git a/docs/query-features/fragments/overview.md b/docs/query-features/fragments/overview.md index af31a5d..9059094 100644 --- a/docs/query-features/fragments/overview.md +++ b/docs/query-features/fragments/overview.md @@ -51,6 +51,16 @@ fragment balanceChange on EthereumBalanceChange { } ``` +Fragments pay off when you find yourself **copy-pasting the same block of fields** into several queries or when one query needs the same selection under multiple paths (for example, different variables or aliases). They keep a single source of truth for “what a balance change looks like” or “which token fields we always need,” which reduces mistakes when the schema evolves. Nesting fragments—smaller fragments included inside larger ones—mirrors how you think about domain objects (a balance change inside a history inside an address) without repeating literal field lists. + +## When to Use Fragments + +- **Repeated field sets**: When three or more queries need identical columns for the same GraphQL type, extract a fragment so a schema change updates one definition instead of many. +- **DRY across environments**: When staging and production queries differ only by variables but should share shape, fragments ensure parity and simplify code review. +- **Cross-chain or multi-entity queries**: When you query similar structures on different roots or with different arguments, shared fragments keep token, trade, or transfer shapes consistent while you vary only the entry point. +- **Client and server collaboration**: When mobile, web, and backend services consume the same Bitquery shapes, a checked-in fragment document becomes an informal contract for the payload. +- **Readability of large operations**: When a query would span dozens of lines, named fragments break it into navigable pieces without changing the wire protocol. + ## Related Resources - [GraphQL aliases](https://docs.bitquery.io/v1/docs/query-features/aliases) diff --git a/docs/query-features/search/search.md b/docs/query-features/search/search.md index 1ac2b89..cd08b83 100644 --- a/docs/query-features/search/search.md +++ b/docs/query-features/search/search.md @@ -88,6 +88,17 @@ query MyQuery { ``` +## When to Use This + +**Search** is built for discovery when you have an incomplete or human-facing string—an address fragment, a token name, a symbol, or a hash—and you want the API to tell you what it might be and which **network** it belongs to. It complements typed, schema-driven queries: instead of choosing a chain and a field filter up front, you supply a string and interpret **subject** (via **__typename** and fragments) to learn whether you hit an address, currency, contract, transaction hash, or message hash. + +Use filtered queries on a specific chain when you already know the network, entity type, and filter fields; use **search** when the user pasted something ambiguous, when you are building a global lookup box, or when you need to resolve “SPECTRE AI” or a partial symbol across protocols. Search answers “what is this string?”; filtered queries answer “give me all rows matching these precise conditions on this network.” + +- **Wallet or explorer UX:** Resolve pasted text to an address, token, or tx with network context before you run detail queries. +- **Token or name lookup:** Find currencies or contracts by name or symbol when the user does not know the canonical address. +- **Ambiguous hashes:** Let **subject** discriminate transaction hashes, message hashes, and related types instead of guessing which root query to call. +- **After search, drill down:** Take the returned **network** and **subject** fields and follow up with narrow, filtered queries for balances, transfers, or events on that chain only. + ## Related Resources - [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) diff --git a/docs/query-features/utilities/utilities.md b/docs/query-features/utilities/utilities.md index 7a0d3a7..fd27edc 100644 --- a/docs/query-features/utilities/utilities.md +++ b/docs/query-features/utilities/utilities.md @@ -55,6 +55,16 @@ The metrics subfield provides metrics on your API usage. To get metrics on your ``` +The utilities root query is most valuable **alongside** your regular blockchain data queries: it answers “what is this costing my account?” and “how much capacity do I have left?” while your other operations answer “what happened on-chain?”. Operational teams often check active period and metrics after exploratory query sessions or before scheduled jobs, so spikes in `sqlRequestsCount` or points usage line up with specific dashboards or pipelines. Treat utilities as the control plane for consumption; treat schema queries as the data plane for analytics. + +## Practical Tips + +- **Before large or repeated jobs**: Inspect points and billing-related fields so batch exports, backfills, or tight polling loops do not exhaust limits unexpectedly. +- **After debugging heavy queries**: Use metrics (including per-query identifiers when you track them) to see which saved queries or integrations drive the most cost, then optimize filters, limits, or frequency. +- **Account health checks**: Use `activePeriod` to confirm whether the account is paid, blocked, or in a points-consumed state before you rely on production automation. +- **Correlate usage with product behavior**: When user-facing features slow down or fail, verifying utilities first rules out quota or billing issues before you dig into GraphQL errors from data queries. +- **Operational dashboards**: Expose utilities to internal tooling so engineers can monitor usage trends the same way they monitor application metrics. + ## Related Resources - [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) From d507f83d0884d55c446fcc00c2f7bf1e0fc041c1 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 13:07:09 +0530 Subject: [PATCH 10/14] Add deprecation notices for ETH2 and Hedera, enterprise use cases, and expand 40 thin Schema detail pages - Deprecation notices on all 8 ETH2 Beacon Chain pages and 9 Hedera pages - Enterprise use-case bullets on 18 active chain overview pages - Introductory context paragraphs on ~40 thinnest detail pages: address, addressStats, balance, blocks, coinpath, activeAddresses, mints, instructions, messages, arguments, and effectArguments across all actively supported chains Made-with: Cursor --- docs/Schema/Avalanche/blocks.md | 6 +++++- docs/Schema/Avalanche/overview.md | 1 + docs/Schema/Cronos/address.md | 2 ++ docs/Schema/Cronos/addresstats.md | 2 ++ docs/Schema/Cronos/overview.md | 1 + docs/Schema/Dash/addressstats.md | 2 ++ docs/Schema/Dash/overview.md | 1 + docs/Schema/Dogecoin/addressstats.md | 2 ++ docs/Schema/Dogecoin/overview.md | 1 + docs/Schema/Polygon/address.md | 2 +- docs/Schema/Polygon/addresstats.md | 2 ++ docs/Schema/Polygon/balance.md | 2 +- docs/Schema/Polygon/overview.md | 2 ++ docs/Schema/algorand/address.md | 2 ++ docs/Schema/algorand/overview.md | 2 ++ docs/Schema/binance_smart_chain/activeaddresses.md | 2 ++ docs/Schema/binance_smart_chain/address.md | 2 ++ docs/Schema/binance_smart_chain/addresstats.md | 2 ++ docs/Schema/binance_smart_chain/overview.md | 1 + docs/Schema/bitcoin/addressstats.md | 2 ++ docs/Schema/bitcoin/overview.md | 2 ++ docs/Schema/cardano/address.md | 1 + docs/Schema/cardano/addressstats.md | 1 + docs/Schema/cardano/coinpath.md | 2 ++ docs/Schema/cardano/mints.md | 1 + docs/Schema/cardano/overview.md | 1 + docs/Schema/celo/address.md | 2 ++ docs/Schema/celo/addresstats.md | 2 ++ docs/Schema/celo/overview.md | 1 + docs/Schema/cosmos/address.md | 2 ++ docs/Schema/cosmos/coinpath.md | 2 ++ docs/Schema/cosmos/overview.md | 1 + docs/Schema/ethereum/activeaddresses.md | 2 ++ docs/Schema/ethereum/address.md | 2 ++ docs/Schema/ethereum/addresstats.md | 2 ++ docs/Schema/ethereum/overview.md | 2 ++ docs/Schema/ethereum2/attestations.md | 4 ++++ docs/Schema/ethereum2/attesterSlashings.md | 3 +++ docs/Schema/ethereum2/blocks.md | 4 ++++ docs/Schema/ethereum2/deposits.md | 4 ++++ docs/Schema/ethereum2/overview.md | 4 ++++ docs/Schema/ethereum2/proposerSlashings.md | 4 ++++ docs/Schema/ethereum2/validatorUpdates.md | 4 ++++ docs/Schema/ethereum2/voluntaryExits.md | 4 ++++ docs/Schema/filecoin/address.md | 2 +- docs/Schema/filecoin/arguments.md | 4 ++++ docs/Schema/filecoin/messages.md | 2 ++ docs/Schema/filecoin/overview.md | 1 + docs/Schema/flow/address.md | 2 ++ docs/Schema/flow/overview.md | 1 + docs/Schema/hedera/address.md | 4 ++++ docs/Schema/hedera/arguments.md | 4 ++++ docs/Schema/hedera/calls.md | 4 ++++ docs/Schema/hedera/coinpath.md | 4 ++++ docs/Schema/hedera/inputs.md | 4 ++++ docs/Schema/hedera/messages.md | 4 ++++ docs/Schema/hedera/outputs.md | 4 ++++ docs/Schema/hedera/overview.md | 4 ++++ docs/Schema/hedera/transactions.md | 4 ++++ docs/Schema/ripple/accountRoots.md | 2 ++ docs/Schema/ripple/addressStats.md | 2 ++ docs/Schema/ripple/blocks.md | 6 +++++- docs/Schema/ripple/overview.md | 2 ++ docs/Schema/solana/address.md | 2 ++ docs/Schema/solana/blocks.md | 6 +++++- docs/Schema/solana/instructions.md | 6 +++++- docs/Schema/solana/overview.md | 2 ++ docs/Schema/stellar/address.md | 2 ++ docs/Schema/stellar/addressStats.md | 1 + docs/Schema/stellar/balanceEffects.md | 2 ++ docs/Schema/stellar/blocks.md | 6 +++++- docs/Schema/stellar/effectArguments.md | 4 +++- docs/Schema/stellar/overview.md | 1 + docs/Schema/tron/address.md | 2 ++ docs/Schema/tron/overview.md | 1 + 75 files changed, 182 insertions(+), 9 deletions(-) diff --git a/docs/Schema/Avalanche/blocks.md b/docs/Schema/Avalanche/blocks.md index f1fa1f9..bb83c36 100644 --- a/docs/Schema/Avalanche/blocks.md +++ b/docs/Schema/Avalanche/blocks.md @@ -29,7 +29,11 @@ description: "Query Avalanche C-Chain blocks, gas, rewards, and transaction coun -Bitquery's Avalanche blocks API provides information on blocks in the Avalanche chain. Below are the fields in the schema: +Bitquery's Avalanche blocks API provides information on blocks in the Avalanche chain. + +Avalanche's C-Chain follows the EVM block model: each block includes gas usage, miner/producer address, rewards, difficulty, and transaction counts. Because Bitquery queries the C-Chain through the `ethereum` root with `network: avalanche`, the block fields are consistent with other EVM chains while reflecting Avalanche's faster finality and subnet-aware consensus. Use the blocks API for C-Chain explorer pages, network throughput dashboards, and validator reward analysis. + +Below are the fields in the schema: ``` query ($network: EthereumNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601DateTime, $till: ISO8601DateTime) { diff --git a/docs/Schema/Avalanche/overview.md b/docs/Schema/Avalanche/overview.md index 784fa42..02c1eb8 100644 --- a/docs/Schema/Avalanche/overview.md +++ b/docs/Schema/Avalanche/overview.md @@ -41,6 +41,7 @@ Avalanche’s architecture is built around **subnets**; most developer-facing ac - **DeFi analytics** — rank pairs, volume, and liquidity events tied to ecosystems such as Trader Joe or Pangolin - **Treasury and wallets** — aggregate AVAX and token balances and transfer history for custody or accounting - **Investigations** — follow **coinpath** traces to explain how funds flowed through intermediaries on the C-Chain +- **Enterprise subnet and tokenization projects** — institutions launching permissioned subnets or tokenized assets on Avalanche can monitor C-Chain contract activity, token flows, and settlement patterns for compliance and operational reporting ## Related Resources diff --git a/docs/Schema/Cronos/address.md b/docs/Schema/Cronos/address.md index d6b13db..e0bd9cf 100644 --- a/docs/Schema/Cronos/address.md +++ b/docs/Schema/Cronos/address.md @@ -8,6 +8,8 @@ keywords: ["Cronos API", "Cronos Address", "Bitquery", "GraphQL"] The `address` allows us to retrieve information about a specific address. +Cronos is an EVM-compatible chain from Crypto.com, so addresses follow the standard Ethereum model. The address API returns CRO balance, annotations, balance history, and smart contract details including token metadata and contract type. Use it for wallet pages, DeFi portfolio snapshots, and verifying contract attributes on the Cronos network before querying transfers or DEX trades. + Here is an example that demonstrates how to retrieve basic information about the USDT smart contract: ``` diff --git a/docs/Schema/Cronos/addresstats.md b/docs/Schema/Cronos/addresstats.md index 15a35bb..b79c0e0 100644 --- a/docs/Schema/Cronos/addresstats.md +++ b/docs/Schema/Cronos/addresstats.md @@ -8,6 +8,8 @@ keywords: ["Cronos API", "Cronos Address Stats", "Bitquery", "GraphQL"] The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics aggregate a Cronos address's lifetime activity into a single response: total CRO and token amounts sent and received, transaction counts, fee totals, and active-day counts. This is useful for compliance profiling, exchange account monitoring, and building summary pages for the Cronos ecosystem without scanning every transaction individually. + Here is an example that demonstrates how to retrieve statistics about the USDT smart contract: ``` diff --git a/docs/Schema/Cronos/overview.md b/docs/Schema/Cronos/overview.md index 0588d2e..e88b21d 100644 --- a/docs/Schema/Cronos/overview.md +++ b/docs/Schema/Cronos/overview.md @@ -39,6 +39,7 @@ Cronos is an EVM-compatible chain from Crypto.com, using **CRO** for gas and set - **DeFi and DEX dashboards** — volume, liquidity, and pair-level activity on Cronos - **Wallet and portfolio tracking** — histories and balances derived from transfer and transaction filters - **Contract monitoring** — watch specific contracts or event signatures for protocol or treasury activity +- **Crypto.com ecosystem integration** — enterprises building on the Crypto.com stack can correlate on-chain Cronos activity with CRO-based payment, card, and exchange flows for unified business intelligence ## Related Resources diff --git a/docs/Schema/Dash/addressstats.md b/docs/Schema/Dash/addressstats.md index 3d89415..11ba5b1 100644 --- a/docs/Schema/Dash/addressstats.md +++ b/docs/Schema/Dash/addressstats.md @@ -24,6 +24,8 @@ description: "Query address statistics and history on Dash." The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics summarize a Dash address's lifetime activity: total sent and received amounts, transaction counts, fee expenditure, and days with activity. These aggregates help compliance teams, explorer backends, and wallet services build address profile pages or flag unusual patterns without replaying the full UTXO history. + Here is an example that demonstrates how to retrieve statistics about a specific address: ``` diff --git a/docs/Schema/Dash/overview.md b/docs/Schema/Dash/overview.md index b3318df..635b47b 100644 --- a/docs/Schema/Dash/overview.md +++ b/docs/Schema/Dash/overview.md @@ -38,6 +38,7 @@ Dash is a privacy-oriented UTXO network known for optional coin-mixing (PrivateS - **Network and masternode-era analytics** — monitor block intervals, fees, and throughput alongside transaction patterns - **UTXO flow tracing** — use coinpath to follow value across several hops for investigations or risk scoring - **Explorer and wallet services** — power address pages, transaction detail, and recent-block feeds for Dash users +- **Enterprise payment processing** — merchants and payment providers accepting DASH can reconcile InstantSend-confirmed transactions against point-of-sale records using block and transaction-level queries ## Related Resources diff --git a/docs/Schema/Dogecoin/addressstats.md b/docs/Schema/Dogecoin/addressstats.md index 07dc2d6..06105fd 100644 --- a/docs/Schema/Dogecoin/addressstats.md +++ b/docs/Schema/Dogecoin/addressstats.md @@ -24,6 +24,8 @@ description: "Query address statistics and history on Dogecoin." The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics give a high-level profile of any Dogecoin address: total DOGE sent and received, transaction counts, fee totals, and active-day counts. This is valuable for merchant dashboards, tipping-platform analytics, and compliance workflows that need an address summary without scanning every UTXO individually. + Here is an example that demonstrates how to retrieve statistics about a specific address: ``` diff --git a/docs/Schema/Dogecoin/overview.md b/docs/Schema/Dogecoin/overview.md index 220ec96..f9ed451 100644 --- a/docs/Schema/Dogecoin/overview.md +++ b/docs/Schema/Dogecoin/overview.md @@ -38,6 +38,7 @@ Dogecoin is a UTXO-based Litecoin-family chain widely used for tips, payments, a - **Payment and tipping analytics** — measure transaction counts, fees, and value moved for merchant or creator use cases - **Address monitoring** — alert on deposits, withdrawals, or large movements for hot wallets or treasuries - **UTXO flow analysis** — follow coinpath hops for compliance or research on the Dogecoin graph +- **Enterprise merchant integration** — businesses accepting DOGE for goods and services can automate payment confirmation, reconciliation, and accounting by querying transaction and address-level data ## Related Resources diff --git a/docs/Schema/Polygon/address.md b/docs/Schema/Polygon/address.md index 3416db7..76f841e 100644 --- a/docs/Schema/Polygon/address.md +++ b/docs/Schema/Polygon/address.md @@ -27,7 +27,7 @@ description: "Get Polygon token and smart contract details for addresses, includ The `address` allows us to retrieve information about a specific address including any smart contract. -Therefore, this api can be helpful to get the initial supply and other attributes of any token. +Therefore, this api can be helpful to get the initial supply and other attributes of any token. Polygon (Matic) shares the EVM address model with Ethereum: the address API returns MATIC balance, annotations, balance history, and—for contracts—token metadata, protocol type, and on-chain attributes. Use it for wallet interfaces, token-supply lookups, and contract verification on Polygon's low-fee network before diving into transfer or DEX data. Here is an example that demonstrates how to retrieve basic information about the USDT Token smart contract: diff --git a/docs/Schema/Polygon/addresstats.md b/docs/Schema/Polygon/addresstats.md index 8e724a4..8e96b96 100644 --- a/docs/Schema/Polygon/addresstats.md +++ b/docs/Schema/Polygon/addresstats.md @@ -27,6 +27,8 @@ description: "Get Polygon (Matic) token supply and activity summaries. Retrieve The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics aggregate a Polygon address's lifetime activity: total sent and received amounts, transaction counts, fee expenditure, distinct currencies, and active-day counts. This powers compliance profiling, explorer summary views, and portfolio dashboards that need a quick snapshot of how active an address has been on Polygon without scanning every individual transfer. + Here is an example that demonstrates how to retrieve statistics about the USDT smart contract: ``` diff --git a/docs/Schema/Polygon/balance.md b/docs/Schema/Polygon/balance.md index d8d612f..6de0028 100644 --- a/docs/Schema/Polygon/balance.md +++ b/docs/Schema/Polygon/balance.md @@ -27,7 +27,7 @@ description: "Get balance or balance history for any address or smart contract o The `address` api also allow you pull balance details including balance history. -You can filter using currency smart contract address and get balance for specific currency. In case of native currency, you can just mention "MATIC". +You can filter using currency smart contract address and get balance for specific currency. In case of native currency, you can just mention "MATIC". The balance API is particularly useful for treasury dashboards, portfolio trackers, and reconciliation workflows where you need current or historical token holdings for an address across MATIC and ERC-20 assets on Polygon. Here is an example on getting balance of [0x198905a3e2e3ffeb20169adf9ceaf0f9e66c35b9](https://explorer.bitquery.io/matic/address/0x198905a3e2e3ffeb20169adf9ceaf0f9e66c35b9): diff --git a/docs/Schema/Polygon/overview.md b/docs/Schema/Polygon/overview.md index 15d4d63..36ddfb9 100644 --- a/docs/Schema/Polygon/overview.md +++ b/docs/Schema/Polygon/overview.md @@ -50,6 +50,8 @@ Let's dive in and explore the Polygon API in following chapters. - **Affordable DeFi analytics** — track DEX volume and lending protocol activity with mainnet-like fields at lower per-query cost on-chain - **Cross-chain bridges** — relate Polygon **transfers** and **coinpath** results to bridge contracts and counterparties on other networks - **Growth metrics** — use **active addresses** and transfer counts for ecosystem reporting and user-acquisition dashboards +- **Enterprise loyalty and NFT programs** — brands deploying loyalty tokens, digital collectibles, or supply-chain credentials on Polygon can monitor issuance, redemption, and holder engagement through transfer and contract activity +- **Corporate payment rails** — low-fee MATIC transfers suit high-volume B2B and payroll disbursements; enterprises can reconcile settlements and generate audit-ready reports from on-chain data ## Related Resources diff --git a/docs/Schema/algorand/address.md b/docs/Schema/algorand/address.md index 7ee0982..7c1946c 100644 --- a/docs/Schema/algorand/address.md +++ b/docs/Schema/algorand/address.md @@ -8,6 +8,8 @@ keywords: ["Algorand API", "Algorand Address", "Bitquery", "GraphQL"] The `address` field allows us to fetch information about a specific address or a list of addresses from the Algorand blockchain. +Algorand addresses hold ALGO balances and may also hold ASA (Algorand Standard Asset) tokens. The address API lets you look up an account's native balance, any human-readable annotation, and related metadata. This is useful for wallet interfaces, account verification tools, and portfolio dashboards that need a quick snapshot of an Algorand account. + Here is an example that demonstrates how to retrieve basic information about a specific address: ``` diff --git a/docs/Schema/algorand/overview.md b/docs/Schema/algorand/overview.md index 3fe6e41..2722545 100644 --- a/docs/Schema/algorand/overview.md +++ b/docs/Schema/algorand/overview.md @@ -38,6 +38,8 @@ Algorand is a pure proof-of-stake layer 1 with fast finality, native **ALGO** tr - **ASA and ALGO treasury tracking** — monitor balances and transfer history for assets and accounts - **dApp and DeFi analytics** — volume and participation around apps, pools, or known program IDs - **Cross-account tracing** — use coinpath to follow ASA or ALGO through several hops +- **Government and CBDC programs** — sovereign issuers and institutions piloting digital currencies or regulated asset tokens on Algorand can track issuance, circulation, and redemption through ASA transfer and smart-contract-call queries +- **Enterprise asset tokenization** — companies tokenizing bonds, real estate, or carbon credits as ASAs can monitor holder distributions, settlement volumes, and compliance-relevant transfer patterns ## Related Resources diff --git a/docs/Schema/binance_smart_chain/activeaddresses.md b/docs/Schema/binance_smart_chain/activeaddresses.md index ac7a23d..155184a 100644 --- a/docs/Schema/binance_smart_chain/activeaddresses.md +++ b/docs/Schema/binance_smart_chain/activeaddresses.md @@ -26,6 +26,8 @@ description: "Query active addresses and counts on BNB Smart Chain." The `activeAddresses` field allows us to retrieve details about the active addresses from the BNB blockchain. +Active addresses count distinct wallets that participated in transfers on BSC during a given period—a key engagement metric for ecosystem dashboards, DeFi protocol growth reports, and investor-facing analytics. You can filter by currency, amount thresholds, sender/receiver roles, and date ranges to segment the count by token, whale activity, or specific time windows. + Here is an example that demonstrates how to retrieve the number of active addresses from the BNB blockchain: ``` diff --git a/docs/Schema/binance_smart_chain/address.md b/docs/Schema/binance_smart_chain/address.md index 69630d2..d313c4c 100644 --- a/docs/Schema/binance_smart_chain/address.md +++ b/docs/Schema/binance_smart_chain/address.md @@ -24,6 +24,8 @@ description: "Look up address balances, annotations, and smart contract details The `address` allows us to retrieve information about a specific address. +On BNB Smart Chain, addresses follow the same EVM model as Ethereum: EOAs hold BNB and interact with contracts, while contract addresses expose BEP-20 token metadata, protocol type, and on-chain attributes. The address API returns balance, annotation, balance history, and smart contract details. Use it for wallet lookups, token supply checks, and verifying contract properties before querying transfers or DEX activity on BSC. + Here is an example that demonstrates how to retrieve basic information about the USDT smart contract: ``` diff --git a/docs/Schema/binance_smart_chain/addresstats.md b/docs/Schema/binance_smart_chain/addresstats.md index 0d0c22f..8d70364 100644 --- a/docs/Schema/binance_smart_chain/addresstats.md +++ b/docs/Schema/binance_smart_chain/addresstats.md @@ -25,6 +25,8 @@ description: "Get address balance history and aggregate statistics on BNB Smart The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics aggregate a BSC address's lifetime activity into a single response: total BNB and token amounts sent and received, transaction counts, fee totals, distinct currency counts, and the number of active days. This helps compliance teams profile addresses, exchange operators build account-health dashboards, and analytics products surface whale or bot behavior without replaying individual transactions. + Here is an example that demonstrates how to retrieve statistics about the USDT smart contract: ``` diff --git a/docs/Schema/binance_smart_chain/overview.md b/docs/Schema/binance_smart_chain/overview.md index 6cfea0d..282d073 100644 --- a/docs/Schema/binance_smart_chain/overview.md +++ b/docs/Schema/binance_smart_chain/overview.md @@ -40,6 +40,7 @@ BNB Smart Chain (BSC) is an EVM-compatible network where **BNB** pays gas and an - **DEX and token analytics** — pair volumes, liquidity events, and trader behavior on BSC-native markets - **Whale and treasury monitoring** — large transfers, contract wallets, and recurring payout patterns - **Ecosystem growth metrics** — active addresses, new contracts, and transfer counts over time +- **Enterprise token operations** — businesses issuing BEP-20 loyalty, reward, or in-game tokens can track distribution, holder activity, and redemption patterns at scale on BSC's low-fee infrastructure ## Related Resources diff --git a/docs/Schema/bitcoin/addressstats.md b/docs/Schema/bitcoin/addressstats.md index ef5a9d5..72f1f41 100644 --- a/docs/Schema/bitcoin/addressstats.md +++ b/docs/Schema/bitcoin/addressstats.md @@ -24,6 +24,8 @@ description: "Get address balance and history on the Bitcoin blockchain. Also, g The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics provide an aggregate profile of a Bitcoin address: total sent and received amounts, transaction counts, fee totals, and the number of active days. This is useful for risk scoring, compliance profiling, and building explorer-style address summary pages without pulling individual transaction history. Because Bitcoin uses a UTXO model, these aggregates are derived from input and output activity rather than account-level state. + Here is an example that demonstrates how to retrieve statistics about a specific address; there is a balance field, too; please avoid using it; if you require a BTC balance, then please use [this API](https://docs.bitquery.io/v1/docs/examples/Bitcoin/bitcoin-address-api). ``` diff --git a/docs/Schema/bitcoin/overview.md b/docs/Schema/bitcoin/overview.md index e8163a8..382dd24 100644 --- a/docs/Schema/bitcoin/overview.md +++ b/docs/Schema/bitcoin/overview.md @@ -39,6 +39,8 @@ Bitcoin is the original UTXO blockchain; **BTC** moves only through transaction - **Exchange and custody reconciliation** — match deposits and withdrawals to UTXO-level movements - **Compliance and investigations** — follow coinpath across hops with block and tx context - **Omni and colored-coin style analytics** — track legacy token layers that ride on Bitcoin transactions +- **Institutional treasury management** — corporations holding BTC on their balance sheet can automate proof-of-reserves, cold-wallet audits, and board-level reporting by querying address balances and UTXO histories +- **Regulatory and AML workflows** — compliance teams at exchanges, banks, and OTC desks can trace coinpath flows to meet travel-rule obligations and flag high-risk transaction patterns ## Related Resources diff --git a/docs/Schema/cardano/address.md b/docs/Schema/cardano/address.md index 7337ce5..de203cd 100644 --- a/docs/Schema/cardano/address.md +++ b/docs/Schema/cardano/address.md @@ -8,6 +8,7 @@ keywords: ["Cardano API", "Cardano Address", "Bitquery", "GraphQL"] The Address API schema returns information about a wallet. The schema includes the following fields: +Cardano uses two address types: payment addresses for value transfer and stake addresses for delegation. The address API returns balance and annotation for a given address. This is useful for wallet interfaces, staking dashboards, and explorer backends that need a quick account overview in Cardano's eUTXO model. ``` query MyQuery { diff --git a/docs/Schema/cardano/addressstats.md b/docs/Schema/cardano/addressstats.md index 4a39026..bff3f98 100644 --- a/docs/Schema/cardano/addressstats.md +++ b/docs/Schema/cardano/addressstats.md @@ -8,6 +8,7 @@ keywords: ["Cardano API", "Cardano Address Stats", "Bitquery", "GraphQL"] The AddressStats API schema returns information about a wallet on its inflows, outflows and activity. The schema includes the following fields: +Address statistics provide aggregate metrics for a Cardano address: transaction counts, sent and received amounts, fee totals, and active-day counts. These summaries help staking platforms, compliance tools, and portfolio trackers assess an address's activity profile without replaying individual eUTXO transactions. ``` query MyQuery { diff --git a/docs/Schema/cardano/coinpath.md b/docs/Schema/cardano/coinpath.md index 7ef1a1a..959b356 100644 --- a/docs/Schema/cardano/coinpath.md +++ b/docs/Schema/cardano/coinpath.md @@ -8,6 +8,8 @@ keywords: ["Cardano API", "Cardano Coinpath", "Bitquery", "GraphQL"] Coinpath APIs are a set of money-tracing APIs that help you track funds from one address to another. +Cardano uses an **eUTXO** model, so coinpath traces how ADA and native tokens flow through transaction outputs across multiple hops. This is valuable for compliance investigations, treasury auditing, and understanding multi-step fund flows in Cardano's native-token ecosystem. The API returns depth, amounts, currency details (including policy-based native tokens), and sender/receiver metadata for each hop in the trace. + ``` query MyQuery { cardano { diff --git a/docs/Schema/cardano/mints.md b/docs/Schema/cardano/mints.md index 2eabd23..905fe0f 100644 --- a/docs/Schema/cardano/mints.md +++ b/docs/Schema/cardano/mints.md @@ -8,6 +8,7 @@ keywords: ["Cardano API", "Cardano Mints", "Bitquery", "GraphQL"] The Mints API query returns information about the mints on the Cardano network. A mint is an event where new tokens are created. The query returns information about the block that the mint occurred in, the amount of tokens minted, the transaction that minted the tokens, and the currency that was minted. +On Cardano, native tokens are defined by **minting policies** rather than smart contracts: any transaction can mint or burn tokens if it satisfies the associated policy script. This API surfaces those mint and burn events with policy IDs, asset names, and quantities. Use it to track token issuance for NFT collections, fungible-token launches, and supply-management workflows where you need to verify on-chain minting activity against expected schedules or caps. ``` query MyQuery { diff --git a/docs/Schema/cardano/overview.md b/docs/Schema/cardano/overview.md index 07a89e7..0a6d0fb 100644 --- a/docs/Schema/cardano/overview.md +++ b/docs/Schema/cardano/overview.md @@ -42,6 +42,7 @@ Cardano uses an **eUTXO** model: **ADA** and **native tokens** live in transacti - **Native asset (token) analytics** — issuance, circulation, and holder flows for policy-specific assets - **Staking and delegation views** — combine transaction and certificate-related fields for participation metrics (where exposed) - **Wallet and explorer backends** — address histories, UTXO/eUTXO-aware transfers, and recent blocks +- **Enterprise identity and credentials** — organizations issuing verifiable credentials, supply-chain tokens, or governance NFTs on Cardano can monitor minting policies, holder distribution, and lifecycle events through native-asset and transfer queries ## Related Resources diff --git a/docs/Schema/celo/address.md b/docs/Schema/celo/address.md index 4637b4c..b19109f 100644 --- a/docs/Schema/celo/address.md +++ b/docs/Schema/celo/address.md @@ -8,6 +8,8 @@ keywords: ["Celo API", "Celo Address", "Bitquery", "GraphQL"] The `address` allows us to retrieve information about a specific address. +Celo is an EVM-compatible, mobile-first network with native stablecoins such as cUSD and cEUR alongside CELO for governance. The address API returns CELO balance, annotations, balance history, and smart contract details including token metadata. Use it for mobile wallet lookups, stablecoin issuer verification, and building account overview pages for Celo's financial-inclusion ecosystem. + Here is an example that demonstrates how to retrieve basic information about the a smart contract: ``` diff --git a/docs/Schema/celo/addresstats.md b/docs/Schema/celo/addresstats.md index b501fd1..d0da76a 100644 --- a/docs/Schema/celo/addresstats.md +++ b/docs/Schema/celo/addresstats.md @@ -8,6 +8,8 @@ keywords: ["Celo API", "Celo Address Stats", "Bitquery", "GraphQL"] The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics aggregate a Celo address's lifetime activity: total sent and received amounts, transaction counts, fee expenditure, and active-day counts across CELO and stablecoin transfers. This is useful for compliance profiling, remittance-corridor analysis, and building account health dashboards for Celo's mobile-payment ecosystem. + Here is an example that demonstrates how to retrieve statistics about a smart contract: ``` diff --git a/docs/Schema/celo/overview.md b/docs/Schema/celo/overview.md index d40173d..09d4152 100644 --- a/docs/Schema/celo/overview.md +++ b/docs/Schema/celo/overview.md @@ -41,6 +41,7 @@ Celo is a mobile-first EVM-compatible network with native stable-value assets su - **Stablecoin circulation** — track cUSD/cEUR (and related assets) mint, burn, and transfer patterns - **Mobile and remittance analytics** — monitor high-volume payment contracts and wallet cohorts - **DeFi monitoring** — DEX volumes, pool events, and protocol treasuries on Celo +- **Financial inclusion and NGO programs** — organizations running micro-payment, aid-disbursement, or mobile-banking programs on Celo can audit fund flows, stablecoin distribution, and beneficiary wallet activity for donor and regulatory reporting ## Related Resources diff --git a/docs/Schema/cosmos/address.md b/docs/Schema/cosmos/address.md index 740805f..564c569 100644 --- a/docs/Schema/cosmos/address.md +++ b/docs/Schema/cosmos/address.md @@ -8,6 +8,8 @@ keywords: ["Cosmos API", "Cosmos Address", "Bitquery", "GraphQL"] The `address` field allows us to retrieve basic information about a particular address or list of address like balance, annotation, etc. +Cosmos addresses identify accounts across Cosmos SDK chains. The address API returns balance and annotation for a given account. Use it for validator dashboards, wallet interfaces, and staking-product backends that need a quick account overview on Cosmos Hub, Crypto.org, or Heimdall networks. + Here is an exmaple that demonstrates retrival of balance for an address: ``` diff --git a/docs/Schema/cosmos/coinpath.md b/docs/Schema/cosmos/coinpath.md index a34e6cf..d21695d 100644 --- a/docs/Schema/cosmos/coinpath.md +++ b/docs/Schema/cosmos/coinpath.md @@ -8,6 +8,8 @@ keywords: ["Cosmos API", "Cosmos Coinpath", "Bitquery", "GraphQL"] The coinpath API provides detailed information about the money flow using coinpath technology. +On Cosmos SDK chains, value moves through **messages** (bank sends, IBC transfers, staking rewards) rather than UTXO outputs or EVM internal transactions. Coinpath traces these message-based flows across multiple hops, letting you follow ATOM, CRO, or other native assets through intermediary accounts. This is useful for staking-reward audits, IBC corridor analysis, and compliance investigations across Cosmos Hub, Crypto.org, or Heimdall networks. +
diff --git a/docs/Schema/cosmos/overview.md b/docs/Schema/cosmos/overview.md index 2d66886..f19d377 100644 --- a/docs/Schema/cosmos/overview.md +++ b/docs/Schema/cosmos/overview.md @@ -45,6 +45,7 @@ The **Cosmos** ecosystem is built on **Tendermint** consensus and the **IBC** in - **Multi-network operations** — compare **Cosmos Hub**, **Heimdall**, and **Crypto.org** traffic using the same schema with different `network` values - **Staking products** — aggregate delegate, undelegate, and reward **messages** for validators and delegators - **IBC observability** — when indexing covers IBC, relate **transfers** and **messages** to cross-chain volume and corridor health +- **Institutional staking and validator management** — custodians and staking-as-a-service providers can track delegation, reward accrual, and validator performance across Cosmos networks for client reporting and SLA compliance ## Related Resources diff --git a/docs/Schema/ethereum/activeaddresses.md b/docs/Schema/ethereum/activeaddresses.md index 91fdc7b..4cf5c24 100644 --- a/docs/Schema/ethereum/activeaddresses.md +++ b/docs/Schema/ethereum/activeaddresses.md @@ -31,6 +31,8 @@ description: "Access historical and current Ethereum active address metrics with The `activeAddresses` field allows us to retrieve details about the active addresses from the Ethereum blockchain. +Active addresses measure network engagement: they count distinct addresses that participated in transfers (as sender or receiver) during a given period. This is a key metric for ecosystem health dashboards, investor reports, and growth analytics—showing whether the network is gaining or losing participants over time. You can filter by currency, amount thresholds, and date ranges to narrow the count to specific tokens, whales, or time windows. + Here is an example that demonstrates how to retrieve the number of active addresses from the Ethereum blockchain: ``` diff --git a/docs/Schema/ethereum/address.md b/docs/Schema/ethereum/address.md index dbf1110..4971998 100644 --- a/docs/Schema/ethereum/address.md +++ b/docs/Schema/ethereum/address.md @@ -31,6 +31,8 @@ description: "Explore specific address details, balances, and smart contract att The `address` allows us to retrieve information about a specific address. +On Ethereum, an address can be an externally owned account (EOA) or a smart contract. The address API returns the current ETH balance, human-readable annotations where available, and—when the address is a contract—details such as contract type, protocol type, token metadata (decimals, symbol, token standard), and on-chain attributes. Use this for wallet pages, portfolio dashboards, token supply lookups, and quick contract verification before diving into transfer or event history. + Here is an example that demonstrates how to retrieve basic information about the USDT smart contract: ``` diff --git a/docs/Schema/ethereum/addresstats.md b/docs/Schema/ethereum/addresstats.md index 56a5737..02d46df 100644 --- a/docs/Schema/ethereum/addresstats.md +++ b/docs/Schema/ethereum/addresstats.md @@ -31,6 +31,8 @@ description: "Explore comprehensive address statistics, including counts, aggreg The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics provide an aggregate profile of an Ethereum address in a single query: total sent and received amounts, transaction counts (including calls and called transactions), fee expenditure, the number of distinct currencies involved, and the count of active days. This is useful for compliance profiling, risk scoring, explorer summary pages, and any workflow where you need a high-level view of an address's lifetime activity without pulling every individual transaction. + Here is an example that demonstrates how to retrieve statistics about the USDT smart contract: ``` diff --git a/docs/Schema/ethereum/overview.md b/docs/Schema/ethereum/overview.md index 719575b..81ba9eb 100644 --- a/docs/Schema/ethereum/overview.md +++ b/docs/Schema/ethereum/overview.md @@ -45,6 +45,8 @@ Let's dive in and explore the Ethereum data available through Bitquery API. - **DeFi and market data** — rank tokens, pools, and DEX volume for research terminals or trading products - **Institutional reporting** — tie **transfers**, balances, and **active addresses** to treasury or compliance views - **Investigations** — use **coinpath** to map how ETH or tokens moved through mixers, bridges, or nested contracts +- **Enterprise compliance and AML** — regulated entities can automate transaction monitoring, sanctions screening, and audit trails by combining coinpath with address and contract metadata across ERC-20 flows +- **Real-world asset (RWA) tokenization** — track issuance, transfers, and holder distribution of tokenized securities, bonds, or real-estate assets deployed as smart contracts on Ethereum ## Related Resources diff --git a/docs/Schema/ethereum2/attestations.md b/docs/Schema/ethereum2/attestations.md index 15af2c1..5c48998 100644 --- a/docs/Schema/ethereum2/attestations.md +++ b/docs/Schema/ethereum2/attestations.md @@ -22,6 +22,10 @@ description: "Query attestations, aggregation bits, and validators on the Beacon +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The attestations API allows you to query for attestations that have been submitted to the Ethereum 2.0 beacon chain. You can use this API to get information about the attestations themselves, such as the epoch number, slot number, and committee index. You can also get information about the block that the attestation was included in, such as the block root hash and timestamp. The below query lists the fields in the schema: ``` diff --git a/docs/Schema/ethereum2/attesterSlashings.md b/docs/Schema/ethereum2/attesterSlashings.md index c769bcf..d14fb55 100644 --- a/docs/Schema/ethereum2/attesterSlashings.md +++ b/docs/Schema/ethereum2/attesterSlashings.md @@ -22,6 +22,9 @@ description: "Query attester slashing evidence on the Beacon Chain." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: ``` query ($network: Ethereum2Network!) { diff --git a/docs/Schema/ethereum2/blocks.md b/docs/Schema/ethereum2/blocks.md index f2f8fe1..1b88a8c 100644 --- a/docs/Schema/ethereum2/blocks.md +++ b/docs/Schema/ethereum2/blocks.md @@ -22,6 +22,10 @@ description: "Query Beacon Chain blocks, roots, and consensus data." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Eth2 blocks API retrieves staking and validator information for a block. Here are the fields in the schema: ``` diff --git a/docs/Schema/ethereum2/deposits.md b/docs/Schema/ethereum2/deposits.md index c026e54..bf39070 100644 --- a/docs/Schema/ethereum2/deposits.md +++ b/docs/Schema/ethereum2/deposits.md @@ -22,6 +22,10 @@ description: "Query validator deposits on the Beacon Chain." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The deposits API allows you to query for deposits that have been made to the Ethereum 2.0 beacon chain. You can use this API to get information about the deposits themselves, such as the amount of ETH that was deposited, the validator that made the deposit, and the block that the deposit was included in. Below are the fields in the schema: ``` diff --git a/docs/Schema/ethereum2/overview.md b/docs/Schema/ethereum2/overview.md index bae8fbc..d7ae189 100644 --- a/docs/Schema/ethereum2/overview.md +++ b/docs/Schema/ethereum2/overview.md @@ -7,6 +7,10 @@ keywords: [Ethereum Beacon Chain API, Ethereum Beacon Chain GraphQL, Ethereum Be # Ethereum Beacon Chain API Overview +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Bitquery provides APIs to access Eth2 data. You can get info on the ethereum's staking model. It uses the Proof-of-stake, a consensus method that blockchain networks utilize to reach distributed consensus. These APIs provide details on validators, their staked amounts, their exits and so on. The easiest way to start is through the [Beacon Chain Explorer](https://explorer.bitquery.io/eth2) diff --git a/docs/Schema/ethereum2/proposerSlashings.md b/docs/Schema/ethereum2/proposerSlashings.md index 1fb6f53..34be2ff 100644 --- a/docs/Schema/ethereum2/proposerSlashings.md +++ b/docs/Schema/ethereum2/proposerSlashings.md @@ -22,6 +22,10 @@ description: "Query proposer slashing evidence on the Beacon Chain." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The proposerSlashings API returns a list of proposer slashings for a given Ethereum 2.0 network. A proposer slashing occurs when a validator is found to have double signed a block. The proposerSlashings API can be used to get information about proposer slashings, such as the date of the slashing, the block height, and the validator's index. diff --git a/docs/Schema/ethereum2/validatorUpdates.md b/docs/Schema/ethereum2/validatorUpdates.md index df8d454..afe5d19 100644 --- a/docs/Schema/ethereum2/validatorUpdates.md +++ b/docs/Schema/ethereum2/validatorUpdates.md @@ -22,6 +22,10 @@ description: "Query validator status updates on the Beacon Chain." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + ``` query ($network: Ethereum2Network!) { ethereum2(network: $network) { diff --git a/docs/Schema/ethereum2/voluntaryExits.md b/docs/Schema/ethereum2/voluntaryExits.md index 4b968e5..169fe2a 100644 --- a/docs/Schema/ethereum2/voluntaryExits.md +++ b/docs/Schema/ethereum2/voluntaryExits.md @@ -22,6 +22,10 @@ description: "Query voluntary validator exits on the Beacon Chain." +:::caution Deprecated +Bitquery has stopped supporting the Ethereum Beacon Chain (ETH2) API. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + ``` query ($network: Ethereum2Network!) { ethereum2(network: $network) { diff --git a/docs/Schema/filecoin/address.md b/docs/Schema/filecoin/address.md index 2cba3c7..926764b 100644 --- a/docs/Schema/filecoin/address.md +++ b/docs/Schema/filecoin/address.md @@ -8,7 +8,7 @@ keywords: ["Filecoin API", "Filecoin Address", "Bitquery", "GraphQL"] The Address API allows you to query information about addresses on the Filecoin blockchain. - +Filecoin addresses (actors) come in several formats—f0 (ID), f1 (secp256k1), f2 (actor/contract), and f3 (BLS). The address API returns the address itself, any annotation label, and the FIL balance. Use it for miner lookups, client account verification, and wallet dashboards that need a quick snapshot before querying messages or deal activity. ``` query MyQuery { diff --git a/docs/Schema/filecoin/arguments.md b/docs/Schema/filecoin/arguments.md index 6f35a13..d9dee85 100644 --- a/docs/Schema/filecoin/arguments.md +++ b/docs/Schema/filecoin/arguments.md @@ -4,6 +4,10 @@ description: "Query Filecoin GraphQL arguments data using Bitquery GraphQL API. keywords: ["Filecoin API", "Filecoin Arguments", "Bitquery", "GraphQL"] --- +# Arguments + +The Filecoin arguments API exposes decoded parameters from actor method calls on the Filecoin network. Actor methods—such as storage-deal proposals, miner sector commitments, and payment-channel updates—carry structured inputs that this API surfaces as queryable fields. Use it when you need to inspect what was passed into a specific actor call rather than just whether a message succeeded, for example to audit deal terms, verify miner commitments, or analyze market-actor interactions programmatically. + ## Related Resources - [Filecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/filecoin/overview) diff --git a/docs/Schema/filecoin/messages.md b/docs/Schema/filecoin/messages.md index 56fad2e..24ee1f8 100644 --- a/docs/Schema/filecoin/messages.md +++ b/docs/Schema/filecoin/messages.md @@ -14,6 +14,8 @@ According to the [official Filecoin documentation](https://docs.filecoin.io/basi > So, in other words, a block describes all changes to the network state > in a given epoch. +Messages are the primary unit of on-chain activity on Filecoin—analogous to transactions on other networks. Every storage deal proposal, miner sector commitment, payment, and governance action is expressed as a message between actors. The messages API lets you query senders, receivers, method names, gas costs, and execution outcomes. Use it for network activity monitoring, miner operations dashboards, and correlating on-chain messages with storage-deal lifecycles. + ``` query ($network: FilecoinNetwork!, $dateFormat: String!, $from: ISO8601DateTime, $till: ISO8601DateTime) { filecoin(network: $network) { diff --git a/docs/Schema/filecoin/overview.md b/docs/Schema/filecoin/overview.md index 79288cf..f97b5e5 100644 --- a/docs/Schema/filecoin/overview.md +++ b/docs/Schema/filecoin/overview.md @@ -35,6 +35,7 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T - **Storage economics** — relate message and call patterns to deal activity, miner behavior, and network utilization - **Miner and client reporting** — summarize transfers and address-level flows for operational or financial reporting - **Forensics** — use **coinpath** to reconstruct how FIL moved across wallets tied to deals or market actors +- **Enterprise data compliance** — organizations storing regulated data on Filecoin can audit deal lifecycles, storage-provider relationships, and FIL payment flows for procurement and data-residency reporting ## Related Resources diff --git a/docs/Schema/flow/address.md b/docs/Schema/flow/address.md index b8d1f5d..3200e3f 100644 --- a/docs/Schema/flow/address.md +++ b/docs/Schema/flow/address.md @@ -8,6 +8,8 @@ keywords: ["Flow API", "Flow Address", "Bitquery", "GraphQL"] The Flow Address API offers basic information about addresses from the Flow Blockchain. +Flow addresses identify accounts that can hold FLOW tokens, NFT collections, and Cadence resources. The address API returns balance, annotation, and account-level metadata. Use it for wallet lookups, collection dashboards, and verifying account identity before drilling into events or transfer history. +
Filtering Addresses diff --git a/docs/Schema/flow/overview.md b/docs/Schema/flow/overview.md index 4d8fdf8..822aaa0 100644 --- a/docs/Schema/flow/overview.md +++ b/docs/Schema/flow/overview.md @@ -33,6 +33,7 @@ Flow targets consumer-scale apps: NFT collections (for example NBA Top Shot), ga - **NFT and collection analytics** — monitor mints, transfers, and marketplace events for a contract or collection - **Game and app telemetry** — aggregate user- or contract-driven events for retention and economy dashboards - **Account flow tracing** — follow FLOW or tokens through several hops for treasury or compliance workflows +- **Enterprise IP and brand partnerships** — major brands (e.g., sports leagues, entertainment studios) launching digital collectibles on Flow can track minting, secondary-market transfers, and royalty events for revenue reporting and rights management ## Related Resources diff --git a/docs/Schema/hedera/address.md b/docs/Schema/hedera/address.md index 38b1548..ec93130 100644 --- a/docs/Schema/hedera/address.md +++ b/docs/Schema/hedera/address.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Address", "Bitquery", "GraphQL"] # Address +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Address API provides basic information about addresses on the Hedera Blockchain. It offers information about various aspects, including the balance of the native currency associated with the address, any available annotations, and more. Here's an example that shows how to retrieve the balance of an address: diff --git a/docs/Schema/hedera/arguments.md b/docs/Schema/hedera/arguments.md index f848f01..25f94e5 100644 --- a/docs/Schema/hedera/arguments.md +++ b/docs/Schema/hedera/arguments.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Arguments", "Bitquery", "GraphQL"] # Arguments +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Arguments API provides you with information about event arguments. It offers valuable information about various aspects, such as the specific values of event arguments, their corresponding types, and even the transaction where the event originally occurred. Here's an example that demonstrates how to extract arguments from a transaction: diff --git a/docs/Schema/hedera/calls.md b/docs/Schema/hedera/calls.md index b0c0141..47c5485 100644 --- a/docs/Schema/hedera/calls.md +++ b/docs/Schema/hedera/calls.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Calls", "Bitquery", "GraphQL"] # Calls +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Calls API provides you with information about calls made on Hedera Blockchain. It offers information about various aspects, such as call inputs, result of the calls, and much more. Here's an example that demonstrates how to extract calls fromm a transaction: diff --git a/docs/Schema/hedera/coinpath.md b/docs/Schema/hedera/coinpath.md index 91c01d6..37dd9c3 100644 --- a/docs/Schema/hedera/coinpath.md +++ b/docs/Schema/hedera/coinpath.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Coinpath", "Bitquery", "GraphQL"] # Coinpath +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Coinpath API offers information related to the flow of funds on the Hedera Blockchain.
diff --git a/docs/Schema/hedera/inputs.md b/docs/Schema/hedera/inputs.md index 86fb644..26508c7 100644 --- a/docs/Schema/hedera/inputs.md +++ b/docs/Schema/hedera/inputs.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Inputs", "Bitquery", "GraphQL"] # Inputs +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Inputs API provides information about transaction inputs on the Hedera Blockchain. Here's an example showcasing how to retrieve input data: diff --git a/docs/Schema/hedera/messages.md b/docs/Schema/hedera/messages.md index 7bb8741..5d98dbf 100644 --- a/docs/Schema/hedera/messages.md +++ b/docs/Schema/hedera/messages.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Messages", "Bitquery", "GraphQL"] # Messages +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Messages API provides information about blockchain messages on the Hedera Blockchain. Here's an exmaple showcasing how to fetch message data: diff --git a/docs/Schema/hedera/outputs.md b/docs/Schema/hedera/outputs.md index afc2a7e..67ae575 100644 --- a/docs/Schema/hedera/outputs.md +++ b/docs/Schema/hedera/outputs.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Outputs", "Bitquery", "GraphQL"] # Outputs +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Outputs API provides information about transaction outputs on the Hedera Blockchain.
diff --git a/docs/Schema/hedera/overview.md b/docs/Schema/hedera/overview.md index 7bc2ed9..d64981d 100644 --- a/docs/Schema/hedera/overview.md +++ b/docs/Schema/hedera/overview.md @@ -7,6 +7,10 @@ keywords: [Hedera API, Hedera GraphQL, Hedera blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Our API makes it easy to access different types of data from the Hedera blockchain, like addresses, arguments, calls, and more. ## Getting Started diff --git a/docs/Schema/hedera/transactions.md b/docs/Schema/hedera/transactions.md index d6ec609..8128192 100644 --- a/docs/Schema/hedera/transactions.md +++ b/docs/Schema/hedera/transactions.md @@ -6,6 +6,10 @@ keywords: ["Hedera API", "Hedera Transactions", "Bitquery", "GraphQL"] # Transactions +:::caution Deprecated +Bitquery has stopped supporting the Hedera blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Transactions API offers insights into transactions on the Hedera Blockchain.
diff --git a/docs/Schema/ripple/accountRoots.md b/docs/Schema/ripple/accountRoots.md index e12b8d8..1f134cd 100644 --- a/docs/Schema/ripple/accountRoots.md +++ b/docs/Schema/ripple/accountRoots.md @@ -29,6 +29,8 @@ description: "Query AccountRoot fields for XRP Ledger accounts." +Account roots represent the fundamental ledger entry for each XRP Ledger account, storing the account's XRP balance, sequence number, flags, and trust-line or escrow settings. This API lets you query these base-layer account properties for compliance checks, account verification, and understanding an account's ledger state beyond just its transaction history. + ``` query MyQuery { ripple(network: ripple) { diff --git a/docs/Schema/ripple/addressStats.md b/docs/Schema/ripple/addressStats.md index b49c94e..7e39361 100644 --- a/docs/Schema/ripple/addressStats.md +++ b/docs/Schema/ripple/addressStats.md @@ -32,6 +32,8 @@ description: "Query aggregate address statistics on the XRP Ledger." The `addressstats` field allows us to retrieves statistics related to blockchain addresses. +Address statistics provide aggregate metrics for an XRP Ledger account: transaction counts, sent and received amounts across XRP and issued currencies, fee totals, and active-day counts. These summaries are useful for compliance profiling, payment corridor analysis, and building explorer-style account pages without scanning every ledger entry. + Here is an example that demonstrates how to retrieve statistics about the USDT smart contract: ``` diff --git a/docs/Schema/ripple/blocks.md b/docs/Schema/ripple/blocks.md index cb78a2a..58cc597 100644 --- a/docs/Schema/ripple/blocks.md +++ b/docs/Schema/ripple/blocks.md @@ -29,7 +29,11 @@ description: "Query validated XRP Ledger ledgers (blocks), timestamps, and trans -Ripple Blocks API helps you get information on Blocks in the network. Below are the fields in the API: +Ripple Blocks API helps you get information on Blocks in the network. + +On the XRP Ledger, "blocks" correspond to validated **ledgers**—each ledger captures a snapshot of all account balances, trust lines, and offers at a specific sequence number. The blocks API returns ledger height, close time, hash, total XRP supply (`totalCoins`), and account-hash references. Use it for network-health dashboards, explorer backends displaying recent ledgers, and correlating transaction data to specific ledger versions. + +Below are the fields in the API: ``` query ($network: RippleNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) { diff --git a/docs/Schema/ripple/overview.md b/docs/Schema/ripple/overview.md index 8ac4772..fa0e3a8 100644 --- a/docs/Schema/ripple/overview.md +++ b/docs/Schema/ripple/overview.md @@ -45,6 +45,8 @@ The **XRP Ledger** (often called **Ripple** in market contexts) is **payment-cen - **Remittance and payments** — analyze high-volume payment traffic and bridge use of XRP between corridors - **DEX and liquidity** — monitor **offers**, fills, and trading-related transactions on the built-in order book - **Advanced ledger features** — study escrows, checks, payment channels, or NFTokens when querying those transaction families +- **Banking and institutional settlement** — financial institutions using XRP as a bridge asset or RippleNet corridors can reconcile ledger-level payment flows, escrow releases, and trust-line positions for treasury and regulatory reporting +- **Enterprise escrow and payment channel management** — businesses leveraging on-ledger escrows or payment channels for scheduled disbursements or streaming payments can track state changes and settlement outcomes programmatically ## Related Resources diff --git a/docs/Schema/solana/address.md b/docs/Schema/solana/address.md index 85b75a3..74b39d6 100644 --- a/docs/Schema/solana/address.md +++ b/docs/Schema/solana/address.md @@ -8,6 +8,8 @@ keywords: ["Solana API", "Solana Address", "Bitquery", "GraphQL"] The Solana address API gives you information of the balance of a wallet in SOL. +Solana addresses (public keys) can be regular wallets, token accounts, or program-derived addresses. The address API returns balance, annotation, and account-level metadata. Use it for wallet lookups, portfolio snapshots, or verifying whether an address is a known entity before diving into transfer or instruction history. + ``` query MyQuery { solana(network: solana) { diff --git a/docs/Schema/solana/blocks.md b/docs/Schema/solana/blocks.md index aa25599..e1223fd 100644 --- a/docs/Schema/solana/blocks.md +++ b/docs/Schema/solana/blocks.md @@ -6,7 +6,11 @@ keywords: ["Solana API", "Solana Blocks", "Bitquery", "GraphQL"] # Blocks -The Blocks API returns information about blocks on the Solana network. The fields in the schema include: +The Blocks API returns information about blocks on the Solana network. + +Solana blocks are produced at sub-second intervals by the current leader validator in the slot schedule. Each block contains a slot height, parent slot reference, transaction count, block hash, and aggregate rewards distributed to validators and stakers. Use the blocks API for network throughput monitoring, explorer-style recent-block feeds, and correlating on-chain activity to specific slots when analyzing instructions or transfers. + +The fields in the schema include: ``` query ($network: SolanaNetwork!,$from: ISO8601DateTime, $till: ISO8601DateTime) { diff --git a/docs/Schema/solana/instructions.md b/docs/Schema/solana/instructions.md index 845ba7a..f82063b 100644 --- a/docs/Schema/solana/instructions.md +++ b/docs/Schema/solana/instructions.md @@ -6,7 +6,11 @@ keywords: ["Solana API", "Solana Instructions", "Bitquery", "GraphQL"] # Instructions -The Solana instructions API allows you to query information about instructions that have been executed on the Solana blockchain. This information includes the program that executed the instruction, the accounts that were affected by the instruction, the data that was passed to the instruction, and the log message that was produced by the instruction. The schema includes the following fields: +The Solana instructions API allows you to query information about instructions that have been executed on the Solana blockchain. This information includes the program that executed the instruction, the accounts that were affected by the instruction, the data that was passed to the instruction, and the log message that was produced by the instruction. + +Instructions are the fundamental unit of execution on Solana—every transaction contains one or more instructions, each targeting a specific program (smart contract). Querying at the instruction level lets you analyze DeFi protocol interactions, NFT minting calls, and program-specific logic that transfer-level queries alone cannot reveal. Use this API for program analytics, debugging failed transactions, and building dashboards that break down activity by program and instruction type. + +The schema includes the following fields: ``` query ($network: SolanaNetwork!, $signature: String!) { diff --git a/docs/Schema/solana/overview.md b/docs/Schema/solana/overview.md index cdc0a72..4da6993 100644 --- a/docs/Schema/solana/overview.md +++ b/docs/Schema/solana/overview.md @@ -44,6 +44,8 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T - **Program analytics** — break down instruction mix and account usage for DeFi, NFT, or consumer programs - **Wallet and SPL portfolios** — aggregate token balances and transfer history per owner or token mint - **Validator economics** — combine **block rewards** with transaction fees for performance or yield reporting +- **Enterprise payment integration** — businesses accepting SOL or SPL tokens for commerce can reconcile high-throughput payment flows with sub-second finality, tying instruction-level data to order systems +- **Institutional program auditing** — fund administrators and protocol teams can verify program interactions, token mints, and authority changes for governance and risk reporting ## Related Resources diff --git a/docs/Schema/stellar/address.md b/docs/Schema/stellar/address.md index 6fb079a..8fff574 100644 --- a/docs/Schema/stellar/address.md +++ b/docs/Schema/stellar/address.md @@ -8,6 +8,8 @@ keywords: ["Stellar API", "Stellar Address", "Bitquery", "GraphQL"] Stellar Address API helps you get information on Address balance in the network. Below are the fields in the API: +Stellar addresses (public keys) identify accounts on the Stellar network. The address API returns balance, annotation, and account-level metadata. Use it for wallet lookups, anchor verification, and portfolio dashboards that need to resolve a Stellar account before querying operations, payments, or trust-line details. + ``` query ($network: StellarNetwork!) { stellar(network: $network) { diff --git a/docs/Schema/stellar/addressStats.md b/docs/Schema/stellar/addressStats.md index 8e6e8e1..adb5eb0 100644 --- a/docs/Schema/stellar/addressStats.md +++ b/docs/Schema/stellar/addressStats.md @@ -8,6 +8,7 @@ keywords: ["Stellar API", "Stellar Address Stats", "Bitquery", "GraphQL"] Stellar AddressStats API helps you get information on Addresses in the network. Below are the fields in the API: +Address statistics aggregate a Stellar account's lifetime activity: transaction counts, sent and received amounts across XLM and issued assets, fee totals, and active-day metrics. These are useful for compliance profiling, anchor due diligence, and building account summary pages for explorers or institutional dashboards. ``` diff --git a/docs/Schema/stellar/balanceEffects.md b/docs/Schema/stellar/balanceEffects.md index 67041d4..b148247 100644 --- a/docs/Schema/stellar/balanceEffects.md +++ b/docs/Schema/stellar/balanceEffects.md @@ -8,6 +8,8 @@ keywords: ["Stellar API", "Stellar Balance Effects", "Bitquery", "GraphQL"] The Stellar BalanceEffects API allows you to get information about the balance changes of an account.Below are the fields in the API: +Balance effects capture every change to an account's balance as a result of operations—payments, path payments, merges, fees, and inflation distributions. This API surface is useful when you need a complete ledger of credits and debits for an account or asset, for reconciliation, audit trails, or building balance-over-time charts. + ``` query ($network: StellarNetwork!, $address: String!, $from: ISO8601DateTime, $till: ISO8601DateTime, $limit: Int!, $offset: Int!) { stellar(network: $network) { diff --git a/docs/Schema/stellar/blocks.md b/docs/Schema/stellar/blocks.md index ee7c5fd..92bf359 100644 --- a/docs/Schema/stellar/blocks.md +++ b/docs/Schema/stellar/blocks.md @@ -6,7 +6,11 @@ keywords: ["Stellar API", "Stellar Blocks", "Bitquery", "GraphQL"] # Blocks -Stellar Blocks API helps you get information on Blocks in the network. Below are the fields in the API: +Stellar Blocks API helps you get information on Blocks in the network. + +On Stellar, blocks correspond to closed **ledgers**—each ledger captures the network state at a sequence number, including total lumens in circulation, the fee pool, base fee, and base reserve. The blocks API exposes these economic parameters alongside height, hash, and protocol version. Use it for network-health monitoring, explorer backends, and tracking Stellar protocol upgrades or reserve-requirement changes over time. + +Below are the fields in the API: ``` query ($network: StellarNetwork!, $from: ISO8601DateTime, $till: ISO8601DateTime) { diff --git a/docs/Schema/stellar/effectArguments.md b/docs/Schema/stellar/effectArguments.md index 24208cd..2feb2f6 100644 --- a/docs/Schema/stellar/effectArguments.md +++ b/docs/Schema/stellar/effectArguments.md @@ -6,7 +6,9 @@ keywords: ["Stellar API", "Stellar Effect Arguments", "Bitquery", "GraphQL"] # Effects Arguments -
Filtering Transfers
+Effect arguments expose the structured parameters attached to Stellar ledger effects—balance changes, trust-line modifications, offer fills, and other state transitions that result from operations. Where the **effects** API tells you *what changed*, effect arguments tell you the *input parameters and context* behind that change. Use this API for detailed reconciliation, audit trails, and understanding exactly how an operation altered account or asset state on the Stellar network. + +
Filtering Effect Arguments
## Fields diff --git a/docs/Schema/stellar/overview.md b/docs/Schema/stellar/overview.md index 6193939..114dd42 100644 --- a/docs/Schema/stellar/overview.md +++ b/docs/Schema/stellar/overview.md @@ -39,6 +39,7 @@ Stellar is a multi-asset ledger: **XLM** is the native asset, while anchors and - **SDEX and anchor analytics** — volumes, spreads, and offer books for on-ledger markets and issued assets - **Cross-border payment monitoring** — path payments, corridor assets, and liquidity pool usage - **Account and asset compliance** — reconstruct activity from operations, effects, and transfers +- **Enterprise remittance and CBDC pilots** — financial institutions and central banks running tokenized fiat or remittance corridors on Stellar can reconcile payment operations, anchor trust-line balances, and settlement flows for regulatory and operational reporting ## Related Resources diff --git a/docs/Schema/tron/address.md b/docs/Schema/tron/address.md index 1c718f6..5b9c9ef 100644 --- a/docs/Schema/tron/address.md +++ b/docs/Schema/tron/address.md @@ -24,6 +24,8 @@ description: "Look up address balances and history on Tron." The `address` field allows us to retrieve details about address or smart contract from Tron blockchain. +Tron addresses hold TRX balances and may be associated with TRC-20 token contracts. The address API returns balance, annotation, and smart contract metadata when the address is a contract. Use it for wallet lookups, token supply queries, and verifying contract attributes on the Tron network. + Here is an example that demonstrates use `address` query: ``` diff --git a/docs/Schema/tron/overview.md b/docs/Schema/tron/overview.md index 0cd6ac7..b2024f4 100644 --- a/docs/Schema/tron/overview.md +++ b/docs/Schema/tron/overview.md @@ -46,6 +46,7 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T - **Stablecoin analytics** — monitor USDT and other TRC-20 volume, counterparties, and corridors at scale - **dApp monitoring** — track **DEX trades**, contract calls, and **arguments** for consumer or B2B dashboards - **Compliance workflows** — combine **coinpath** with contract metadata to explain complex multi-hop flows +- **Enterprise cross-border settlement** — companies using TRC-20 USDT for B2B payments or remittance corridors can automate reconciliation, fee tracking, and counterparty verification across high-volume transfer data ## Related Resources From 8adc187b019a72cfeff71f2c0ce17a986b94a6c0 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 15:44:04 +0530 Subject: [PATCH 11/14] Add coinpath queries, Flow deprecation notices, and improve internal linking across docs - Add example GraphQL queries to 10 coinpath Schema pages (Ethereum, BSC, Cronos, Bitcoin, Dash, Dogecoin, Algorand, Celo, Cosmos, Tron) - Add deprecation notices to all 15 Flow Schema pages (chain no longer supported) - Fix self-referencing links in 9 coinpath Related Resources sections - Add Examples links to 7 Schema overview pages (Ethereum, BSC, Polygon, Cronos, Celo, Dash, Cardano) - Add Related Resources with Schema backlinks to 9 Example pages (Algorand, Avalanche, Bitcoin, Ripple) - Improve internal linking on 8 guide pages (graphql-ide, building-queries) - Fix Dogecoin coinpath intro text, standardize headings, normalize URL patterns Made-with: Cursor --- docs/Examples/Zcash/address-api.md | 8 +-- docs/Examples/algorand/smartContractCalls.mdx | 7 ++ docs/Examples/algorand/transactions.mdx | 7 ++ docs/Examples/algorand/transfers.mdx | 7 ++ docs/Examples/avalanche/avax-trades-api.mdx | 9 ++- .../bitcoin/Bitcoin-Input-and-Output API.mdx | 8 +++ docs/Examples/coinpath/money-flow-api.md | 11 +-- docs/Examples/ripple/balances.mdx | 7 ++ docs/Examples/ripple/payments.mdx | 7 ++ docs/Examples/ripple/trades.mdx | 7 ++ docs/Examples/ripple/transfers.mdx | 7 ++ docs/Schema/Avalanche/coinpath.md | 2 +- docs/Schema/Cronos/coinpath.md | 65 +++++++++++++++++ docs/Schema/Cronos/overview.md | 5 +- docs/Schema/Dash/coinpath.md | 39 ++++++++++- docs/Schema/Dash/overview.md | 3 +- docs/Schema/Dogecoin/coinpath.md | 41 ++++++++++- docs/Schema/Polygon/coinpath.md | 4 +- docs/Schema/Polygon/overview.md | 6 +- docs/Schema/algorand/coinpath.md | 40 +++++++++++ docs/Schema/binance_smart_chain/coinpath.md | 67 +++++++++++++++++- docs/Schema/binance_smart_chain/overview.md | 6 +- docs/Schema/bitcoin/coinpath.md | 42 ++++++++++- docs/Schema/cardano/overview.md | 3 +- docs/Schema/celo/coinpath.md | 65 +++++++++++++++++ docs/Schema/celo/overview.md | 5 +- docs/Schema/cosmos/coinpath.md | 40 +++++++++++ docs/Schema/ethereum/coinpath.md | 69 ++++++++++++++++++- docs/Schema/ethereum/overview.md | 6 +- docs/Schema/flow/address.md | 4 ++ docs/Schema/flow/arguments.md | 4 ++ docs/Schema/flow/blockSeals.md | 4 ++ docs/Schema/flow/blocks.md | 4 ++ docs/Schema/flow/coinpath.md | 4 ++ docs/Schema/flow/collections.md | 4 ++ docs/Schema/flow/eventFields.md | 4 ++ docs/Schema/flow/events.md | 4 ++ docs/Schema/flow/inputs.md | 4 ++ docs/Schema/flow/outputs.md | 4 ++ docs/Schema/flow/overview.md | 4 ++ docs/Schema/flow/transactionAuthorizers.md | 4 ++ .../flow/transactionEnvelopeSignatures.md | 4 ++ .../flow/transactionPayloadSignatures.md | 4 ++ docs/Schema/flow/transactions.md | 4 ++ docs/Schema/ripple/coinpath.md | 2 +- docs/Schema/tron/coinpath.md | 48 ++++++++++++- .../Fund Tracking/EVM_Chains.md | 3 +- .../Fund Tracking/Ledger_Based_Chains.md | 3 +- .../Fund Tracking/UTXO_Chains.md | 5 +- docs/building-queries/FAQ.md | 6 +- .../basic-structure-of-a-query.md | 5 +- docs/graphql-ide/apikey.md | 3 +- docs/graphql-ide/how-to-start.md | 4 +- docs/graphql-ide/ide.md | 3 +- docs/graphql-ide/query-builder.md | 5 +- .../graphql-ide/use-it-in-your-application.md | 3 +- docs/graphql-ide/v1-and-v2.md | 3 +- 57 files changed, 697 insertions(+), 49 deletions(-) diff --git a/docs/Examples/Zcash/address-api.md b/docs/Examples/Zcash/address-api.md index 446e603..d3d7936 100644 --- a/docs/Examples/Zcash/address-api.md +++ b/docs/Examples/Zcash/address-api.md @@ -289,8 +289,8 @@ You can query multiple addresses at once by using `{in: ["address1", "address2", ## Related Resources -- [UTXO Input/Output API Examples](https://docs.bitquery.io/v1/docs/examples/Transactions/input-output-api) -- [Transaction API Examples](https://docs.bitquery.io/v1/docs/examples/Transactions/transaction-api) -- [ZenZEC Token Trades API](https://docs.bitquery.io/v1/docs/examples/Zcash/zenzec-api) -- [Coinpath Money Flow API](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [UTXO Input/Output API Examples](https://docs.bitquery.io/v1/docs/Examples/Transactions/input-output-api) +- [Transaction API Examples](https://docs.bitquery.io/v1/docs/Examples/Transactions/transaction-api) +- [Coinpath Money Flow API](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/algorand/smartContractCalls.mdx b/docs/Examples/algorand/smartContractCalls.mdx index 4c9dd4b..2f70427 100644 --- a/docs/Examples/algorand/smartContractCalls.mdx +++ b/docs/Examples/algorand/smartContractCalls.mdx @@ -124,3 +124,10 @@ The query retrieves information about the latest 10 smart contract calls on the ## Video Tutorial | How to get Newly Created Tokens on Algorand + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Algorand Coinpath API examples](https://docs.bitquery.io/v1/docs/Examples/algorand/coinpath) +- [Smart Contract Calls API examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractCalls/smart-contract-calls-api) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/algorand/transactions.mdx b/docs/Examples/algorand/transactions.mdx index f9fb7fe..b0126a4 100644 --- a/docs/Examples/algorand/transactions.mdx +++ b/docs/Examples/algorand/transactions.mdx @@ -177,3 +177,10 @@ The query retrieves details of a specific transaction with the given transaction ## Video Tutorial | How to get Algorand Transactions Data using Bitquery API v1 + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Algorand Coinpath API examples](https://docs.bitquery.io/v1/docs/Examples/algorand/coinpath) +- [Transaction API examples](https://docs.bitquery.io/v1/docs/Examples/Transactions/transaction-api) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/algorand/transfers.mdx b/docs/Examples/algorand/transfers.mdx index e62a1cb..0abe5cd 100644 --- a/docs/Examples/algorand/transfers.mdx +++ b/docs/Examples/algorand/transfers.mdx @@ -100,3 +100,10 @@ query MyQuery { ## Video Tutorial | How to get Algorand Transfers Data using Bitquery API v1 + +## Related Resources + +- [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) +- [Algorand Coinpath API examples](https://docs.bitquery.io/v1/docs/Examples/algorand/coinpath) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/avalanche/avax-trades-api.mdx b/docs/Examples/avalanche/avax-trades-api.mdx index 7c4ea7c..9b48245 100644 --- a/docs/Examples/avalanche/avax-trades-api.mdx +++ b/docs/Examples/avalanche/avax-trades-api.mdx @@ -82,4 +82,11 @@ query MyQuery { } } } -``` \ No newline at end of file +``` + +## Related Resources + +- [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [OHLC candlestick examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/ohlc) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) \ No newline at end of file diff --git a/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx b/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx index cdc1d6c..14cea6a 100644 --- a/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx +++ b/docs/Examples/bitcoin/Bitcoin-Input-and-Output API.mdx @@ -247,3 +247,11 @@ query MyQuery { ## Video Tutorial to Get Daily Miner Rewards Info + +## Related Resources + +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [Bitcoin Coinpath API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin/Bitcoin-Coinpath-API) +- [Bitcoin Transaction API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin/Bitcoin-Transaction-API) +- [Input/Output API examples](https://docs.bitquery.io/v1/docs/Examples/Input_Output/IO_examples) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/coinpath/money-flow-api.md b/docs/Examples/coinpath/money-flow-api.md index 8b3af01..4d5d259 100644 --- a/docs/Examples/coinpath/money-flow-api.md +++ b/docs/Examples/coinpath/money-flow-api.md @@ -879,11 +879,12 @@ Discover direct and indirect funding relationships between a token creator and b You may also be interested in: -- [Cross-Chain API ➤](https://docs.bitquery.io/v1/docs/examples/cross-chain/cross-chain-api) -- [Solana DEX Trades API ➤](https://docs.bitquery.io/docs/blockchain/Solana/solana-dextrades/) -- [Blockchain Address API Examples ➤](https://docs.bitquery.io/docs/blockchain/Ethereum/balances/balance-api/) -- [Transaction API ➤](https://docs.bitquery.io/docs/blockchain/Ethereum/transactions/transaction-api/) -- [Transfers API ➤](https://docs.bitquery.io/docs/blockchain/Ethereum/transfers/erc20-token-transfer-api/) +- [Ethereum Coinpath Schema](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Bitcoin Coinpath Schema](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Solana Coinpath Schema](https://docs.bitquery.io/v1/docs/Schema/solana/coinpath) +- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) +- [Cross-Chain API examples](https://docs.bitquery.io/v1/docs/Examples/cross-chain/cross-chain-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) ## Need Help? diff --git a/docs/Examples/ripple/balances.mdx b/docs/Examples/ripple/balances.mdx index 9fb02da..beb3fa4 100644 --- a/docs/Examples/ripple/balances.mdx +++ b/docs/Examples/ripple/balances.mdx @@ -71,3 +71,10 @@ query ($network: RippleNetwork!, $address: String!, $from: ISO8601DateTime, $til ## Video Tutorial | How to get Balance of an Address on Ripple Blockchain + +## Related Resources + +- [Ripple schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple Payments examples](https://docs.bitquery.io/v1/docs/Examples/ripple/payments) +- [Ripple Transfers examples](https://docs.bitquery.io/v1/docs/Examples/ripple/transfers) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/ripple/payments.mdx b/docs/Examples/ripple/payments.mdx index 276f08d..439f70d 100644 --- a/docs/Examples/ripple/payments.mdx +++ b/docs/Examples/ripple/payments.mdx @@ -106,3 +106,10 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date ## Video Tutorial | How to get payments data on Ripple Blockchain + +## Related Resources + +- [Ripple schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple Balances examples](https://docs.bitquery.io/v1/docs/Examples/ripple/balances) +- [Ripple Transfers examples](https://docs.bitquery.io/v1/docs/Examples/ripple/transfers) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/ripple/trades.mdx b/docs/Examples/ripple/trades.mdx index d54f336..d680478 100644 --- a/docs/Examples/ripple/trades.mdx +++ b/docs/Examples/ripple/trades.mdx @@ -77,3 +77,10 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date ## Video Tutorial | How to get Trades of a currency on Ripple Blockchain + +## Related Resources + +- [Ripple schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple Balances examples](https://docs.bitquery.io/v1/docs/Examples/ripple/balances) +- [Ripple Transfers examples](https://docs.bitquery.io/v1/docs/Examples/ripple/transfers) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Examples/ripple/transfers.mdx b/docs/Examples/ripple/transfers.mdx index e7ec1eb..7bebe2f 100644 --- a/docs/Examples/ripple/transfers.mdx +++ b/docs/Examples/ripple/transfers.mdx @@ -176,3 +176,10 @@ query ($network: RippleNetwork!, $limit: Int!, $offset: Int!, $from: ISO8601Date ## Video Tutorial | How to get Transfers data on Ripple Blockchain + +## Related Resources + +- [Ripple schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) +- [Ripple Balances examples](https://docs.bitquery.io/v1/docs/Examples/ripple/balances) +- [Ripple Payments examples](https://docs.bitquery.io/v1/docs/Examples/ripple/payments) +- [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) diff --git a/docs/Schema/Avalanche/coinpath.md b/docs/Schema/Avalanche/coinpath.md index 5dfc858..ff27e8e 100644 --- a/docs/Schema/Avalanche/coinpath.md +++ b/docs/Schema/Avalanche/coinpath.md @@ -158,7 +158,7 @@ The following are available fields for the `coinpath`: - [Avalanche schema overview](https://docs.bitquery.io/v1/docs/Schema/Avalanche/overview) - [Avalanche API examples](https://docs.bitquery.io/v1/docs/Examples/avalanche/avax-trades-api) -- [Coinpath (Avalanche)](https://docs.bitquery.io/v1/docs/Schema/Avalanche/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Cronos/coinpath.md b/docs/Schema/Cronos/coinpath.md index 157a6c2..20bb561 100644 --- a/docs/Schema/Cronos/coinpath.md +++ b/docs/Schema/Cronos/coinpath.md @@ -42,6 +42,71 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound CRO fund flow from an address up to 2 hops deep, returning sender/receiver details, amounts, and block timestamps. Add `direction: inbound` inside `options` to trace incoming funds instead. + +```graphql +{ + ethereum(network: cronos) { + coinpath( + initialAddress: { is: "0x6f5e71A271579E3aF530067a2e7c7eaCe8fBe68a" } + currency: { is: "CRO" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + date: { since: "2023-01-01", till: "2023-06-30" } + ) { + sender { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + receiver { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + amount + currency { + symbol + name + } + transaction { + hash + value + } + block { + height + timestamp { + time(format: "%Y-%m-%d") + } + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing, two-address relationship analysis, and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Cronos schema overview](https://docs.bitquery.io/v1/docs/Schema/Cronos/overview) diff --git a/docs/Schema/Cronos/overview.md b/docs/Schema/Cronos/overview.md index e88b21d..42f1796 100644 --- a/docs/Schema/Cronos/overview.md +++ b/docs/Schema/Cronos/overview.md @@ -43,8 +43,9 @@ Cronos is an EVM-compatible chain from Crypto.com, using **CRO** for gas and set ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [DEX Trades examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) -- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/Dash/coinpath.md b/docs/Schema/Dash/coinpath.md index c280b22..c7a29a6 100644 --- a/docs/Schema/Dash/coinpath.md +++ b/docs/Schema/Dash/coinpath.md @@ -57,11 +57,48 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound DASH fund flow from an address, returning sender/receiver addresses, amounts, block height, and transaction hashes. Dash uses the UTXO model, so coinpath queries go through the `bitcoin` schema with `network: dash`. + +```graphql +{ + bitcoin(network: dash) { + coinpath( + initialAddress: { is: "XpESxaUmonkq8RaLLp46Brx2K39ggQe226" } + date: { after: "2023-01-01" } + options: { limit: 10, asc: "block.height", seed: 10 } + ) { + amount(in: USD) + block { + height + } + sender { + address + } + receiver { + address + } + transaction { + hash + } + currency { + name + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Dash schema overview](https://docs.bitquery.io/v1/docs/Schema/Dash/overview) - [Blockchain API examples](https://docs.bitquery.io/v1/docs/Examples/overview) -- [Coinpath (Dash)](https://docs.bitquery.io/v1/docs/Schema/Dash/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Dash/overview.md b/docs/Schema/Dash/overview.md index 635b47b..2b98c1a 100644 --- a/docs/Schema/Dash/overview.md +++ b/docs/Schema/Dash/overview.md @@ -42,7 +42,8 @@ Dash is a privacy-oriented UTXO network known for optional coin-mixing (PrivateS ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Cross-chain API examples](https://docs.bitquery.io/v1/docs/Examples/cross-chain/cross-chain-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) diff --git a/docs/Schema/Dogecoin/coinpath.md b/docs/Schema/Dogecoin/coinpath.md index b2febaf..3ff8010 100644 --- a/docs/Schema/Dogecoin/coinpath.md +++ b/docs/Schema/Dogecoin/coinpath.md @@ -22,7 +22,7 @@ description: "Track DOGE fund flows up to any depth on the Dogecoin blockchain u -The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology from Dash. +The `coinpath` field allows us to retrieve detailed information about money flow using coinpath technology from Dogecoin.
Filtering Options @@ -57,11 +57,48 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound DOGE fund flow from an address, returning sender/receiver addresses, amounts, block height, and transaction hashes. Dogecoin uses the UTXO model, so coinpath queries go through the `bitcoin` schema with `network: dogecoin`. + +```graphql +{ + bitcoin(network: dogecoin) { + coinpath( + initialAddress: { is: "DRSqEwcnJESVpUFD2bNmEXHqy2DKhiRVJb" } + date: { after: "2023-01-01" } + options: { limit: 10, asc: "block.height", seed: 10 } + ) { + amount(in: USD) + block { + height + } + sender { + address + } + receiver { + address + } + transaction { + hash + } + currency { + name + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Dogecoin schema overview](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/overview) - [Dogecoin API examples](https://docs.bitquery.io/v1/docs/Examples/Dogecoin) -- [Coinpath (Dogecoin)](https://docs.bitquery.io/v1/docs/Schema/Dogecoin/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Polygon/coinpath.md b/docs/Schema/Polygon/coinpath.md index 0632848..b235637 100644 --- a/docs/Schema/Polygon/coinpath.md +++ b/docs/Schema/Polygon/coinpath.md @@ -107,7 +107,7 @@ The `coinpath` API allows us to retrieve detailed information about flow of fund ``` -Check more examples of Coinpath APIs **[here](/docs/Examples/coinpath/money-flow-api.md)**. +Check more examples of Coinpath APIs **[here](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api)**.
Filtering Options @@ -155,7 +155,7 @@ Sign up on our **[GraphQL IDE](https://ide.bitquery.io/)** and get your Access T - [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) - [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) -- [Coinpath (Polygon)](https://docs.bitquery.io/v1/docs/Schema/Polygon/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/Polygon/overview.md b/docs/Schema/Polygon/overview.md index 36ddfb9..2a311be 100644 --- a/docs/Schema/Polygon/overview.md +++ b/docs/Schema/Polygon/overview.md @@ -55,8 +55,10 @@ Let's dive in and explore the Polygon API in following chapters. ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [DEX Trades examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Smart Contract Events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/algorand/coinpath.md b/docs/Schema/algorand/coinpath.md index 3795544..aac390d 100644 --- a/docs/Schema/algorand/coinpath.md +++ b/docs/Schema/algorand/coinpath.md @@ -42,6 +42,46 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces fund flow from a sender address on Algorand, returning amounts, block timestamps, receiver addresses, depth, and transaction hashes. + +```graphql +{ + algorand { + coinpath( + date: { after: "2023-08-05" } + options: { desc: "block.timestamp.iso8601", limit: 10 } + sender: { is: "BWSNMG43TUYEOHE76J6KDWIY6MU4U6JFJYGAYCZA2RF5IS3XPO3P3G4FEI" } + ) { + amount + block { + timestamp { + iso8601 + } + } + currency { + address + name + } + depth + receiver { + address + } + sender { + address + } + transaction { + hash + value + } + } + } +} +``` + +For more coinpath examples — including receiver-based tracing and transaction counts — see the [Algorand Coinpath API examples](/v1/docs/Examples/algorand/coinpath) and the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Algorand schema overview](https://docs.bitquery.io/v1/docs/Schema/algorand/overview) diff --git a/docs/Schema/binance_smart_chain/coinpath.md b/docs/Schema/binance_smart_chain/coinpath.md index 2a80f6e..e192ef0 100644 --- a/docs/Schema/binance_smart_chain/coinpath.md +++ b/docs/Schema/binance_smart_chain/coinpath.md @@ -58,11 +58,76 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound BNB fund flow from an address up to 2 hops deep, returning sender/receiver details, amounts, and block timestamps. Add `direction: inbound` inside `options` to trace incoming funds instead. + +```graphql +{ + ethereum(network: bsc) { + coinpath( + initialAddress: { is: "0x8894e0a0c962cb723c1ef8a1b3c07b89fcb4ea93" } + currency: { is: "BNB" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + date: { since: "2023-01-01", till: "2023-06-30" } + ) { + sender { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + receiver { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + amount + currency { + symbol + name + } + transaction { + hash + value + } + block { + height + timestamp { + time(format: "%Y-%m-%d") + } + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing, two-address relationship analysis, and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [BNB Smart Chain schema overview](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/overview) - [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) -- [Coinpath (BNB Smart Chain)](https://docs.bitquery.io/v1/docs/Schema/binance_smart_chain/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/binance_smart_chain/overview.md b/docs/Schema/binance_smart_chain/overview.md index 282d073..0f22794 100644 --- a/docs/Schema/binance_smart_chain/overview.md +++ b/docs/Schema/binance_smart_chain/overview.md @@ -44,8 +44,10 @@ BNB Smart Chain (BSC) is an EVM-compatible network where **BNB** pays gas and an ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [DEX Trades examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Smart Contract Events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) -- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/bitcoin/coinpath.md b/docs/Schema/bitcoin/coinpath.md index c5d23be..11a2c40 100644 --- a/docs/Schema/bitcoin/coinpath.md +++ b/docs/Schema/bitcoin/coinpath.md @@ -57,10 +57,48 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound BTC fund flow from a seed address, returning sender/receiver addresses, amounts in USD, block height, and transaction hashes. + +[Open this query on IDE](https://ide.bitquery.io/Destination-of-Funds-from-a-Specific-Address-on-Bitcoin) + +```graphql +{ + bitcoin(network: bitcoin) { + coinpath( + initialAddress: { is: "bc1p4kufll9uhnpkgzuc65slcxd2qaw2hl9xecket3h8yyu4awglcsqslqaztd" } + date: { after: "2023-10-10" } + options: { limit: 10, asc: "block.height", seed: 10 } + ) { + amount(in: USD) + block { + height + } + sender { + address + } + receiver { + address + } + transaction { + hash + } + currency { + name + address + } + } + } +} +``` + +For more coinpath examples — including inbound tracing and two-address relationship analysis — see the [Bitcoin Coinpath API examples](/v1/docs/Examples/bitcoin/Bitcoin-Coinpath-API) and the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) -- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) -- [Coinpath (Bitcoin)](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) +- [Bitcoin API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/cardano/overview.md b/docs/Schema/cardano/overview.md index 0a6d0fb..3a4cbf6 100644 --- a/docs/Schema/cardano/overview.md +++ b/docs/Schema/cardano/overview.md @@ -46,7 +46,8 @@ Cardano uses an **eUTXO** model: **ADA** and **native tokens** live in transacti ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Cross-chain API examples](https://docs.bitquery.io/v1/docs/Examples/cross-chain/cross-chain-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Solana schema overview](https://docs.bitquery.io/v1/docs/Schema/solana/overview) diff --git a/docs/Schema/celo/coinpath.md b/docs/Schema/celo/coinpath.md index fbea8d0..038715d 100644 --- a/docs/Schema/celo/coinpath.md +++ b/docs/Schema/celo/coinpath.md @@ -42,6 +42,71 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound CELO fund flow from an address up to 2 hops deep, returning sender/receiver details, amounts, and block timestamps. Add `direction: inbound` inside `options` to trace incoming funds instead. + +```graphql +{ + ethereum(network: celo_mainnet) { + coinpath( + initialAddress: { is: "0xe11BFCBDd43745D4Aa6f4f18E24aD24f4623af04" } + currency: { is: "CELO" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + date: { since: "2023-01-01", till: "2023-06-30" } + ) { + sender { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + receiver { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + amount + currency { + symbol + name + } + transaction { + hash + value + } + block { + height + timestamp { + time(format: "%Y-%m-%d") + } + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing, two-address relationship analysis, and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Celo schema overview](https://docs.bitquery.io/v1/docs/Schema/celo/overview) diff --git a/docs/Schema/celo/overview.md b/docs/Schema/celo/overview.md index 09d4152..e235b56 100644 --- a/docs/Schema/celo/overview.md +++ b/docs/Schema/celo/overview.md @@ -45,8 +45,9 @@ Celo is a mobile-first EVM-compatible network with native stable-value assets su ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [DEX Trades examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) -- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/cosmos/coinpath.md b/docs/Schema/cosmos/coinpath.md index d21695d..defc512 100644 --- a/docs/Schema/cosmos/coinpath.md +++ b/docs/Schema/cosmos/coinpath.md @@ -38,6 +38,46 @@ On Cosmos SDK chains, value moves through **messages** (bank sends, IBC transfer - `sender`: returns sender address - `transaction`: returns message of transfer happened +## Example Query + +The following query traces outbound fund flow from a Cosmos address, returning amounts in USD, block height and timestamps, sender/receiver addresses, and transaction hashes. + +```graphql +{ + cosmos { + coinpath( + initialAddress: { is: "cosmos1ypejmkpfqrqmv5w7cscq874xf8rlggq7w44rsw" } + date: { after: "2023-08-07" } + options: { desc: "block.timestamp.iso8601", limit: 10 } + ) { + amount(in: USD) + block { + height + timestamp { + iso8601 + } + } + currency { + address + name + } + receiver { + address + } + sender { + address + } + transaction { + hash + value + } + } + } +} +``` + +For more coinpath examples — including two-address flow analysis and minimum-amount filtering — see the [Cosmos Coinpath API examples](/v1/docs/Examples/cosmos/coinpath) and the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Cosmos schema overview](https://docs.bitquery.io/v1/docs/Schema/cosmos/overview) diff --git a/docs/Schema/ethereum/coinpath.md b/docs/Schema/ethereum/coinpath.md index 558f210..e0c8b95 100644 --- a/docs/Schema/ethereum/coinpath.md +++ b/docs/Schema/ethereum/coinpath.md @@ -65,10 +65,77 @@ The following are available fields for the `coinpath`: - `transaction`: returns transaction details. - `transactions`: returns attributes of transactions. +## Example Query + +The following query traces outbound fund flow from an address up to 2 hops deep, returning sender/receiver details, amounts, block timestamps, and transaction hashes. You can switch to inbound tracing by adding `direction: inbound` inside `options`. + +[Open this query on IDE](https://ide.bitquery.io/destination-of-funds-for-upbit-hackers) + +```graphql +{ + ethereum(network: ethereum) { + coinpath( + initialAddress: { is: "0xa09871aeadf4994ca12f5c0b6056bbd1d343c029" } + currency: { is: "ETH" } + depth: { lteq: 2 } + options: { + seed: 110 + asc: "depth" + desc: "amount" + limitBy: { each: "depth", limit: 10 } + } + date: { since: "2018-03-01", till: "2021-01-31" } + ) { + sender { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + receiver { + address + annotation + smartContract { + contractType + currency { + symbol + name + } + } + } + amount + currency { + symbol + name + } + transaction { + hash + value + } + block { + height + timestamp { + time(format: "%y-%d-%m") + } + } + depth + count + } + } +} +``` + +For more coinpath examples — including inbound tracing, two-address relationship analysis, and multi-hop fund tracking — see the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) - [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) -- [Coinpath (Ethereum)](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/ethereum/overview.md b/docs/Schema/ethereum/overview.md index 81ba9eb..fd5c377 100644 --- a/docs/Schema/ethereum/overview.md +++ b/docs/Schema/ethereum/overview.md @@ -50,8 +50,10 @@ Let's dive in and explore the Ethereum data available through Bitquery API. ## Related Resources -- [Bitquery documentation intro](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum DEX Trades examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Ethereum Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) +- [Smart Contract Events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) - [Polygon schema overview](https://docs.bitquery.io/v1/docs/Schema/Polygon/overview) -- [Coinpath explained](https://docs.bitquery.io/v1/docs/building-queries/Coinpath-Explained/Overview) diff --git a/docs/Schema/flow/address.md b/docs/Schema/flow/address.md index 3200e3f..5b24317 100644 --- a/docs/Schema/flow/address.md +++ b/docs/Schema/flow/address.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Address", "Bitquery", "GraphQL"] # Address +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Address API offers basic information about addresses from the Flow Blockchain. Flow addresses identify accounts that can hold FLOW tokens, NFT collections, and Cadence resources. The address API returns balance, annotation, and account-level metadata. Use it for wallet lookups, collection dashboards, and verifying account identity before drilling into events or transfer history. diff --git a/docs/Schema/flow/arguments.md b/docs/Schema/flow/arguments.md index 39d270d..14e9bdc 100644 --- a/docs/Schema/flow/arguments.md +++ b/docs/Schema/flow/arguments.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Arguments", "Bitquery", "GraphQL"] # Arguments +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Arguments API provides information about transaction arguments from the flow blockchain which contains the payload and envelope signatures
diff --git a/docs/Schema/flow/blockSeals.md b/docs/Schema/flow/blockSeals.md index 6738b43..7b58f16 100644 --- a/docs/Schema/flow/blockSeals.md +++ b/docs/Schema/flow/blockSeals.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Block Seals", "Bitquery", "GraphQL"] # Block Seals +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Block Seals API provides you information about blocks seal from the Flow Blockchain. A block seal is an attestation that execution result of a specific block has been verified and approved by a quorum of verification nodes.
diff --git a/docs/Schema/flow/blocks.md b/docs/Schema/flow/blocks.md index 792f9bc..6ab7615 100644 --- a/docs/Schema/flow/blocks.md +++ b/docs/Schema/flow/blocks.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Blocks", "Bitquery", "GraphQL"] # Blocks +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Blocks API provides detailed information about blocks created on the Flow Blockchain.
diff --git a/docs/Schema/flow/coinpath.md b/docs/Schema/flow/coinpath.md index bb183cf..9bcb4f6 100644 --- a/docs/Schema/flow/coinpath.md +++ b/docs/Schema/flow/coinpath.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Coinpath", "Bitquery", "GraphQL"] # Coinpath +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Tezos Coinpath API provides information about money flow from the Flow Blockchain.
diff --git a/docs/Schema/flow/collections.md b/docs/Schema/flow/collections.md index 95e434e..bd586cc 100644 --- a/docs/Schema/flow/collections.md +++ b/docs/Schema/flow/collections.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Collections", "Bitquery", "GraphQL"] # Collections +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Collections API provides information about collections from the Flow Blockchain. A collection is batch of transactions that have been includes in a block.
diff --git a/docs/Schema/flow/eventFields.md b/docs/Schema/flow/eventFields.md index c6faa0d..83cf8b3 100644 --- a/docs/Schema/flow/eventFields.md +++ b/docs/Schema/flow/eventFields.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Event Fields", "Bitquery", "GraphQL"] # Event Fields +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Event Fields API provides information about events from the Flow Blockchain.
diff --git a/docs/Schema/flow/events.md b/docs/Schema/flow/events.md index b6e8d31..b43eca5 100644 --- a/docs/Schema/flow/events.md +++ b/docs/Schema/flow/events.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Events", "Bitquery", "GraphQL"] # Events +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Events API provides information about events emiited on the Flow Blockchain.
diff --git a/docs/Schema/flow/inputs.md b/docs/Schema/flow/inputs.md index 708c399..b425341 100644 --- a/docs/Schema/flow/inputs.md +++ b/docs/Schema/flow/inputs.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Inputs", "Bitquery", "GraphQL"] # Inputs +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Inputs API provides information about transaction inputs from the Flow Blockchain.
diff --git a/docs/Schema/flow/outputs.md b/docs/Schema/flow/outputs.md index 46c8f16..6da067f 100644 --- a/docs/Schema/flow/outputs.md +++ b/docs/Schema/flow/outputs.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Outputs", "Bitquery", "GraphQL"] # Outputs +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Outputs API provides information about the transaction outputs from the Flow Blockchain.
diff --git a/docs/Schema/flow/overview.md b/docs/Schema/flow/overview.md index 822aaa0..7299ff4 100644 --- a/docs/Schema/flow/overview.md +++ b/docs/Schema/flow/overview.md @@ -7,6 +7,10 @@ keywords: [Flow API, Flow GraphQL, Flow blockchain data, Bitquery] # Overview +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + Flow is a layer 1 blockchain for creating and trading non-fungible tokens (NFTs), decentralized applications (dApps), and games. ![flow explorer](/img/flow.png) diff --git a/docs/Schema/flow/transactionAuthorizers.md b/docs/Schema/flow/transactionAuthorizers.md index 9c35f27..a177099 100644 --- a/docs/Schema/flow/transactionAuthorizers.md +++ b/docs/Schema/flow/transactionAuthorizers.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Transaction Authorizers", "Bitquery", "GraphQL"] # Transaction Authorizers +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Transaction Authorizers API provides information about transaction authorizers from the Flow Blcockhain.
diff --git a/docs/Schema/flow/transactionEnvelopeSignatures.md b/docs/Schema/flow/transactionEnvelopeSignatures.md index 4ba1b6c..89a3afb 100644 --- a/docs/Schema/flow/transactionEnvelopeSignatures.md +++ b/docs/Schema/flow/transactionEnvelopeSignatures.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Transaction Envelope Signatures", "Bitquery", "Grap # Transaction Envelope Signatures +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Transaction Envelope Signatures API provides details about envelope signatures of transaction from the Flow Blockchain.
diff --git a/docs/Schema/flow/transactionPayloadSignatures.md b/docs/Schema/flow/transactionPayloadSignatures.md index c067102..eadce0f 100644 --- a/docs/Schema/flow/transactionPayloadSignatures.md +++ b/docs/Schema/flow/transactionPayloadSignatures.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Transaction Payload Signatures", "Bitquery", "Graph # Transaction Payload Signatures +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Transaction Payload Signatures API provides information about payload signatures of transaction from the Flow Blockchain.
diff --git a/docs/Schema/flow/transactions.md b/docs/Schema/flow/transactions.md index 0badf7b..e75cea9 100644 --- a/docs/Schema/flow/transactions.md +++ b/docs/Schema/flow/transactions.md @@ -6,6 +6,10 @@ keywords: ["Flow API", "Flow Transactions", "Bitquery", "GraphQL"] # Transactions +:::caution Deprecated +Bitquery has stopped supporting the Flow blockchain. Historical data may still be available, but it is no longer updated. The schema reference below is preserved for archival purposes. +::: + The Flow Transaction API provides information about transactions from the Flow Blockchain.
diff --git a/docs/Schema/ripple/coinpath.md b/docs/Schema/ripple/coinpath.md index d11d6ac..b7dc86d 100644 --- a/docs/Schema/ripple/coinpath.md +++ b/docs/Schema/ripple/coinpath.md @@ -178,7 +178,7 @@ query ($network: RippleNetwork!, $address: String!, $inboundDepth: Int!, $outbou - [XRP Ledger schema overview](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) - [Ripple API examples](https://docs.bitquery.io/v1/docs/Examples/ripple) -- [Coinpath (XRP Ledger)](https://docs.bitquery.io/v1/docs/Schema/ripple/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/Schema/tron/coinpath.md b/docs/Schema/tron/coinpath.md index efcc51a..abd8f16 100644 --- a/docs/Schema/tron/coinpath.md +++ b/docs/Schema/tron/coinpath.md @@ -55,11 +55,57 @@ Coinpath data can be filtered using following arguments: - `sender`: returns sender address - `transaction`: returns transaction of transfer happened +## Example Query + +The following query traces USDT fund flow from an initial address on Tron, returning amounts, block timestamps, sender/receiver balances, depth, and transaction hashes. + +```graphql +{ + tron { + coinpath( + currency: { is: "TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t" } + initialAddress: { is: "TTd9qHyjqiUkfTxe3gotbuTMpjU8LEbpkN" } + initialDate: { after: "2023-07-31" } + options: { desc: "block.timestamp.iso8601", limit: 5 } + ) { + amount + block { + timestamp { + iso8601 + } + } + currency { + address + name + } + depth + receiver { + address + balance + amountOut + amountIn + } + sender { + address + amountIn + amountOut + balance + } + transaction { + hash + } + } + } +} +``` + +For more coinpath examples — including receiver-based tracing — see the [Tron Coinpath API examples](/v1/docs/Examples/tron/coinpath) and the [Coinpath Money Flow API examples](/v1/docs/Examples/coinpath/money-flow-api). + ## Related Resources - [Tron schema overview](https://docs.bitquery.io/v1/docs/Schema/tron/overview) - [Tron API examples](https://docs.bitquery.io/v1/docs/Examples/tron) -- [Coinpath (Tron)](https://docs.bitquery.io/v1/docs/Schema/tron/coinpath) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Documentation intro](https://docs.bitquery.io/v1/docs/intro) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md index fa06d68..0ce1d57 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/EVM_Chains.md @@ -88,4 +88,5 @@ Track where funds went from an address over 2 hops on Ethereum: - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [UTXO Fund Tracking](./UTXO_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) - [Ethereum Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/ethereum/coinpath) -- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Smart Contract Events examples](https://docs.bitquery.io/v1/docs/Examples/smartcontractEvents/smart-contract-events-api) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md index 2e740da..9983b3b 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/Ledger_Based_Chains.md @@ -52,4 +52,5 @@ To address these challenges, the Coinpath graph for ledger-based chains differs - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [EVM Fund Tracking](./EVM_Chains) | [UTXO Fund Tracking](./UTXO_Chains) - [Ripple schema reference](https://docs.bitquery.io/v1/docs/Schema/ripple/overview) -- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Ripple Transfers examples](https://docs.bitquery.io/v1/docs/Examples/ripple/transfers) diff --git a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md index 122b54b..9bc229b 100644 --- a/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md +++ b/docs/building-queries/Coinpath-Explained/Fund Tracking/UTXO_Chains.md @@ -93,5 +93,6 @@ Track where BTC moved from an address over 2 hops: - [How to Read a Coinpath Graph](../How_to_read_coinpath_graph) — nodes, edges, depth levels. - [EVM Fund Tracking](./EVM_Chains) | [Ledger-Based Fund Tracking](./Ledger_Based_Chains) - [Bitcoin Coinpath schema reference](https://docs.bitquery.io/v1/docs/Schema/bitcoin/coinpath) -- [Bitcoin Coinpath API examples](https://docs.bitquery.io/v1/docs/examples/bitcoin/Bitcoin-Coinpath-API) -- [Coinpath Money Flow API — query cookbook](https://docs.bitquery.io/v1/docs/examples/coinpath/money-flow-api) +- [Bitcoin Coinpath API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin/Bitcoin-Coinpath-API) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) +- [Bitcoin Input/Output API examples](https://docs.bitquery.io/v1/docs/Examples/bitcoin/Bitcoin-Input-and-Output%20API) diff --git a/docs/building-queries/FAQ.md b/docs/building-queries/FAQ.md index df0e536..7b40dd5 100644 --- a/docs/building-queries/FAQ.md +++ b/docs/building-queries/FAQ.md @@ -189,8 +189,10 @@ Note: In many cases token attributes shown as null in those cases you should fin ## Related Resources -- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [Bitcoin schema overview](https://docs.bitquery.io/v1/docs/Schema/bitcoin/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) - [Basic structure of a query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) - [Expressions overview](https://docs.bitquery.io/v1/docs/query-features/expressions/overview) - [Metrics in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/Metrics) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) diff --git a/docs/building-queries/basic-structure-of-a-query.md b/docs/building-queries/basic-structure-of-a-query.md index acc264e..a7b131b 100644 --- a/docs/building-queries/basic-structure-of-a-query.md +++ b/docs/building-queries/basic-structure-of-a-query.md @@ -67,8 +67,9 @@ Datasets are types of data such as Ethereum and Binance smart chain, both are Et ## Related Resources -- [Introduction](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) - [Network selection](https://docs.bitquery.io/v1/docs/building-queries/network-selection) -- [Bitquery API FAQ](https://docs.bitquery.io/v1/docs/building-queries/FAQ) - [Aggregation in Bitquery GraphQL API](https://docs.bitquery.io/v1/docs/query-features/aggregation/aggregation) - [Filtering fields](https://docs.bitquery.io/v1/docs/query-features/filtering/fields) \ No newline at end of file diff --git a/docs/graphql-ide/apikey.md b/docs/graphql-ide/apikey.md index 21f21d2..1017c73 100644 --- a/docs/graphql-ide/apikey.md +++ b/docs/graphql-ide/apikey.md @@ -124,8 +124,9 @@ Your Access Token is your identity in the system, you have to be very careful to ## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) - [Use Bitquery in your application](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) - [How to use the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) - [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [V1 vs V2 APIs](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) -- [Account dashboard](https://docs.bitquery.io/v1/docs/graphql-ide/account) diff --git a/docs/graphql-ide/how-to-start.md b/docs/graphql-ide/how-to-start.md index f3559dd..8d2545f 100644 --- a/docs/graphql-ide/how-to-start.md +++ b/docs/graphql-ide/how-to-start.md @@ -114,8 +114,10 @@ Check our [Youtube Channel](https://www.youtube.com/@bitquery) for video tutoria ## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Coinpath Money Flow API examples](https://docs.bitquery.io/v1/docs/Examples/coinpath/money-flow-api) - [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) - [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) -- [Use Bitquery in your application](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) - [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) - [V1 vs V2 APIs](https://docs.bitquery.io/v1/docs/graphql-ide/v1-and-v2) diff --git a/docs/graphql-ide/ide.md b/docs/graphql-ide/ide.md index ac2e323..bce388b 100644 --- a/docs/graphql-ide/ide.md +++ b/docs/graphql-ide/ide.md @@ -70,8 +70,9 @@ If the IDE isn't your preferred route, you can still directly access our API fro ## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [GraphQL query builder guide](https://docs.bitquery.io/v1/docs/graphql-ide/query-builder) - [API access token setup](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) -- [Account dashboard overview](https://docs.bitquery.io/v1/docs/graphql-ide/account) - [Use Bitquery APIs in your app](https://docs.bitquery.io/v1/docs/graphql-ide/use-it-in-your-application) diff --git a/docs/graphql-ide/query-builder.md b/docs/graphql-ide/query-builder.md index 255c4d7..b079901 100644 --- a/docs/graphql-ide/query-builder.md +++ b/docs/graphql-ide/query-builder.md @@ -40,8 +40,9 @@ Simplify your query creation process and access the data you need from various b ## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [DEX Trades API examples](https://docs.bitquery.io/v1/docs/Examples/dexTrades/dex-trading-data-api) +- [Transfer API examples](https://docs.bitquery.io/v1/docs/Examples/Transfers/transfer-api) - [How to use the Bitquery GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) - [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Supported blockchains](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) - [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) -- [Bitcoin examples](https://docs.bitquery.io/v1/docs/examples/Bitcoin) diff --git a/docs/graphql-ide/use-it-in-your-application.md b/docs/graphql-ide/use-it-in-your-application.md index 6fb0242..1386a6a 100644 --- a/docs/graphql-ide/use-it-in-your-application.md +++ b/docs/graphql-ide/use-it-in-your-application.md @@ -37,8 +37,9 @@ Authentication is usually a bearer-style token you obtain from the account or AP ## Related Resources +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) - [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) - [How to use the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/ide) - [Getting started with the IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) -- [Common API errors](https://docs.bitquery.io/v1/docs/graphql-ide/errors) - [Basic structure of a GraphQL query](https://docs.bitquery.io/v1/docs/building-queries/basic-structure-of-a-query) diff --git a/docs/graphql-ide/v1-and-v2.md b/docs/graphql-ide/v1-and-v2.md index 8c4fcca..fce7d20 100644 --- a/docs/graphql-ide/v1-and-v2.md +++ b/docs/graphql-ide/v1-and-v2.md @@ -92,7 +92,8 @@ If you have questions about our APIs, please check out [Telegram](https://t.me/b ## Related Resources -- [Bitquery V1 documentation overview](https://docs.bitquery.io/v1/docs/intro) +- [Ethereum schema overview](https://docs.bitquery.io/v1/docs/Schema/ethereum/overview) +- [API examples overview](https://docs.bitquery.io/v1/docs/Examples/overview) - [Getting started with the GraphQL IDE](https://docs.bitquery.io/v1/docs/graphql-ide/how-to-start) - [Supported blockchains (V1)](https://docs.bitquery.io/v1/docs/graphql-ide/supported-blockchains) - [Getting an API access token](https://docs.bitquery.io/v1/docs/graphql-ide/apikey) From 3120e8c9c5bf0a94b03b54547ecea6916c80d203 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 15:53:44 +0530 Subject: [PATCH 12/14] Enable showLastUpdateTime for docs pages Adds git-based "Last updated" timestamps to all doc pages, improving content freshness signals for SEO and user trust. Made-with: Cursor --- docusaurus.config.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docusaurus.config.js b/docusaurus.config.js index 10ea52d..75c7b8e 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -112,10 +112,12 @@ const config = { docs: { sidebarPath: require.resolve("./sidebars.js"), editUrl: "https://github.com/bitquery/graphql-docs/tree/main", + showLastUpdateTime: true, }, blog: { showReadingTime: true, editUrl: "https://github.com/bitquery/graphql-docs/tree/main", + showLastUpdateTime: true, }, theme: { customCss: require.resolve("./src/css/custom.css"), From 11cc390fee915c7240fcd51b196edfb7d45d2371 Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 15:59:21 +0530 Subject: [PATCH 13/14] Remove showLastUpdateTime from blog (unsupported in Docusaurus 2.x) Made-with: Cursor --- docusaurus.config.js | 1 - 1 file changed, 1 deletion(-) diff --git a/docusaurus.config.js b/docusaurus.config.js index 75c7b8e..439320c 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -117,7 +117,6 @@ const config = { blog: { showReadingTime: true, editUrl: "https://github.com/bitquery/graphql-docs/tree/main", - showLastUpdateTime: true, }, theme: { customCss: require.resolve("./src/css/custom.css"), From 21e7c45fdfaadb457bbc6631cd197b5d45619f5f Mon Sep 17 00:00:00 2001 From: Gaurav agarwal Date: Thu, 2 Apr 2026 16:31:09 +0530 Subject: [PATCH 14/14] Remove createRedirects from client-redirects plugin config Made-with: Cursor --- docusaurus.config.js | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docusaurus.config.js b/docusaurus.config.js index 439320c..9540e6c 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -92,15 +92,6 @@ const config = { from: "/docs/category/Bitcoin", }, ], - // On case-sensitive hosts, also redirect /docs/Examples/bitcoin → /docs/examples/Bitcoin. - // Can't be a static redirect here (macOS build is case-insensitive); handle in nginx if needed. - createRedirects(existingPath) { - // Bitcoin hub: slug /examples/Bitcoin differs from file path Examples/bitcoin - if (existingPath === "/docs/examples/Bitcoin") { - return ["/docs/Examples/bitcoin/index"]; - } - return undefined; - }, }, ], ],