public-apis/public-apis is the internet's favourite API directory — and it needs your pull request.
There are roughly 1,400 free APIs catalogued in one Markdown file on GitHub, and that file has been starred more than 427,000 times. Someone, somewhere, is opening it right now to find a weather endpoint for a side project. The question is: who keeps it accurate?
Setting
The public-apis/public-apis repository started as a simple community list — a single README.md grouping free, publicly accessible APIs by category (animals, finance, music, government data, and dozens more). No database, no backend, no sign-up required. Just a well-formatted table that developers could ctrl+F their way through.
That simplicity is both its superpower and its problem. The repo is maintained by a very small core team, and the surface area is enormous. APIs go down. Endpoints change. New free APIs launch every week. The gap between "what's in the list" and "what actually works" widens a little every day. The maintainers have said openly in issues that they need help — not heroic contributions, just steady, small ones.
The Story
Here is what the repo literally is: one large Markdown table, broken into sections, each row containing an API name, a short description, whether authentication is required, whether HTTPS is supported, and a CORS (cross-origin resource sharing — a browser security setting) status. That's it. Clean, readable, copy-pasteable.
A concrete scenario: imagine you're building a hobby project that shows random dog facts. You open the repo, jump to the Animals section, and find the Dog API listed with its URL, auth requirements, and CORS support in three seconds. You don't need to Google, you don't need a Medium post from 2019. You have your answer.
Now flip the scenario: that API shut down six months ago, but no one updated the entry. You spend twenty minutes debugging before realising the endpoint is dead. That broken entry is exactly where contributors help. Filing a pull request (a proposed change submitted for review) to remove or update a dead link takes under ten minutes and saves the next person real time.
The Python scripts in the repo handle automated validation — checking whether listed URLs respond, whether HTTPS is active, whether CORS headers are present. If you can read basic Python (the language used to write these scripts) and run a test locally, you can improve that validation layer. If you can't write code at all but you know a free API that isn't listed, that's a valid contribution too: one row, formatted correctly, submitted as a pull request.
Good first issues (GitHub's label for beginner-friendly tasks) are regularly tagged. Past examples include fixing formatting inconsistencies, adding missing HTTPS flags, and removing APIs that have moved behind a paywall. None of these require deep expertise. They require attention to detail and a willingness to follow the contribution guidelines in the repo.
The Insight
The honest reason to contribute here isn't altruism — it's that this is one of the lowest-friction repositories on GitHub to get a merged pull request on record. The contribution rules are clear, the scope of each task is tiny, and the maintainers are responsive. For a junior developer building a portfolio, a merged PR on a 427K-star repo is a real line item. For someone curious about open-source culture, this is the equivalent of a beginner climbing route: real, counts, not embarrassing.
The barrier worth naming honestly: most issue discussion happens in English, and the formatting rules are strict. If your API entry doesn't match the table style exactly, it will be sent back for revision. That's not gatekeeping — it's the only way a one-file repo at this scale stays usable. Read the contributing guide before you submit. The second barrier is time expectation: this is not a repo where you build a feature over three weekends. It rewards five-minute, focused contributions.
One thing the maintainers are genuinely short on is people who will regularly audit existing entries — not just add new ones. If you can commit to checking ten entries a month for accuracy, that's more valuable than a one-time addition of twenty new APIs.
Contributing to public-apis won't make you famous, but it will make the internet marginally more accurate — and it will leave a clean, visible record that you showed up and did the work. If you want to find more repositories at this level of contributor-friendliness, we keep curating them at teum.io/stories.
한국어 요약
public-apis/public-apis는 1,400개 이상의 무료 API를 모아놓은 GitHub 레포로, 별이 42만 개가 넘는다. 메인테이너 팀이 소규모라 링크 검증, 항목 추가·수정 같은 작은 기여가 실질적으로 필요한 상황이다. 코드를 몰라도 괜찮고, PR 하나로 포트폴리오에 실제 기여 이력을 남길 수 있다. 기여 규칙이 엄격하니 컨트리뷰팅 가이드를 먼저 읽는 게 핵심이다. 비슷한 레포는 teum.io/stories에서 계속 소개할 예정이다.
A merged PR on a 427K-star repo is a real portfolio line item.