Upstox's fundamentals limits are per endpoint, and cannot be bought higher

Upstox's fundamentals limits are per endpoint, and cannot be bought higher

The Upstox story is not a blog post but a forum answer, and it is more useful than most. A developer on the Upstox community asked about Company Fundamentals API rate limits and paid options for higher limits, and the reply from @Ketan spells out the model in six points. Limits apply “per API, per user.” Each Fundamentals endpoint, profile and income statement and so on, has its own allowance of 50 a second, 500 a minute and 2,000 per 30 minutes, and every company and parameter counts against that endpoint. Fundamentals calls do not touch the historical candle or other market data limits. And the one line every integrator wants answered: “The limits are the same for every user, with no paid plan or custom increase.”

There are no marketing numbers here, only limits, and they survive because they are concrete. All of a user’s apps and tokens, OAuth and Analytics alike, share one allowance per API, so spinning up a second app buys nothing. Exceeding it returns HTTP 429 with the code UDAPI10005. The reply even does the math for the asker: 2,666 companies across 7 endpoints, paced under 500 a minute per endpoint, “completes the download in a little over an hour.” That is the right way to answer a rate-limit question, with the arithmetic, not a sales link.

Upstox on apis.io carries 23 API pages, and the thread is about one of them, the Upstox Fundamentals API. It also explains why the separation matters: the market data a fundamentals crawler might otherwise compete with sits on its own pages, the Upstox History V3 API for candles and the Upstox Market Quote V3 API for quotes, each with its own budget. The per-user rule ties back to the Upstox Login API, since the token, not the app, is what is counted.

The measurement confirms the answer. Upstox scores 74.7 on the Kin Score, exemplar, with operational transparency at 94.7, the highest of today’s five provider stories, and rate limit signal lit in an Agent Readiness score of 53.3. Contract governance is the weak facet at 18.2, and idempotency and agentic access are unlit. The limits themselves, though, live in a forum reply. A table this clear belongs in the Fundamentals contract, where a crawler can read it before it earns its first UDAPI10005.

← Union Square Ventures' portfolio lists Stack Overflow, and our rollup scores it as Microsoft Active Directory
Whop's KYC tutorial walks an identity API the catalog has not mapped →