Statement-first API
Fetch canonical income statement, balance sheet, and cash flow data through a single contract across regimes.
Zapi now runs live on api.zedxe.com. This public site layer is where users discover the API, understand regional coverage, compare access tiers, and enter the signup flow before account dashboards and token management arrive.
What ships now
Separate product surface
api.zedxe.com stays backend-only. zedxe.com/api becomes the marketing, docs, and signup layer.
Plan-aware auth
Site users graduate from anonymous access to signed JWT access without changing the statement contract.
Canonical financial data
The main site can keep replacing older finance dependencies and standardize on Zapi as the source of record.
Fetch canonical income statement, balance sheet, and cash flow data through a single contract across regimes.
The main ZedXe site owns plans, signup, and future token management while the API stays focused on data delivery.
US is official today. UK and India are partially live. Japan stays pending until the EDINET production key is available.
Terminal tables, charts, and later account dashboards can all read from the same Zapi response model.
Coverage
Coverage depth can differ from requested periods when the upstream filing history is incomplete. The docs surface that behavior directly in metadata.
Free, Plus, and Pro
Official SEC statements are the production baseline, including restated and as-reported views.
Pro when parser coverage is ready
Companies House auth is live, but full filing-level parser coverage is still being completed.
Pro as broader parser coverage comes online
Official annual coverage is live. Quarterly and TTM depth still depends on broader parser work.
Pro once the EDINET key is available
Official EDINET parsing is pending the production key, so Japan is not yet fully available on the live site flow.
Core endpoints
/v1/statements/:identifierCanonical financial statement endpoint for annual, quarterly, normalized, and matrix output.
Bearer JWT for Free, Plus, and Pro users, plus service-key access for internal backend traffic.
/v1/regimesCurrent adapter and regime status so the site can explain what is live, limited, or pending.
Public discovery access
/v1/auth/statusPlan-aware auth inspection endpoint for dashboards, quota display, and upgrade messaging.
Bearer JWT or service key
Example request
curl "https://api.zedxe.com/v1/statements/AAPL?regime=sec_edgar&statement=income_statement&frequency=annual&format=normalized&periods=5" \
-H "Authorization: Bearer YOUR_SITE_TOKEN"Normalized response shape
{
"meta": {
"ticker": "AAPL",
"companyName": "Apple Inc.",
"statement": "income_statement",
"frequency": "annual",
"view": "restated",
"currency": "USD",
"fiscalYearEnd": "Sep 30",
"titleSlug": "AAPL_income-statement_Annual_Restated",
"sourceRegime": "sec_edgar",
"requestedPeriods": 3,
"returnedPeriods": 3,
"historyCoverage": "full",
"qualityFlags": []
},
"columns": ["2023", "2024", "2025"],
"rows": [
{
"metricCode": "gross_profit",
"label": "Gross Profit",
"depth": 0,
"unit": "USD",
"rowKind": "metric",
"values": [169148000000, 180683000000, 195036000000],
"qualityFlags": []
}
],
"periods": {
"2025": {
"revenue_total": 416161000000,
"eps_diluted": 7.46
}
}
}Access tiers
The product model is now Free, Plus, and Pro. Rate limits are deliberate guardrails so individual users cannot spam the API and cause instability for the rest of the app.
Signed-in starter plan
$0
100
requests per hour
Best for getting started with the API while keeping abuse risk low through tighter rate limiting.
Paid US plan
$7/mo
500
requests per hour
Adds a higher US-only rate limit and includes the API access path for the upcoming Excel plugin.
Full API plan
$10/mo
2,000
requests per hour
Designed for serious product use with broader region access and a materially higher rate limit.