Skip to content

BUILD ON THE RECORD

Developer API.

Bitcoin BLAKE2b observations and sourced pool terms for your tools, research and community dashboards. Free, read-only access. No account or API key required.

Versioned JSON

Four endpoints with source, chain identity and generation time.

Visible coverage

Recorded observations, sample counts and explicit missing values.

Data you can share

CSV exports and links to specific historical periods.

Make your first request

Base URL: https://blakestack.com/api/v1. Browser requests support CORS without credentials.

curl https://blakestack.com/api/v1/network

curl 'https://blakestack.com/api/v1/history?interval=1h'

curl 'https://blakestack.com/api/v1/blocks?limit=50'

Every JSON response has meta and data. Metadata identifies Bitcoin BLAKE2b mainnet by its fork height and hash. Failed requests return {"error":{"code":"…","message":"…"}}.

Endpoints

GET /api/v1/network

Latest node observation: tip, difficulty, estimated hashrate, average block interval and node-visible mempool.

No parameters. Check meta.status, sampled_at and received_at before using a reading.

GET /api/v1/history

UTC-aligned means of recorded hashrate and BLAKE2b difficulty, with sample counts and coverage dates.

from / to: UTC ISO timestamps ending in Z. Default: last 24 hours, ending at the latest 30-second boundary. Start inclusive; end exclusive. Maximum window: 31 days. interval: auto (default), 30s, 5m, 1h or 1d. Maximum: 10,000 buckets. format: json (default) or csv.

GET /api/v1/blocks

Stored canonical BLAKE2b blocks, ordered by descending height. Optional block statistics can be null.

limit: 1–500 (default 100). before_height: exclusive height cursor. Pass meta.next_before_height to fetch the next page; null means no more stored blocks.

GET /api/v1/pools

Editorial pool terms, sources, DATUM support, review dates and unknown or provisional values.

No parameters. Fee and payout terms are descriptive strings, not guaranteed normalized numeric values. This is a sourced selection, not live pool telemetry.

Fetch observations in JavaScript

const response = await fetch(
  'https://blakestack.com/api/v1/network'
);
if (!response.ok) throw new Error('Data unavailable');
const { meta, data } = await response.json();
if (meta.status === 'live') {
  console.log(data.tip_height, data.hashrate_hps);
}

Network status can be live, stale, syncing, offline or waiting. With no stored observation, the endpoint returns 503. A stored observation can still return 200 with a stale or syncing status. Observation age is separate from block age.

Limits, units and reuse

  • Responses are cached for up to 30 seconds and support ETag / If-None-Match. Poll at most once every 30 seconds. A shared origin budget replenishes at two requests per second, with a burst of 30; requests beyond it return 429 and Retry-After. Concurrent data reads and cache size are bounded.
  • 400 means invalid parameters; 404 means an unknown endpoint; 405 means an unsupported method; 503 means observations are unavailable or the data service is busy. Error responses are not cached. GET, HEAD and OPTIONS are supported.
  • Hashrate uses H/s. Block intervals use seconds, fees use satoshis, block sizes use bytes and mempool size uses vbytes. BLAKE2b difficulty is distinct from SHA256d difficulty.
  • History averages observations, not independently measured hardware output. Null hashrates are excluded from means; empty buckets are omitted. Inspect sample counts and coverage. Boundary buckets only use observations inside your requested window.
  • Canonical block records and affected observations can change after reorganizations. Identify blocks by hash and re-fetch overlapping pages. A dated URL fixes a query, not an immutable snapshot.
  • Pool terms include their sources and actual review dates. Unknown fees stay unknown. The API provides descriptive terms, not a profitability promise.
  • You may use and redistribute BlakeStack’s network observation exports commercially or noncommercially. A source link is appreciated and optional. Third-party pool text and linked material remain subject to their respective rights. For research, cite the requested period, generation time and methodology and keep a downloaded copy.

Sources and methodology · Network history and CSV downloads