Problem type:
https://docs.nordicfinancialnews.com/problems/plan-limit-exceeded403 when your request is well formed and your key is valid, but your plan does not reach what you asked for. Three things produce it:
- Your plan does not include API access at all. Every request fails this way until the plan changes.
- The content sits outside your plan’s window. Plans differ in how far back they reach and how much of the calendar they cover, and an individual record beyond your window is refused rather than silently omitted.
- The endpoint or capability is not on your plan. Per-company calendars and incremental calendar sync are the usual examples.
Example response
detail usually names a way forward, and it is worth surfacing verbatim rather than replacing with your own copy. Where a narrower endpoint can answer the same question on your plan, this is where you are told about it.
How to fix it
Retrying changes nothing. Your plan is the same on the next request. Either take the alternativedetail names, if there is one, or upgrade the account. What each plan reaches is set out on the pricing page, and your current plan is shown in API key settings.
If you are building for other people’s accounts, treat this as an expected response rather than an error. Handle it by degrading to what the plan does cover, and show detail so the account owner understands what they are missing.
Not the same as the other 403
Insufficient permissions also returns403, but it is about the API key rather than the account. Editing scopes fixes that one and never fixes this one. Branch on type, not on the status code.
Note also that a resource your plan cannot reach is sometimes hidden rather than refused, returning 404 instead. A 404 is therefore not proof that something does not exist.
Related
- Error handling for the full problem type list
- Authentication for what counts toward your quota
- Insufficient permissions for the
403returned when your key lacks a scope