Cloud Counter API GET

Counter is a simple tool for incrementing, decrementing, and resetting a cloud counter. It returns the current value of the counter.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/counter

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Cloud Counter response payload
  }
}

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

Analytics: Use the Counter API to increment or decrement counters for analytics. Use the data to track events, count occurrences, and measure performance
User Engagement: Increment counters by using the Counter API for user engagement. Use the data to track user interactions, monitor activity, and analyze behavior
Game Development: Use the Counter API to increment or decrement counters for game development. Use the data to track scores, count achievements, and manage progress
Data Processing: Increment counters by using the Counter API for data processing. Use the data to count records, track changes, and analyze trends

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

View all integrations →

Other ways to use Cloud Counter

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the Cloud Counter API.

Read the docs →

What does the Cloud Counter API do?

Counter is a simple tool for incrementing, decrementing, and resetting a cloud counter. It returns the current value of the counter.

How do I authenticate Cloud Counter API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Cloud Counter API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Cloud Counter API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Cloud Counter API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Cloud Counter API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

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
`id`Required	string	`test_counter`	The ID of the counter (e.g., test_counter)

Example request

1
2

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-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

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.

Sample response

{
  "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"`
`id`	string	`"test_counter"`
`lastAction`	string	`"get"`
`lastRead`	string	`"2025-12-16T22:21:45.000Z"`
`lastUpdated`	string	`"2024-04-26T22:09:46.000Z"`
`numberOfDigits`	number	`1`
`ordinal`	string	`"zeroth"`
`value`	number	`0`
`words`	string	`"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.

Compare all pricing tiers →

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

1
2

curl "https://api.apiverve.com/v1/counter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/counter-apiSource, issues and the examples this page is built from.ReferenceCloud Counter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/counternpm apiverve-counterPyPI APIVerve.API.CloudCounterNuGet

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.

Install — npm

npm install @apiverve/counter

Node.js

const 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

npm@apiverve/counterThe published Node.js client, versioned and signed.GitHubapiverve/counter-apiSource, issues and the examples this page is built from.ReferenceCloud Counter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

apiverve-counterPyPI APIVerve.API.CloudCounterNuGet

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.

Install — PyPI

pip install apiverve-counter

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/counter",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

PyPIapiverve-counterThe published Python client, versioned and signed.GitHubapiverve/counter-apiSource, issues and the examples this page is built from.ReferenceCloud Counter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/counternpm APIVerve.API.CloudCounterNuGet

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.

Install — NuGet

dotnet add package APIVerve.API.CloudCounter

C# / .NET

using 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

NuGetAPIVerve.API.CloudCounterThe published C# / .NET client, versioned and signed.GitHubapiverve/counter-apiSource, issues and the examples this page is built from.ReferenceCloud Counter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/counternpm apiverve-counterPyPI

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

@apiverve/counternpm apiverve-counterPyPI APIVerve.API.CloudCounterNuGet

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.

PHP

$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

@apiverve/counternpm apiverve-counterPyPI APIVerve.API.CloudCounterNuGet

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.

Ruby

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.body

Resources

Also published for

@apiverve/counternpm apiverve-counterPyPI APIVerve.API.CloudCounterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

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

Cloud Counter API GET

Try it — live request, no key required

About the Cloud Counter API

What people use it for

Ways to call it

Other ways to use Cloud Counter

Questions.

Request parameters — GET /v1/counter

Required

Authentication

Response — GET /v1/counter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/counter

Resources

Also published for

Call it from Node.js — GET /v1/counter

Resources

Also published for

Call it from Python — GET /v1/counter

Resources

Also published for

Call it from C# / .NET — GET /v1/counter

Resources

Also published for

Call it from Go — GET /v1/counter

Resources

Also published for

Call it from PHP — GET /v1/counter

Resources

Also published for

Call it from Ruby — GET /v1/counter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Cloud Counter API

Data Processing

Related articles

Ready to build with Cloud Counter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog