Skip to main content

​
How Quotas Work

Fetchin uses a quota system to track your API usage. Each API request consumes one credit from your quota. The one exception is /post/engagement, which returns comments and reactions together and bills 2 credits, all or nothing.

​
Credit Counting

Paginated endpoints charge per page you request, not per item returned.

​
What is billed

  • ✅ Successful requests - the price of the endpoint, from the table above
  • ⚠️ 404 not found - 1 credit, always 1 even on /post/engagement
  • ✅ Every other failure (400, 401, 403, 429, 402, 5xx) - free
  • 🔄 Quota renewal - happens automatically on your renewal date
A 404 is the one failing response that costs a credit, and confirming an absence costs more than returning a record rather than less. A success answers on the first attempt; an absence is only concluded once two independent sessions agree, across up to ten attempts, so a login wall is never reported to you as a missing record.Accounts created from 27 August 2026 onwards are charged from their first request. Accounts that existed before then are not charged for 404s until 1 October 2026.
Nothing else billable exists. Authentication errors, validation errors, rate limiting, running out of credits and any failure on our side are all free. Full breakdown at fetchin.io/pricing/credits.

​
Available Plans

Trial Plan

1,000 credits/monthPerfect for testing and small projects
  • Auto-created on signup
  • 5 requests per second (RPS)
  • Renews monthly
  • Free forever

Enterprise Plan

Custom limitsFor production workloads
  • Custom monthly credit limits
  • Custom RPS limits
  • Priority support
  • Volume discounts
  • Contact sales

​
Monitoring Your Quota

​
Dashboard

Your dashboard shows real-time quota information:
  • Credits Remaining - How many credits you have left
  • Plan Limit - Your monthly quota
  • RPS Limit - Your requests per second limit
  • Renewal Date - When your quota will reset
  • Usage Chart - Daily breakdown of your usage

​
Checking Quota Programmatically

Call GET /api/v1/subscription to read your quota from code. It returns the same figures the dashboard shows, and it does not consume credits.
Use creditsRemaining to back off before you hit 402, and renewalDate to know when the allowance resets. active reflects billing standing only, so check both: a subscription can be active with zero credits left.
This endpoint is free and is not gated on your quota, so it keeps answering after you have been blocked with 402. When a request fails on quota, call it to find out whether you are out of credits or whether billing needs attention. Your per-second rate limit still applies.
Poll this on a schedule rather than before every request. Usage is counted in memory and written back every 30 seconds, so creditsRemaining can lag your real consumption by up to that much during a burst. Leave yourself that much headroom rather than pacing right up to the last credit.

​
Quota Management

​
What Happens When You Run Out?

When your quota reaches 0, API requests return a 402 Payment Required error with code: "QUOTA_EXHAUSTED". This is distinct from a 429 Too Many Requests (code: "RATE_LIMITED"), which is per-second throttling — the HTTP status alone tells them apart:

​
Options When Quota Is Exceeded

1

Wait for renewal

Your quota automatically resets on your renewal date (shown in dashboard)
2

Upgrade your plan

Contact sales for an Enterprise plan with higher limits
3

Buy additional credits

Pay-as-you-go credits are available on request. Contact support with your expected volume and we will set up a quote.

​
Pay-As-You-Go Credits

Pay-as-you-go lets you buy credits on top of your plan instead of upgrading it, billed per request with no monthly commitment. It is provisioned on request rather than self-serve, so tell support the volume and request rate you expect and we will quote it.

​
Best Practices

Store API responses locally to avoid redundant requests for the same data.
Use exponential backoff for failed requests instead of immediately retrying.
Check your dashboard regularly to track usage patterns and avoid surprises.
Quota exhaustion is 402 with code: "QUOTA_EXHAUSTED", and retrying will not clear it. Handle it separately from 429 (RATE_LIMITED), which is per-second throttling and is worth retrying after a short backoff.

​
Quota Reset Schedule

Quotas reset monthly on your signup anniversary:
  • Signed up on January 15 → Resets on the 15th of each month
  • Signed up on March 31 → Resets on the last day of each month
  • Time zone: UTC
Unused credits do NOT carry over to the next month. Use them or lose them!