billing

GET /v1/usage/visits

Get the organisation's metered visits and any overage charge.

Ҳамаи нуқтаҳои ниҳоии billing

Санҷиши ҳаққоният

Kaliti API-ро ҳамчун рамзи доранда (bearer token) фиристед. Калит бояд дорои иҷозати billing.view бошад; калиди бидуни он бо хатои 403 рад карда мешавад, на 404.

Ин нуқтаи поёнӣ ягон рақами мушаххаси созмонро талаб намекунад. Калиди шумо аллакай созмонеро, ки ба он тааллуқ дорад, муайян мекунад ва ҷавоб ба он маҳдуд карда мешавад.

Санҷидан

Ҳар чизро дар қаavски кунҷӣ бо қиматҳои худ ва ҷойи нигоҳдорандаи калидро бо калима аз панели идоракунии худ иваз кунед.

curl -X GET https://api.zinndigital.com/v1/usage/visits \
  -H "Authorization: Bearer zdk_live_…"

Воarid шудаед? Консоли API дар панели идоракунии шумо рақами мушаххаси ташкилоти воқеӣ ва калиди худро пур мекунад ва дархостро бар зидди API-и фаъол иҷро мекунад, то шумо посухи воқеиро бубинед. Ин нуқтаи ниҳоиро дар консоли API кушоед

Тафсилот

Billable page views for the current billing period against the plan's `monthly_visits` allowance, plus the overage that has accrued. Requires `billing.view` rather than `sites.view`: this endpoint's distinguishing content is a **charge**, and a teammate granted site access to publish content should not thereby learn what the account is about to be invoiced. **Over the allowance, the site keeps serving** (owner ruling 2026-08-11). Nothing is throttled, suspended or refused for being popular; the excess is billed per block of 10,000 page views and shown here before the invoice is raised. **The first partial period is pro-rated.** Metering began on 2026-08-11 and nothing before it can be measured, so a period that started earlier has its allowance scaled to the part actually observed and `prorated` is `true` — otherwise a customer would be billed for a gap in our own instrumentation. `fullAllowance` carries the unscaled monthly figure so the UI can show both. `overageAmountMinor` and `overageCurrency` are `null` **together** when no overage rate is in force. That is a real state and it is not zero: "not yet priced" and "costs nothing" are different facts, and only one of them is safe to show a customer as a bill.

Ҷавоб

НомНамудТалаб карда мешавадИн чӣ аст
period_startstringБалеStart of the subscription's current billing period.
period_endstringБалеEnd of the subscription's current billing period.
page_viewsintegerБалеBillable human page views this period, across every site the plan pays for.
excluded_page_viewsintegerБалеPage views excluded as automated. Published so the bot rule is auditable — a customer disputing an invoice can see what they were not charged for.
allowanceintegerБалеThe ceiling applied to this period, already pro-rated where `prorated` is true. `-1` means unlimited.
full_allowanceintegerБалеThe plan's unscaled monthly `monthly_visits` grant, so the UI can quote the pricing-page figure alongside a pro-rated one.
proratedbooleanБалеWhether `allowance` was scaled down because this period began before metering did. Surfaced so a number that will not match the pricing page can be explained rather than looking…
unlimitedbooleanБалеWhether the plan grants unlimited visits.
remainingintegerБалеPage views left in the allowance. Never negative.
over_byintegerБалеPage views beyond the allowance. Never negative.
over_limitbooleanБалеWhether the allowance has been exceeded. The site keeps serving either way.
overage_blocksintegerБалеBlocks of overage, rounded **up** — one page view over the allowance buys a whole block.
overage_amount_minorintegerБалеThe overage charge in minor units of `overage_currency` (integer minor units, never a float). `null` when no overage rate is in force, which is not the same as zero.
overage_currencystringБалеISO 4217 code for `overage_amount_minor`. Null exactly when it is.

Хатоҳое, ки ин нуқтаи ниҳоӣ метавонад баргардонад

401 · 403 · 404 · 429