Get subscription and quota status
Return the authenticated account's current subscription state: plan, remaining/used/total credits, per-second rate limit (RPS), renewal date, and whether the subscription is active (in good standing) or affected by a non-payment or scheduled cancellation. Use it to programmatically confirm access before routing traffic. This endpoint is free — it does not consume credits — and returns a 200 even when your quota is exhausted (so you can detect exactly why calls are failing). Credits come from two balances - the monthly plan allowance and any pay-as-you-go credits bought outright (valid 12 months from purchase) - and creditsRemaining is their sum, broken out by subscriptionCreditsRemaining and paygCreditsRemaining. Values reflect our billing store and may lag real-time usage by a few seconds. Treat creditsRemaining > 0 as "can I call the API right now?" - a pay-as-you-go-only account has no subscription and reports status: "free" with active: false while still being able to call every endpoint. This endpoint is also metered on its OWN budget of 1 request per second per account, counted separately from your plan's per-second limit: polling it never consumes plan RPS (it returns X-RateLimit-Cost: 0), and a 429 here means you exceeded 1 req/s on this endpoint alone, not that your plan budget is spent. Because the call spends none of the plan window it does not report it, so this response carries no X-RateLimit-Remaining or X-RateLimit-Reset; X-RateLimit-Limit still shows your plan's RPS.
Request
- Base URL: https://api.fetchin.io
- URL: https://api.fetchin.io/api/v1/subscription
- Auth: API key in header X-API-Key
Response
Current subscription and quota status
Example response
{
"plan": "custom",
"active": true,
"status": "active",
"creditsRemaining": 684230,
"subscriptionCreditsRemaining": 184230,
"paygCreditsRemaining": 500000,
"paygExpiresAt": "2027-03-02T00:00:00.000Z",
"creditsLimit": 250000,
"creditsUsed": 65770,
"renewalDate": "2026-07-15T00:00:00.000Z",
"rpsLimit": 20
}Changes
No recorded changes to this operation across all 1 revision of this API.