When someone codes a connection to GitHub, they lose hours reading docs and guessing what each call accepts. This repository is the official OpenAPI description of GitHub's entire REST API. It is a file that both people and programs read to learn what can be requested and how.
Who this is NOT for
If your business does not use GitHub, or uses it but nobody on your team writes code that talks to its API, this is useless to you. It is not an app, it has no screens or buttons, and it automates nothing on its own. If you want to connect apps without coding, look at n8n or Activepieces and skip this repo.
We list it out of honesty: it has stars and sounds useful, but it is raw material for developers, not a tool for your business. For people who do code, its value is being the official source. GitHub says it uses it to validate requests to its own API and that it updates automatically (the latest change is from today). That is why it accepts no outside changes: if you find an error, you open an issue. The typical mistake is treating the `descriptions-next` folder as the real one. It is version 3.1 and may have breaking changes. The stable one is `descriptions`. The README also admits some headers are missing and that not every possible path for each operation is documented.
Your first step
Send the repo link to whoever codes your integrations and tell them to work from the descriptions folder in bundled format, which is the stable one GitHub recommends.
The GitHub's REST API OpenAPI Description implementation guide
The project belongs to GitHub and it is free: the link beside asks for nothing. The guide to set it up without getting lost is ours: step by step, common mistakes and a checklist. Leave your email and we will send it.
No spam. Unsubscribe anytime.