Skip to main content
GitHub Authentication Guide

How to authenticate GitHub for use with Tines

Updated over a week ago

GitHub, Inc. is an Internet hosting service for software development and version control using Git. It provides the distributed version control of Git plus access control, bug tracking, software feature requests, task management, continuous integration, and wikis for every project.

Firstly, create a credential in Tines,

  1. Login to your Tines tenant

  2. Navigate to the team that will be using the API and click "Credential"

  3. Click "+ New Credential" and select "OAuth 2.0"

  4. Copy the "Callback URL"

Next, create a GitHub OAuth App

  1. Navigate to and sign in. If you don't have an existing account, click on "Sign up"

  2. Click on your profile in the top right-hand corner and select "Settings"

  3. Click on "Developer Settings" at the bottom of the sidebar on the left-hand side.

  4. Click on "OAuth Apps" and then "Register a new application"

  5. Fill out the application details, using the "Callback URL" copied from your Tines credential for "Authorization callback URL". Once completed, click "Register application"

  6. Click "Generate a new client secret" and copy the secret generated, along with the "Client ID"

  7. Click "Update the application"

Lastly, continue creating the credential in Tines

  1. Input the values for the GitHub credential

    1. Name: Required

    2. Description: Optional

    3. Client ID: "Client ID" copied earlier

    4. Client secret: "Client secret" copied earlier

    5. Scope: repo user

    6. OAuth Provider: Manual

    7. Grant type: Authorization code

    8. OAuth authorization request URL:

    9. PKCE challenge method: None

    10. OAuth token URL:

  2. Optional

    1. Domains: Ensure this credential can only be used when making HTTP requests to specific domains

    2. Access: What other teams can also use the API

  3. When you click "Save", you may be asked to "Authorize Tines"

For more on creating credentials in Tines, click here.

You can find a selection of GitHub stories in the story library

Did this answer your question?