Mboum Finance API Review: Stocks, Options, News & More

What Mboum Finance does and who it is for

Mboum Finance started life as a wrapper around Yahoo Finance data and has since evolved into a standalone financial data platform with its own infrastructure. The API covers the full range of data a quantitative developer or fintech application typically needs: live and snapshot quotes, historical price series, fundamentals, options chains, insider transactions, SEC filings, earnings calendars, IPO schedules, dividend events, and a set of pre-computed technical indicators. That breadth makes it relevant for a wide range of builders — from individual algo traders running backtests to teams shipping full brokerage or portfolio-tracking products.

The API sits on RapidAPI's marketplace with a popularity score of 9.9 out of 10 and more than 3,500 subscribers, which is a meaningful signal of community traction. The reported average success rate is 100%, and average latency sits around 1,649 ms — acceptable for batch or background jobs, though worth factoring in if you are building a real-time UI that polls aggressively.

Endpoint walkthrough

With 78 total endpoints organized into logical groups, Mboum Finance covers significantly more ground than most single-purpose financial APIs. Here is what each major category delivers.

Market and quote data

GET /v1/market/tickers returns the universe of available symbols, which is useful for populating dropdowns or validating user input before fetching deeper data. Two separate quote endpoints handle real-time (/v1/market/quotes real-time) and snapshot quotes, giving you flexibility depending on whether you need the freshest tick or a cached value. The screener endpoint (/v1/market/screener) lets you filter the market based on custom criteria — handy for building watchlist generators or stock discovery features without maintaining your own screening logic.

Stock fundamentals via modules

The stock data layer is built around a single parameterized endpoint, GET /v1/markets/stock/modules, with the module query parameter selecting the data shape. This design keeps the base URL clean while exposing a rich set of data objects:

• Financials: income statement, balance sheet (v1 and v2), cash flow statement, financial data summary
• Earnings: current earnings, earnings history, earnings trend
• Ownership: institution ownership, insider holders, insider transactions, net share purchase activity
• Analysis: recommendation trends, upgrade/downgrade history
• Filings: SEC filings, index trend, calendar events per stock
• Profile: company name, description, website, and other metadata via asset-profile

Because each module maps to one GET request, applications that need several data points about a single stock will make multiple calls. Plan your request budget accordingly.

Options data

Three options endpoints cover different use cases. The base /v1/markets/options endpoint returns the full options chain for a given symbol. /v1/markets/options/most-active surfaces the contracts with the highest activity on the day, including IV rank and put/call ratio. /v1/markets/options/unusual-options-activity flags contracts trading at volume disproportionate to their open interest — a common signal-generation input for traders monitoring institutional flow.

Calendar events

Six calendar endpoints provide forward and historical visibility into earnings dates, dividend schedules, economic events, IPOs, secondary public offerings, and stock splits. These are broadly useful for scheduling automated data pulls or surfacing upcoming events in a product dashboard.

Technical indicators

Four pre-computed indicators are available directly: SMA (simple moving average), RSI (relative strength index), MACD (moving average convergence/divergence), and ADX (average directional movement index). If your application needs common signals without running them locally, this avoids implementing or maintaining that math yourself.

Historical data, news, and search

GET /v1/stock/history provides historical OHLCV data for backtesting or charting. Two news endpoints (/v1/market/news and /v2/market/news) return market news by sector and by ticker respectively. The search endpoint (/v1/search) resolves company names or partial symbols to tickers across stocks, ETFs, mutual funds, and crypto.

Note that several endpoints are documented as deprecated (marked with legacy path prefixes like /sc/, /ne/, /qu/, /hi/, /mo/, /op/). If you are starting a new integration, use the /v1/markets/ path family to avoid breakage when those legacy routes are removed.

Pricing breakdown

Mboum Finance uses a tiered freemium model. The table below summarizes the four plans available through the marketplace.

The free BASIC tier gives you 500 requests per month at one request per second. That is enough to experiment with endpoints and prototype a small personal project, but it will run out quickly in production — 500 requests disappears in minutes if you are polling quotes for even a small watchlist. Real applications will land on PRO at minimum.

At PRO, 100,000 requests per month at $19.95 works out to roughly $0.0002 per request before overage kicks in. If you exceed the quota, the $0.003 overage rate applies. ULTRA roughly halves the per-request cost and doubles the rate limit ceiling to 10 req/sec. MEGA is for high-throughput use cases — at 2.5 million requests, the included cost per request drops further, and the $0.001 overage rate is the most economical for burst traffic.

The provider also advertises plans up to 1.5 million requests through their own dashboard at mboum.com, with a 40% discount using code WELCOME40, which may offer different terms than the marketplace plans listed here.

Practical use cases

Portfolio tracker: Combine /v1/markets/stock/modules?module=asset-profile for metadata, real-time quotes for current prices, and historical data for performance charts. Calendar endpoints can surface upcoming earnings dates relevant to held positions.

Options flow monitor: The unusual options activity endpoint does the heavy lifting of identifying notable contracts. Pair it with the standard options chain for context on strike distribution and expiry.

Earnings season dashboard: The calendar/earnings endpoint gives you a forward-looking schedule. The earnings and earnings-history modules provide actuals and estimates for individual symbols. Together these support a full earnings research workflow.

Backtesting engine: Historical data plus technical indicators (SMA, RSI, MACD, ADX) pre-computed server-side reduces the local processing burden. This is practical for smaller backtests, though high-frequency strategies at large scale will need to consider the 1,649 ms average latency.

Things to verify before integrating

• Rate limits and quota math: Map your expected request volume to a plan before writing production code. If you poll 50 tickers every minute, that is 72,000 requests per day — well above the PRO monthly allowance.
• Latency tolerance: At roughly 1.6 seconds average, Mboum Finance is not suited to millisecond-sensitive trading systems. For analytical applications and background jobs it is fine.
• Deprecated endpoints: The legacy path prefixes are explicitly marked as deprecated. Avoid them in new code; build against the /v1/markets/ paths.
• Overage costs: PRO overage at $0.003/request can add up unexpectedly under bursty workloads. Implement request caching and quota monitoring early.

Getting started

1. Subscribe to a plan on the marketplace to receive an API key.
2. Include the key in the request headers of each HTTP GET call.
3. Parse the JSON response — all endpoints return JSON.
4. Start with GET /v1/market/tickers to confirm connectivity, then GET /v1/market/quotes with a known symbol to validate real-time data flow.
5. Review the full documentation at docs.mboum.com for parameter schemas and response field definitions for each module.

For integration questions, the provider offers support via [email protected].