XRP Flow Indicator

This namespace contains endpoints to retrieve metrics related to XRP Flow Indicators.

Exchange Inflow Value Distribution

get

Exchange Inflow Value Distribution is a metric that shows the amount distribution of xrp tokens flowed into exchange wallets according to its value.

Authorizations

Access Token

AuthorizationstringRequired

For each API request, include this HTTP header: Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required. You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.

Query parameters

exchangestringRequired

An exchange from the table that we support. See here.

Example: binance

windowstringOptional

Currently we support day, hour, and block.

Default: dayExample: day

fromanyOptional

This defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.

Example: 20191001T100000

toanyOptional

This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.

Example: 20191001T103025

limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100

formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json

Responses

200

exchange inflow's distribution band by the amount of the trasferred tokens(xrp) at once

application/json

get

/xrp/flow-indicator/exchange-inflow-value-distribution

ShellJavaScriptNodeJSRubyPython

curl "https://api.cryptoquant.com/v1/xrp/flow-indicator/exchange-inflow-value-distribution?exchange=binance&window=day&from=20191001&limit=2"

200

exchange inflow's distribution band by the amount of the trasferred tokens(xrp) at once

{
  "status": {
    "code": 200,
    "message": "success"
  },
  "result": {
    "window": "day",
    "data": [
      {
        "date": "2020-07-29",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      },
      {
        "date": "2020-07-28",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      }
    ]
  }
}

Exchange Outflow Value Distribution

get

Exchange Outflow Value Distribution is a metric that shows the amount distribution of xrp tokens flowed out from exchange wallets according to its value.

Authorizations

Access Token

AuthorizationstringRequired

For each API request, include this HTTP header: Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required. You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.

Query parameters

exchangestringRequired

An exchange from the table that we support. See here.

Example: binance

windowstringOptional

Currently we support day, hour, and block.

Default: dayExample: day

fromanyOptional

This defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.

Example: 20191001T100000

toanyOptional

This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.

Example: 20191001T103025

limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100

formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json

Responses

200

exchange outflow's distribution band by the amount of the trasferred tokens(xrp) at once

application/json

get

/xrp/flow-indicator/exchange-outflow-value-distribution

ShellJavaScriptNodeJSRubyPython

curl "https://api.cryptoquant.com/v1/xrp/flow-indicator/exchange-outflow-value-distribution?exchange=binance&window=day&from=20191001&limit=2"

200

exchange outflow's distribution band by the amount of the trasferred tokens(xrp) at once

{
  "status": {
    "code": 200,
    "message": "success"
  },
  "result": {
    "window": "day",
    "data": [
      {
        "date": "2020-07-29",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      },
      {
        "date": "2020-07-28",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      }
    ]
  }
}

Exchange Inflow Count Value Distribution

get

Exchange Inflow Count Value Distribution is a metric that shows the number of transactions of xrp tokens flowed into exchange wallets according to its value segment.

Authorizations

Access Token

AuthorizationstringRequired

For each API request, include this HTTP header: Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required. You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.

Query parameters

exchangestringRequired

An exchange from the table that we support. See here.

Example: binance

windowstringOptional

Currently we support day, hour, and block.

Default: dayExample: day

fromanyOptional

This defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.

Example: 20191001T100000

toanyOptional

This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.

Example: 20191001T103025

limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100

formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json

Responses

200

number of transactions of each exchange inflow's distribution band by the amount of the trasferred tokens(xrp) at once

application/json

get

/xrp/flow-indicator/exchange-inflow-count-value-distribution

ShellJavaScriptNodeJSRubyPython

curl "https://api.cryptoquant.com/v1/xrp/flow-indicator/exchange-inflow-count-value-distribution?exchange=binance&window=day&from=20191001&limit=2"

200

number of transactions of each exchange inflow's distribution band by the amount of the trasferred tokens(xrp) at once

{
  "status": {
    "code": 200,
    "message": "success"
  },
  "result": {
    "window": "day",
    "data": [
      {
        "date": "2020-07-29",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      },
      {
        "date": "2020-07-28",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      }
    ]
  }
}

Exchange Outflow Count Value Distribution

get

Exchange Outflow Count Value Distribution is a metric that shows the number of transactions of xrp tokens flowed into exchange wallets according to its value segment.

Authorizations

Access Token

AuthorizationstringRequired

For each API request, include this HTTP header: Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required. You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.

Query parameters

exchangestringRequired

An exchange from the table that we support. See here.

Example: binance

windowstringOptional

Currently we support day, hour, and block.

Default: dayExample: day

fromanyOptional

This defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.

Example: 20191001T100000

toanyOptional

This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.

Example: 20191001T103025

limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100

formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json

Responses

200

number of transactions of each exchange outflow's distribution band by the amount of the trasferred tokens(xrp) at once

application/json

get

/xrp/flow-indicator/exchange-outflow-count-value-distribution

ShellJavaScriptNodeJSRubyPython

curl "https://api.cryptoquant.com/v1/xrp/flow-indicator/exchange-outflow-count-value-distribution?exchange=binance&window=day&from=20191001&limit=2"

200

number of transactions of each exchange outflow's distribution band by the amount of the trasferred tokens(xrp) at once

{
  "status": {
    "code": 200,
    "message": "success"
  },
  "result": {
    "window": "day",
    "data": [
      {
        "date": "2020-07-29",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      },
      {
        "date": "2020-07-28",
        "range_1000_below": null,
        "range_1001_to_10000": null,
        "range_10001_to_100000": null,
        "range_100001_to_1000000": null,
        "range_1000000_over": null
      }
    ]
  }
}

Exchange Supply Ratio

get

The ratio of exchange's xrp reserve compared to total supply of xrp.

Authorizations

Access Token

AuthorizationstringRequired

For each API request, include this HTTP header: Authorization with the Bearer {access_token}. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required. You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please upgrade your plan to Professional or Premium plan. You'll be able to see your access token on the API tab of your profile page after the subscription.

Query parameters

exchangestringRequired

An exchange from the table that we support. See here.

Example: binance

windowstringOptional

Currently, we support day and hour.

Default: dayExample: day

fromanyOptional

This defines the starting time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the earliest time.

Example: 20191001T100000

toanyOptional

This defines the ending time for which data will be gathered, formatted as YYYYMMDDTHHMMSS (indicating YYYY-MM-DDTHH:MM:SS, UTC time). If window=day is used, it can also be formatted as YYYYMMDD (date). If window=block is used, you can also specify the exact block height (e.g. 510000). If this field is not specified, response will include data from the latest time.

Example: 20191001T103025

limitinteger · min: 1 · max: 100000Optional

The maximum number of entries to return before the latest data point (or before to if specified). This field ranges from 1 to 100,000.

Default: 100Example: 100

formatstringOptional

A format type about return message type. Supported formats are json, csv.

Default: jsonExample: json

Responses

200

exchange supply ratio

application/json

get

/xrp/flow-indicator/exchange-supply-ratio

ShellJavaScriptNodeJSRubyPython

curl "https://api.cryptoquant.com/v1/xrp/flow-indicator/exchange-supply-ratio?exchange=binance&window=day&from=20191001&limit=2"

200

exchange supply ratio

{
  "status": {
    "code": 200,
    "message": "success"
  },
  "result": {
    "window": "day",
    "data": [
      {
        "date": "2019-10-02",
        "exchange_supply_ratio": null
      },
      {
        "date": "2019-10-01",
        "exchange_supply_ratio": null
      }
    ]
  }
}