Endpoints overview

Every endpoint lives under https://api.equibles.com/v1. Many datasets also have an MCP tool, but the two surfaces are not identical and each reference documents its own coverage and response shape. All endpoints are GET requests except your own portfolios, which also accept POST, PATCH and DELETE. Portfolios are the only write endpoints; portfolios and trackers are the account-owned read surfaces whose answer differs per API key. See the API guide for auth, pagination, and the response envelope. Prefer to try them live? The interactive Swagger docs document every parameter and response schema.

Each family page below lists its endpoints and parameters. Established data families also include a worked example — a curl / Python / JavaScript request and the real JSON response (mostly for NVIDIA, ticker NVDA).

Start with a task

Endpoint families

• Stocks & ETFs — shared /stocks market-data routes, compatibility aliases, and the distinction between ETF portfolios and their owners.

• Filings & documents — list, search, and read filings and transcripts; Form D.

• Fundamentals & valuation — revenue breakdowns, company KPIs, the non-GAAP bridge, management guidance, valuation multiples, customer concentration, and going-concern status.

• Debt profiles — issuer-reported totals, stable notes and credit facilities, covenant terms, filing history, and exact SEC evidence.

• Earnings calls & investor relations — call briefs and insights, call events and speakers, investor-day events and slide decks, and the IR news feed.

• Institutional holdings (13F) — holders, ownership, activity, leaderboards, institution portfolios, and super-investors.

• ETFs — dedicated exchange-traded ticker search, performance, assets, allocations, and holdings.

• Funds & advisers — fund holdings and operations, funds holding a stock, and Form ADV advisers.

• Insider trading — transactions, ownership, Form 144 proposed sales, insider search, and sentiment scores.

• Congressional trading — trades, member search, net-worth, and market-wide aggregates.

• Short data — short volume, short interest, off-exchange volume, fails-to-deliver, and squeeze scores.

• Capital, executives & screening — buyback and ATM programs, executive changes and compensation, and the stock screener.

• Prices & technicals — daily OHLCV, dividends and splits, the latest close/volume for many tickers, intraday quotes, technical indicators, and correlated stocks.

• Economic data (FRED) — series search, observations, latest values, and the release calendar.

• Options — listed expirations, the calls-and-puts chain with greeks and open interest, and a single contract by OCC symbol.

• IPOs — the S-1/F-1 pipeline with verified offer terms, pre-IPO financials, and prospectus insights.

• FDA catalysts — scheduled FDA advisory-committee meetings.

• Government contracts — awards won by a company and the top contractors.

• Futures positioning (CFTC) — contract search, weekly COT positioning, and the latest snapshot.

• Market sentiment (CBOE) — put/call ratios and VIX.

• Market status & calendar — whether the market is open now, and the holiday calendar.

• Stock indexes — constituents of the S&P 500, 400 and 600, the Nasdaq-100, the Russell 1000 and 2000 and the Dow, the additions and deletions behind each list, and the published entry rules applied to every company we track.

• Your portfolios — create portfolios, record stock and option lots, close or correct them, watch instruments you don't hold, and read a priced portfolio with unrealized and realized profit and loss.

• Trackers — read the schedule and latest verified results for recurring web collections created and managed in the Portal.

Conventions

• Auth — every request needs your API key as a Bearer token (or ?api_key=). See Authentication.
• Paging — paged endpoints take limit (and usually offset) and wrap rows in { data, meta }, where meta.hasMore signals another page. Max limit is 500, and some endpoints cap it lower. Not every list endpoint is paged: many take limit only, some take no query parameters at all, and several return domain context (ticker, coverage, totals) beside data instead of a meta block. Each endpoint's worked example below shows its real envelope.
• Unknown parameters are rejected — a query parameter an endpoint does not declare returns 400 invalid_parameter and the message lists every name that endpoint accepts. That error is the quickest way to discover an endpoint's real parameter set, and the OpenAPI spec carries the same list.
• Wire format — JSON with camelCase fields; dates are YYYY-MM-DD.
• Check the scale before you do arithmetic. Percentage-style values are not on one convention: shortVolumePercent arrives as 39.38 (meaning 39.38%) while shortInterestPercentOfShares arrives as 0.232 (meaning 23.2%), and a Percent in the field name does not settle which. Read the scale off the worked example for the endpoint you are calling rather than assuming.
• Errors & limits — non-2xx returns { "error": { "code", "message", "status" } }; requests count against a daily limit shared with MCP. See Errors & retries and Plans & limits.