Quick start¶
The AtomGit API gives you programmatic access to resources on AtomGit. This guide explains how to use it: valid API requests, authentication, status codes, pagination, path parameters, and more.
For AI agents and automation¶
If you are an AI agent or an automation tool, read the following resources in order instead of parsing the rendered HTML page by page:
- AtomGit API index and summary (llms.txt): an index of the name, description, and documentation link for every endpoint. Read this file first when you are looking for an endpoint.
- AtomGit API JSON specification: the complete machine-readable API specification (OpenAPI 3.0.3). Read this file when you build request parameters or integrate the API into a tool.
- AtomGit API Markdown version of the same specification: the complete machine-readable specification in Markdown. Use this URL when you want to feed the specification to an agent.
API hosts and multiple domains¶
The AtomGit API is served from several domains with identical functionality and endpoints, so you can pick the one closest to your network:
| Host | Description |
|---|---|
https://api.atomgit.com |
Official AtomGit API domain |
https://api.gitcode.com |
GitCode domain; API behavior is identical to the AtomGit domain |
Requests to both hosts share the same paths, parameters, authentication, and response structure, so you can switch hosts without changing any code. For example, the following two requests are equivalent:
Note: examples in this documentation use
https://api.atomgit.com. If you use the GitCode domain, only the host part changes. We recommend storing the host in an environment variable so it is easy to switch and migrate.
Making your first request¶
- Create a token on the personal access token page.
-
Save the token as an environment variable:
-
Look up a public user profile. This endpoint does not require authentication:
-
List the open issues in a repository:
Markdown source: View on AtomGit·Content from the open-source project gitcode-dev/atomgit-api-doc