Skip to main content
Your plan bundles a number of credits per billing period. Each paid request deducts a fixed number of credits. Free endpoints deduct nothing. Denied and rate-limited requests are never billed: metering happens only after authentication, the access check and the rate limit have all passed.

Cost per endpoint

The sales list is the one endpoint priced by quantity. Its cost is ceil(sales_limit / 20): the default 20 rows cost 1 credit, 100 rows cost 5, the maximum of 200 rows costs 10. A sales_limit outside 1..200 is rejected with 400 invalid_parameter before anything is charged.
The ping endpoints are billed like any other call on their API. To test a key for free, use GET /usage.

Included, purchasable, or on request

Each key carries the list of APIs it may call. Calling an API your key is not granted returns 403 forbidden regardless of your credit balance. To enable an API on your key, contact Eventory.

Included quota versus hard cap

Two numbers from GET /usage matter:
  • credits.included is the quota bundled into your plan for the period. Going past it does not block you; usage beyond it is billed as overage.
  • credits.hard_cap is where the gateway stops serving. A paid request is refused with 402 limit_reached when its cost would take usage past the cap, so near the cap a 5-credit scrape can be refused while 1-credit calls still pass. At the cap, every paid request is refused until the period resets or the cap is raised. Free endpoints keep working. A cap of "unlimited" means there is no ceiling.
usage_status folds this into one field you can switch on: credits.remaining is what is left of the included quota (or of the hard cap, if that is lower). It reads 0 once you are in overage, even though paid requests keep being served until the hard cap. credits.used can trail your most recent requests by a minute or so. credits.projected_used extrapolates your current pace to the end of the period.

Subscription state

Only active and trialing subscriptions are served. A paused, cancelled, unpaid or past-due subscription returns 402 no_subscription on every paid endpoint. GET /usage still answers, with "status": "none" and zeroed credits, so you can detect the situation programmatically. A plan without API credits, such as Monitors Essential, is answered the same way.

Keeping costs down

  • Cache GET /events/platforms. The registry changes rarely and costs 5 credits.
  • If you have Notifications API access, prefer it to polling. Watching an event deducts no credits; scraping it every minute is 5 credits a minute.
  • Request only the sales rows you need. sales_limit=40 costs 2 credits; sales_limit=200 costs 10.
  • Do not retry 4xx responses. They are billed once and will fail again. Retry only 5xx, with backoff: each retry is billed like a new request.
Last modified on October 31, 2026