- Help Center
- GitHub Integration Docs
- GitHub Connector Troubleshooting
-
Get Started With Unito
-
Using Unito
-
Items in Sync, Account Management, and Billing
-
Troubleshooting and FAQs
-
Data Privacy & Security
-
Integration Documentation
- Airtable
- Azure DevOps
- Basecamp
- Bitbucket
- ClickUp
- Confluence
- Eloqua
- Favro
- GitLab
- HubSpot
- Intercom
- Jotform
- Mailchimp
- MeisterTask
- Microsoft Excel
- Microsoft Outlook
- Miro
- monday.com
- Notion
- Pipedrive
- PostgreSQL
- Slack
- Snowflake
- Stripe
- SurveyMonkey
- Teamwork
- Typeform
- Xero
- Zendesk
- Zoho Projects
- MySQL
-
Atlassian Jira Integration Docs
-
Trello Power-Up Docs
-
2-Way ServiceNow Integration
-
Asana Integration Docs
-
Google Integration Docs
-
Salesforce Integration Docs
-
Wrike Integration Docs
-
Azure DevOps Integration Docs
-
Smartsheet Integration Docs
-
GitHub Integration Docs
Which GitHub APIs Are Used?
GitHub has an extensive API which Unito uses to sync issues. Learn more.
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 of your GitHub Server, 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.
API Endpoints Used
-
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 (/)