Most list endpoints in the MKK API accept a common set of query parameters that let you narrow results by fund, time period, section, or free-text search. Understanding how these parameters compose — and how pagination works — will help you write precise queries rather than fetching and filtering data client-side.Documentation Index
Fetch the complete documentation index at: https://demircancelebi.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Common filter parameters
| Parameter | Type | Applies to | Description |
|---|---|---|---|
fund_id | integer | Most list endpoints | Filter by the fund’s internal numeric ID. |
fund_code | string | Most list endpoints | Filter by fund code (e.g. OJB). Preferred over fund_id for readability. |
period | string | Documents, line-item-values, portfolio-entries | Match on period string prefix (e.g. 2023, 2023-Q1). |
section_id | integer | Sections, line-item-values | Filter by the section’s internal ID. |
line_item_slug | string | Line-item-values | Filter by line item slug (e.g. net-asset-value). |
q | string | Documents, sections, line-items | Full-text search across label and text fields. |
label | string | Line-item-values | Filter values by their display label (partial match). |
limit | integer | All paginated endpoints | Maximum results per page. |
offset | integer | All paginated endpoints | Number of results to skip. |
Using fund_code vs fund_id
Bothfund_code and fund_id identify the same fund, but fund_code is a human-readable string (e.g. OJB) while fund_id is an opaque integer. Use fund_code when you are working interactively or constructing URLs by hand — it is stable across environments and easier to read in logs.
fund_code takes precedence.
Filtering by period
Theperiod parameter performs a prefix match on the period string stored for each document or value. This means you can filter at any level of granularity — year, quarter, or full period string.
Period strings are stored as-is from the MKK disclosure data. Common formats include
YYYY, YYYY-QN, and YYYY-MM. Pass the prefix that matches the granularity you need.Text search with the q parameter
Use theq parameter on the /documents, /sections, and /line-items endpoints to search by label or text content. The search is case-insensitive and matches partial strings.
Filtering line item values by section and slug
On/line-item-values (and its alias /key-values), use section_id to restrict results to a specific section of a document, and line_item_slug to retrieve values for a specific line item across all documents or periods.
label with other filters to match values by their display label:
Filtering portfolio entries
Use/portfolio-entries with fund_code, period, and section to find holdings for a given fund and period.
Pagination
All list endpoints return atotal field alongside the data array. Use limit and offset together to page through results.
funds, documents, line_items, portfolio_entries, etc.).
Use total to determine how many pages exist: ceil(total / limit). Keep incrementing offset by limit until offset >= total.
Per-endpoint limits
| Endpoint | Maximum limit |
|---|---|
/line-items | 500 |
/stocks | 1000 |
| All others | Varies; check total in response |
Paginating embedded portfolio in fund detail
When usinginclude_portfolio=true on GET /funds/{fundId}, the embedded portfolio list is paginated with its own portfolio_limit and portfolio_offset parameters — separate from the top-level limit and offset.
portfolio_entry_count field at the fund level indicating the full count of portfolio entries for that fund, and portfolio_limit/portfolio_offset reflecting the pagination applied to the embedded array.