MKK Structured Data API: Overview and Data Model

Learn how the MKK Structured Data API turns PDF fund disclosure reports into queryable, normalized JSON data you can integrate into your own tools.

The MKK Structured Data API gives you programmatic access to normalized financial disclosure data extracted from MKK and VYK PDF reports. Rather than parsing raw PDFs yourself, you query a structured REST API that exposes funds, documents, financial line items, and portfolio holdings — all organized into a coherent data model and served as JSON over HTTPS.

Data model

The API is organized around five core resources that reflect the natural hierarchy of fund disclosure data:

Fund
 └── Document (a single disclosure PDF)
      ├── Section (a canonical section of the report)
      │    └── Line Item Value (a financial metric or text value)
      └── Portfolio Entry (a holding within that document)

• Fund — The top-level entity. Each fund has a unique code (e.g., OJB) and groups all documents filed for that fund over time.
• Document — A single parsed disclosure report tied to a fund and reporting period. Documents are the source of all structured data in the API.
• Section — A named, canonical section of a report (e.g., “Net Assets”, “Expense Ratios”). Sections provide a consistent schema for comparing data across funds and periods.
• Line Item Value — A single financial metric or text value within a section. Line items are what you query when you want numbers like NAV, expense ratios, or descriptive text fields.
• Portfolio Entry — A single holding row from a fund’s portfolio table. Each entry includes security identifiers, market value, weight, and quantity where available.

Two additional resources round out the model:

• Stock — A deduplicated view of equity securities held across all funds, useful for cross-fund analysis.
• Export — CSV download endpoints for bulk data access.

What makes this data unique

MKK and VYK fund disclosures are published as PDF documents. Extracting structured data from PDFs is non-trivial: layouts shift across report versions, numeric formats vary, and section headings are not standardized. This API solves that by providing data that has already been:

• Extracted from source PDFs using document parsing pipelines
• Normalized so that the same metric (e.g., total net assets) maps to the same line item definition across funds and periods
• Structured into a relational model you can filter, join, and export without any PDF processing on your end

The result is a queryable dataset that reflects the full disclosure history available in the underlying reports.

Base URL and access

All endpoints are served from:

https://mkk-roan.vercel.app/api

The API is read-only — it does not accept POST, PUT, PATCH, or DELETE requests. No authentication is required; all endpoints are publicly accessible.

Because the API is read-only and unauthenticated, you can start querying immediately without registering for an API key or setting up credentials.

Key capabilities

Capability	Description
List and filter funds	Retrieve all funds or look up a specific fund by code
Browse disclosure documents	Access structured data from individual PDF reports
Query financial line items	Filter metrics by fund, period, section, or line item type
Explore portfolio holdings	Get normalized holdings with security identifiers and weights
Cross-fund equity lookup	Find all funds holding a given stock via the Stocks resource
Data quality review	Access flagged entries and review queues for quality monitoring
Bulk CSV exports	Download line item values and portfolio data as CSV files

Start exploring

Quick start

Make your first API call in minutes with step-by-step curl examples.

Funds

Understand the top-level fund resource and how to filter by code and period.

Documents

Learn how disclosure PDFs map to structured documents in the API.

Line items

Query canonical financial metrics across funds and reporting periods.

Portfolio entries

Access normalized holdings data including security identifiers and weights.