Endpoints

Endpoint categories

The Alphractal API is organised into logical categories, each representing a specific data domain:

  • Mining – network security, difficulty, hash rate, and miner revenue metrics

  • Market – price, returns, volatility, valuation, and growth indicators

  • Derivatives – funding rates, open interest, long/short ratios, and positioning data

  • Exchange Flow – reserves and asset movements across exchanges

  • Addresses & Supply – holder distribution and address balance cohorts

  • Lifespan / Behavioural – SOPR, realised price, and lifecycle-based metrics

  • Macro & Liquidity – macroeconomic and liquidity indicators relevant to crypto markets

Each category contains multiple endpoints returning time-series data.

Endpoint structure

Most endpoints follow one of these patterns:

  • Asset-scoped metric

    /{asset}/{category}/{metric}
    

    Returns a time-series for a single metric and asset.

  • Query / bulk endpoint

    /{category}
    /api/Query{Category}
    

    Returns a paginated collection of records with optional filtering and field selection.

How to read an endpoint definition

For each endpoint in this documentation, you will find:

  • Description – what the endpoint represents and why it exists

  • Parameters – required and optional inputs (path, query)

  • Response – data structure and fields returned

  • Use cases – common analytical or product scenarios

If a parameter or field is not explicitly documented, it should be treated as unsupported.

Time and ordering

  • All timestamps are returned in UTC using ISO-8601 format.

  • Time-series data is returned in ascending chronological order unless stated otherwise.

Stability and changes

  • Endpoints are considered stable once published.

  • Additive changes (new fields or endpoints) may occur without breaking existing clients.

  • Breaking changes will be versioned and documented in advance.

Final note

The Alphractal API is designed for data correctness, consistency, and analytical depth.
If you are building latency-sensitive or high-frequency systems, plan your architecture accordingly.