# public-apis-4Kr keeps its rankings in collapsed HTML tables > The public-apis-4Kr project is a Korean list of public APIs, updated to a stated date, whose two ranking tables sit inside collapsed HTML sections and label every row as either REST or LINK. **yybmion/public-apis-4Kr** — 한국 서비스에 이용 가능한 Public API 모음 | Public APIs Available for Korean Services - Repository: https://github.com/yybmion/public-apis-4Kr - Stars: 3,268 · Forks: 355 - Language: Python - License: MIT - Published: 2026-09-24 · Updated: 2026-09-24 · Language: en - Canonical page: https://hysenlabs.com/projects/yybmion-public-apis-4kr ## The Korean file is the default one The file that opens on arrival is the Korean version, and it says in one sentence what the project is: a list that systematically organises all the public APIs developers in Korea can use. A second line states that the content was updated with the latest information as of 2026-09-07 and will keep being updated periodically. Three Markdown files sit at the root of the repository, and the switcher near the top links all three: this Korean README, an English version named README_EN.md, and a third file for global public APIs named GLOBAL_PUBLIC_APIS_KR.md. Neither of the other two is reproduced in this file, so what a non-Korean reader sees by default is the Korean text, the Korean agency names and the Korean API names, with two ranking tables underneath them. ## Both ranking tables are collapsed by default The two tables are not plain Markdown. Each one sits inside an HTML details element whose summary line is its title, the first being the public data usage application top 10 for June 2026 and the second the top 20 for June 2026 counting cumulatively since 2026. A collapsed details element shows only that summary until someone expands it, so a reader who skims sees two headings and no data at all. Expanded, each table has the same five columns: rank, agency, the name of the Open API, a URL and a type. The URLs all point at the same host, data.go.kr, one per API identifier, with the detail page for that identifier. The type column is what separates the two worlds the file describes, and it holds only two values. ## Two type values, and they are not interchangeable Every row ends in either REST or LINK. In the June 2026 top 10 table, eight rows are REST and two are LINK, and the two LINK rows are the vehicle information service from the Ministry of Land, Infrastructure and Transport and the exchange rate information from the Korea Export-Import Bank. The cumulative table is more mixed: among the seventeen rows visible in this file, eleven are REST and six are LINK, including the real time address lookup, the continuous cadastral map, the geocoder and the recruitment listing service. That distribution is the practical point of the type column. A LIST row and a REST row are both counted as usage applications in the same table, so a ranking tells you an API is being called, not that it can be called the same way as its neighbour. ## One ministry takes four of the ten slots Read the agency column rather than the API column and the list stops looking varied. In the June 2026 table, the Ministry of Land, Infrastructure and Transport, 국토교통부, holds four of the ten ranks: 3 and 6 for apartment sale transaction data and its detail version, 7 for a vehicle information service, and 10 for a building registry service. Every other agency appears exactly once, among them the meteorological administration, the public procurement service, the national tax service, the astronomy institute, the export-import bank and the tourism organization. The cumulative table repeats the pattern, with the same ministry at ranks 3, 5, 10, 12, 13, 14 and 15 of the seventeen rows shown. Real estate and land registry data is what dominates both rankings here. ## The monthly ten is a subset of the cumulative twenty Every one of the ten rows in the monthly table also appears in the cumulative table, so the June list is a reordering rather than a new set of APIs. The ranks move, though, and by amounts that show what a single month buys. Apartment transaction data sits at 3 in both. The astronomy institute's holiday information climbs from 5 to 2. The public procurement service's bid notice service drops from 2 to 4, and the tax service's business registration check drops from 4 to 6. The vehicle information service falls from 7 to 5, the exchange rate service rises from 8 to 7, and the tourism service rises from 9 to 11. Rows 12 to 17 of the cumulative table, including the employment and financial services listings, have no place in the monthly ten at all. ## Only one of the two tables names its source The June table carries an attribution line above it: the figures come from the public data issue and recommendation page on data.go.kr, and the link includes the parameters that produce this particular view, an issue identifier, a type of USE, a sort order and a page size of 10. That is a reproducible pointer, and it is specific to the table beneath it. The cumulative table has no such line in this file. Its twenty-six years of accumulated usage are presented as a plain HTML table with a summary heading and no stated origin, so the two tables sit at different levels of traceability even though they share a shape and much of their content. If you need to check a number, only one of them tells you where to look. ## Markdown files plus a Python toolchain The repository is not only prose. Alongside the three Markdown files and the licence and contributing guide sit four directories: assets, reports, scripts and test, and the language recorded for the project is Python. Nothing in the visible text explains what those directories do, so a reader cannot tell from this file whether the rankings are generated or typed by hand, and there are no releases to inspect either, since the repository has none. What can be said from the layout is that the lists are maintained as a working directory rather than as a single exported page, with a place for images, a place for output and a place for tests, on the main branch whose last commit is dated 2026-10-02. ## Conclusion Treat this repository as a starting map rather than a dependency. Nothing here is code you import, the freshness date written into the file is 2026-09-07, and the entries themselves live on data.go.kr, where the key and the terms are decided. Before you plan a build on it, check three things: whether the English file and the global file hold the entries this Korean default file does not show, whether the API you want is one of the REST rows or one of the LINK rows, since the two are not interchangeable in what they return, and whether the ranking that pushed it to the top of a usage table still holds six months from now. Copy the data.go.kr identifier, not the ranking. ## FAQ ### What does the public-apis-4Kr project collect? It describes itself as a list that systematically organises all the public APIs developers in Korea can use, updated with the latest information as of 2026-09-07 and intended to be updated periodically from then on. ### Which languages does the public-apis-4Kr README come in? The default file README.md is Korean. An English version sits beside it as README_EN.md, and a third file, GLOBAL_PUBLIC_APIS_KR.md, is linked from the same switcher as the global public API list. ### What kinds of API does the public-apis-4Kr list record? Each ranking row ends in a type column holding one of two values, REST or LINK. In the June 2026 top 10 table eight rows are REST and two are LINK, and in the visible part of the cumulative table eleven are REST and six are LINK. ### Which agency appears most often in public-apis-4Kr rankings? The Ministry of Land, Infrastructure and Transport, 국토교통부, takes four of the ten slots in the June 2026 table at ranks 3, 6, 7 and 10, and appears at seven ranks of the cumulative table shown here. ### Does public-apis-4Kr publish releases? No, the repository has no GitHub releases. What it has is three Markdown files, directories for assets, reports, scripts and tests, and a last commit to main dated 2026-10-02. ## Sources - [Issues](https://github.com/yybmion/public-apis-4Kr/issues) - [License: MIT](https://github.com/yybmion/public-apis-4Kr/blob/main/LICENSE) - [README](https://github.com/yybmion/public-apis-4Kr/blob/main/README.md) - [yybmion/public-apis-4Kr on GitHub](https://github.com/yybmion/public-apis-4Kr) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/yybmion-public-apis-4kr