Track and adjust persistent totals without running a database.
Cloud Counter stores and updates persistent numeric counters by ID without needing a database. It tracks increments, decrements, and custom values while returning timestamps and number properties like parity and prime status.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
"created": "2024-04-26T22:09:46.000Z",
"id": "test_counter",
"lastAction": "get",
"lastRead": "2025-12-16T22:21:45.000Z",
"lastUpdated": "2024-04-26T22:09:46.000Z",
"numberOfDigits": 1,
"ordinal": "zeroth",
"value": 0,
"words": "zero",
"isEven": true,
"isNegative": false,
"isZero": true,
"isPrime": false
}
}
About the Cloud Counter API
Counter works by incrementing, decrementing, and resetting a cloud counter. It uses advanced algorithms to ensure the counter is updated accurately and returns the current value of the counter.
What people use it for
- Article View Counts
- Increment a page tally each time a reader loads a blog post, returning the fresh total without querying a local database.
- Feature Usage Quotas
- To enforce monthly limits, SaaS backends increase a user action counter and check whether the total crosses allowed thresholds.
- Live Score Tracking
- Gaming servers adjust player points up or down during matches while fetching parity and formatted word representations.
- Inventory Stock Adjustments
- When shoppers complete checkout, decrement item tallies and inspect the remaining balance without maintaining dedicated database tables.
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Cloud Counter
Same data, same APIVerve account, same credit balance — one key works on all of them.
What operations can I perform on a counter?
Does the counter support negative numbers and zero?
Can I adjust a counter by custom step amounts on the Free plan?
What would 50,000 counter updates a month cost me?
What metadata does reading a counter return?
Request parameters — GET /v1/counter
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
idRequired | string | test_counter | The ID of the counter (e.g., test_counter) |
curl "https://api.apiverve.com/v1/counter?id=test_counter" \
-H "x-api-key: YOUR_API_KEY"Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — GET /v1/counter
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"created": "2024-04-26T22:09:46.000Z",
"id": "test_counter",
"lastAction": "get",
"lastRead": "2025-12-16T22:21:45.000Z",
"lastUpdated": "2024-04-26T22:09:46.000Z",
"numberOfDigits": 1,
"ordinal": "zeroth",
"value": 0,
"words": "zero",
"isEven": true,
"isNegative": false,
"isZero": true,
"isPrime": false
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
created | string | "2024-04-26T22:09:46.000Z" | ISO timestamp of when the counter was first created |
id | string | "test_counter" | The identifier of the counter |
lastAction | string | "get" | The most recent action performed on the counter (e.g., get, up, down, set) |
lastRead | string | "2025-12-16T22:21:45.000Z" | ISO timestamp of when the counter was most recently queried |
lastUpdated | string | "2024-04-26T22:09:46.000Z" | ISO timestamp of when the counter's value was last changed |
numberOfDigits | number | 1 | The number of digits in the counter's current value, not counting a negative sign |
ordinal | string | "zeroth" | The counter's current value spelled out as an ordinal word (e.g., "zeroth") |
value | number | 0 | The counter's current numeric value |
words | string | "zero" | The counter's current value spelled out in words (e.g., "zero") |
isEven | boolean | true | Whether the counter value is even |
isNegative | boolean | false | Whether the counter value is negative |
isZero | boolean | true | Whether the counter value is zero |
isPrime | boolean | false | Whether the counter value is a prime number |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 2 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Cloud Counter calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — GET /v1/counter
No SDK to install — this is a plain HTTPS call to /v1/counter with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/counter" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — GET /v1/counter
Install the Node.js SDK, then call the Cloud Counter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/counterconst res = await fetch("https://api.apiverve.com/v1/counter", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — GET /v1/counter
Install the Python SDK, then call the Cloud Counter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-counterimport requests
res = requests.get(
"https://api.apiverve.com/v1/counter",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — GET /v1/counter
Install the C# / .NET SDK, then call the Cloud Counter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.CloudCounterusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/counter");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — GET /v1/counter
No SDK to install — this is a plain HTTPS call to /v1/counter with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/counter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — GET /v1/counter
No SDK to install — this is a plain HTTPS call to /v1/counter with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/counter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — GET /v1/counter
No SDK to install — this is a plain HTTPS call to /v1/counter with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/counter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Cloud Counter form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Cloud Counter API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Cloud Counter API.
Data Processing
Related articles
All articles →
Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
Business Day Math Is Harder Than You ThinkWeekends, holidays, and country-specific rules make working day calculations surprisingly tricky. Here's what to watch for.Read