1. Home
  2. Docs
  3. API documentation
  4. GET
  5. Emission sum over 1d/7d/30d

Emission sum over 1d/7d/30d

Returns the total estimated emission value in USD across all tracked coins, aggregated for the most common recent timeframes: 24h, 7d, 30d.
Internally, the service queries emissionbytimeframe.php?frequency={d|w|m} and sums each coin’s EmissionUSD for those timeframes.


Endpoint

GET /emission.php


Description

For each timeframe:

  • 24h → fetched from frequency=d
  • 7d → fetched from frequency=w
  • 30d → fetched from frequency=m

The endpoint sums EmissionUSD across all items in data[] returned by emissionbytimeframe.php and emits a compact JSON summary.


Query parameters

None.


Response

Top level fields:

FieldTypeDescription
Timestampstring (ISO 8601, UTC)Time the summary was generated.
emission_24hstringTotal USD emission for last 24 hours.
emission_7dstringTotal USD emission for last 7 days.
emission_30dstringTotal USD emission for last 30 days.
subscriptionstringEchoed subscription label (currently "BASIC" in responses).

Formatting: numeric values are strings with 2 decimals, . as decimal separator and non-breaking space as thousands separator (e.g., "1 234 567.89"). Depending on client display, this may render as a regular space.


Example request

GET /emission.php

Example response

{
  "Timestamp": "2025-07-17T23:17:34Z",
  "emission_24h": "1 688 856 684.72",
  "emission_7d": "11 513 674 174.97",
  "emission_30d": "49 637 688 810.02",
  "subscription": "BASIC"
}

(Values shown are illustrative.)


Caching & freshness

  • The summary is cached on disk for 24 hours.
  • If a fresh cached file exists, it is returned immediately.

Errors

  • 403 — Access denied (Origin/Referer/header checks failed).
  • On upstream issues, the endpoint still responds 200 with zeroed sums for affected timeframes rather than erroring.

How can we help?