Authorization

Bugherd
Prerequisites
Before creating a BugHerd credential, you need to obtain authentication credentials from your BugHerd account. BugHerd supports Basic Authentication using either a username and password combination or a personal API key.
To use BugHerd with Nexla, you need:
- Access to your BugHerd account
- A BugHerd account with appropriate permissions to access the projects and resources you want to work with
- Either your username and password, or a personal API key
Personal API keys can be created in your BugHerd account settings. API keys provide a secure alternative to using passwords and can be revoked independently if needed. For detailed information about BugHerd authentication and API key creation, refer to the BugHerd API documentation.
Create a BugHerd Credential
- To create a new BugHerd credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
New Credential Overlay – BugHerd

Credential Name & Description
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.
Basic Authentication Configuration
-
Enter your BugHerd username or personal API key in the Username Or API Key field. You can use either your BugHerd username or a personal API key for authentication.
-
Enter your BugHerd password in the Password field. If you are using a personal API key as the username, enter the API key value in this field as well. If you are using your username, enter your BugHerd account password. The default value is
xif not specified.Keep your authentication credentials secure and do not share them publicly. The credentials provide access to your BugHerd account and should be treated as sensitive information. Personal API keys are recommended over passwords as they can be revoked independently and provide better security.
Save the Credential
-
Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.
-
The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.