Alpha AnalystDocs

API Quickstart

Start with the Alpha Analyst API — create a key, resolve a company, then pull filings, financials, and the rest of the catalog.

The API exposes the same data as the Alpha Analyst platform: resolve a company once, then read SEC and EDINET filings as markdown, standardized financials, XBRL facts, screeners, FX spots, and your own uploads. Every call is JSON with an API key.

If you landed here first, follow the steps below. If you use Claude, Cursor, or ChatGPT, see MCP instead—another surface, not a substitute for these REST endpoints.

Catalog at a glance

  • Company identity — Turn a ticker, name, CIK, or LEI into one id you reuse on every other endpoint.
  • Filings & documents — Search and read exhibits across US EDGAR, Japan EDINET, and files you uploaded.
  • Numbers — Standardized statements, fundamentals time series, XBRL tags, and a latest snapshot screener.
  • Markets — Dated price and metric series, plus latest forex spots for currency conversion.
  • Your workspace — Watchlists and private document libraries for your account.

Get started

Create an API key. Open the API portal, sign in if needed, and generate a key under API keys.

Create API key

Send it on every request as Authorization: ApiKey YOUR_API_KEY. Authentication also covers Bearer tokens and query-string keys for clients that cannot set headers.

Resolve a company. You know the symbol or CIK → Entity Reference. You have a partial name or messy ticker → Entity Search. Read Entities once so ids, listings, and share classes make sense.

Call a dataset. Pick a group below, open its overview, then try the interactive request panel on any endpoint page. Check Coverage when you need counts, date ranges, or scope.

Limits and credentials. See Rate limits for quotas and 429 handling. Treat your API key as a secret—see Authentication—no matter how you call the API.

How platform-linked access works

Most endpoints serve shared catalog data. Watchlists and User Documents instead return your lists and files—the workspace tied to your website login.

One login carries two subscriptions: an API plan (permission to call the API) and a website plan (what the app allows—watchlists, Files, Japan, and the rest). Platform-linked routes check both; the website plan must include the feature you are calling.

An API key belongs to a user on that login. Each request resolves that user and applies the same entitlements as the website—via Authorization: ApiKey … only, not user_id. No user on the key → 401. No API plan or website feature → 403.

API groups

Documents searches SEC, EDINET, and uploads in one list when you want a single search box.

Base URL

https://alpha-analyst.com/apicontents plus the path on each endpoint page (for example /v2/entities).

Next