GitHub has an extensive API which Unito uses to sync issues. Learn more.
What this article covers:
-
Why Unito accesses the GitHub APIs
-
The OAuth Endpoint Unito accesses
-
The API Endpoints Unito uses
-
The API Endpoints Unito does not use
Though Unito uses GitHub's extensive API to sync issues, we request the minimum access possible. Unfortunately GitHub does not offer a permission scope for just issues. In the spirit of transparency, and in case you wanted to place a proxy or API gateway in front or your GitHub enterprise (support coming soon), here is the list of API endpoints we use, and don't use.
Note in particular, we never access source code!
OAuth Endpoint
This endpoint is used to get an access token after you authorize Unito. This endpoint is not actually part of the API, so we list it here separately.
or
API Endpoints Used
Notes:
-
URLs under https://api.github.com or https://your-GHE-domain/api/
-
Only HTTP HEAD and GET verbs are used, unless specified otherwise
-
* indicates any URL-compatible string EXCLUDING a slash (/)
-
** indicates any URL-compatible string, including any number of slashes (/)
API Endpoints NOT Used
This list is provided for convenience and may not be complete
What's next?
Learn how to sync multiple GitHub repositories.
Learn how to sync GitHub with Jira.
Not a Unito user? Try Unito for two weeks free!
Already a user? Sign in here!