Here are some quick links to get you up and running with the GraphQL API:
For more information about GitHub's APIs, see "About GitHub's APIs."
The GraphQL data query language is:
Strongly typed. The schema defines an API's type system and all object relationships.
Introspective. A client can query the schema for details about the schema.
An application layer. GraphQL is not a storage model or a database query language. The graph refers to graph structures defined in the schema, where nodes define objects and edges define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored.
GitHub chose GraphQL because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and only the data you want—is a powerful advantage over traditional REST API endpoints. GraphQL lets you replace multiple REST requests with a single call to fetch the data you specify.
For more details about why GitHub invested in GraphQL, see the original announcement blog post.
The docs in the sidebar are generated from the GitHub GraphQL schema. All calls are validated and executed against the schema. Use these docs to find out what data you can call:
You can access this same content via the Explorer Docs sidebar. Note that you may need to rely on both the docs and the schema validation to successfully call the GraphQL API.
For other information, such as authentication and rate limit details, check out the guides.
有关 GitHub Apps、OAuth Apps 和 API 开发的问题、漏洞报告和讨论，请访问 APIs and Integrations discussions on GitHub Community。 该讨论由 GitHub 工作人员管理和维护，但不能保证发布到论坛的问题都会得到 GitHub 工作人员的回复。
请考虑使用联系人表单直接联系 GitHub 支持：
- 要保证得到 GitHub Enterprise Server 工作人员的回应
- 关于 GitHub Enterprise Server 产品的反馈