Account

Usage breakdown by endpoint

Cost: 0 credits. Credit usage grouped by endpoint.

period=billing exists because the rolling window never lines up with what you are actually billed on: the credit counter is zeroed at 00:00 UTC on the 1st of each month, so on the 18th a 30-day rolling total spans two allowances and cannot be reconciled against credits_used. The default stays rolling so no existing client changes behaviour.

⚠️ period_days is an int under period=rolling (it echoes days, unchanged) and a float under period=billing, where it is the measured length of the current period rather than a requested window — e.g. 31.0 for a period that started on the 1st. The widening only reaches callers who opt in by passing the new parameter; period_start and period_end are always returned so the window never has to be inferred from it.

get/v1/usage/analytics

Request

  • Base URL: https://api.puntersedge.online
  • URL: https://api.puntersedge.online/v1/usage/analytics
  • Auth: API key in header X-API-Key

Query parameters

daysinteger

Rolling window length. Ignored when period=billing.

periodstring

rolling = the last days days (default, unchanged). billing = the CURRENT billing period, so the totals here match credits_used and credits_remaining exactly.

Headers

X-API-Keystring
X-RapidAPI-Proxy-Secretstring

Response

Successful Response

unknown required

Changes

No recorded changes to this operation across all 1 revision of this API.