Statistics API User Guide

Knowing how much of your API quota you’ve used — and how much you have left — sounds like it should be simple. But for developers and teams running applications on top of blockchain infrastructure, that information is surprisingly hard to get without digging through a dashboard every time. The NOWNodes Statistics API solves this by letting you pull your subscription and usage data programmatically, on demand, directly into whatever system you’re building.

This guide walks you through what the Statistics API does, who can use it, and exactly how to get it working.

What the Statistics API does

At its core, the Statistics API answers one question: where do you stand? Send a request to the endpoint, and you get back a structured snapshot of your current subscription — when it started, when it expires, how many requests you’ve made, how many remain, and what percentage of your allocation you’ve burned through. That’s the full picture in a single call.

This matters most when you’re building tools that need to make decisions based on resource availability, or when you want to monitor usage without logging into a dashboard manually. A backend service, a monitoring script, a Slack alert that fires when you hit 80% — all of these become straightforward once you have programmatic access to this data.

Who can use it

The Statistics API is available on NOWNodes Business plans and above. If you’re on a lower tier and want access, upgrading your subscription will unlock the endpoint.

The endpoint

Everything happens at a single URL:

GET https://api.nownodes.io/v1.0/statistics

You pass your access token as a query parameter:

https://api.nownodes.io/v1.0/statistics?token=YOUR_TOKEN_HERE

That’s it. No request body, no headers beyond what your HTTP client handles automatically. A successful call returns a JSON object with the following fields:

• subscription_type — the name of your current plan
• activated_at — the date and time your subscription started, in ISO 8601 format
• expires_at — when your subscription ends
• used_requests — the total number of requests consumed so far in this subscription period
• request_limit — your plan’s maximum request allowance
• remaining_requests — what’s left
• usage_percent — your consumption as a rounded whole number percentage

A real response might look something like this:

{
  "subscription_type": "Business",
  "activated_at": "2026-01-01T00:00:00Z",
  "expires_at": "2026-12-31T23:59:59Z",
  "used_requests": 4200000,
  "request_limit": 10000000,
  "remaining_requests": 5800000,
  "usage_percent": 42
}

Every field in that response is guaranteed to be present — the API specification marks all of them as required, so you won’t need to write defensive fallback logic for missing values.

When things go wrong

The API returns standard HTTP status codes, so error handling is predictable. If your token is missing or invalid, you’ll get a 401 response with a message explaining the authentication problem. If your token exists but your plan doesn’t include Statistics API access, you’ll get a 403. Internal server errors come back as 500. In each case, the response body contains a message field describing what went wrong, which makes debugging straightforward.

Practical ways to use this

The most obvious use case is automated monitoring. Set up a cron job or scheduled function that calls the endpoint every hour, logs the usage_percent, and sends an alert if it climbs above a threshold. This keeps you from hitting your limit unexpectedly during peak traffic.

Teams building internal tooling can surface this data in dashboards or admin panels, giving non-technical stakeholders visibility into infrastructure usage without needing access to the NOWNodes dashboard directly.

You can also use it as a pre-flight check in your application — if remaining_requests drops below a defined minimum, your app can throttle its own behavior or surface a warning before you run out entirely.

The Statistics API is a small surface, intentionally so. One endpoint, one token, one clean response. That simplicity is the point: usage data should be easy to get, and now it is.