Support

How to Authenticate

View as Markdown

Step-by-step instructions for generating a Personal Access Token (PAT) or classic developer key to authenticate GoDaddy API calls.

Overview

GoDaddy API uses authentication to ensure that only authorized users can access the API. The two authentication methods are using a Personal Access Token (PAT) or the Classic Developer Key. All v3 Domains APIs require a PAT. Some APIs accept only the classic developer key. The following article provides step-by-step instructions for generating a PAT or classic developer key to authenticate GoDaddy API calls. Go to About Authentication to learn more about the different authentication methods and their scopes.

Generate, use, and manage tokens

The following sections explain how to generate, use, and manage PATs or classic developer keys to authenticate GoDaddy API calls.

Generate a token

The following steps explain how to generate a PAT to authenticate GoDaddy API calls.

  1. Sign in to the Personal Access Token page.
  2. Select Generate Token.
  3. On the Generate Personal Access Token page, complete the following fields:
    FieldDescriptionNote
    Token NameName for the token.
    Expires AfterHow long the token stays valid: 7, 30, 60, or 90 days, or 1 year.
    PermissionsScopes for the token.Go to PAT scopes to see the available scopes.
  4. Select Create Token.

Store your token securely

After generating the token, it displays once. You can't retrieve it again from the Personal Access Token page and you should store it in secure storage immediately. Don't commit it to source control, check it into a repo, or paste it into chat.

  1. In the Personal Access Token Created dialog, select Copy Token.
  2. Save the token in a password manager, secrets manager, or your application's secure credential store.
  3. Load the token at runtime when you need it as a local script in a shell session or as a secret in a secrets store or CI/CD environment variable:
export GODADDY_PAT="<GODADDY_PAT>"

Don't treat export as storage

export GODADDY_PAT="<GODADDY_PAT>" makes the token available to the current shell. It is not a secure place to keep credentials long term. Store the value in a secrets manager first, then export or inject it only when running a command or starting your app.

Use a token

The following steps explain how to use a PAT to authenticate GoDaddy API calls.

  • Add the header to every request:
Authorization: Bearer ${GODADDY_PAT}

Clone a token

The following steps explain how to clone an existing PAT.

  1. Sign in to the Personal Access Token page.
  2. Next to the token you want to clone, select the actions menu (⋯), then select Clone.
  3. On the Generate Personal Access Token page, change the selected scopes if needed.
  4. Select Create Token.
  5. Save the new token in a password manager, secrets manager, or your application's secure credential store.

Revoke a token

The following steps explain how to revoke a PAT.

  1. Sign in to the Personal Access Token page.
  2. Next to the token you want to revoke, select the actions menu (⋯), then select Revoke.
  3. In the Revoke token? dialog, select Revoke Token.

Agent & Automation Notes

PermissionsAny account
ScopesNot applicable: this page is credential setup
Rate limitPAT creation: interactive UI, not rate-limited.
IdempotentYes
DestructiveNo
On failurePAT reveals once at creation. If lost, revoke and regenerate. Revocation is instant across all edges.

Last updated on

How is this guide?

On this page