Skip to main content

Authorization

Follow this guide to create a new Guru credential that will allow Nexla to authenticate to and exchange data with your Guru account.
guru_api_auth.png

Guru

Prerequisites​

Before creating a Guru credential in Nexla, you will need an API token from your Guru account. Guru uses HTTP Basic Authentication for API access, where your Guru account email address serves as the username and an API token serves as the password.

Guru supports two types of API tokens, each suited to different use cases:

  • User Token — Provides full read and write access to the Guru API based on the permissions of the user who generated the token. Use a User Token when you need to read from or write to your Guru knowledge base via Nexla.

  • Collection Token — Provides read-only access to the content in a single, specific Collection. Use a Collection Token when you only need to retrieve knowledge from one Collection and prefer a scoped, read-only credential.

Only Guru Admins can generate API tokens. Admins can generate tokens for themselves or on behalf of other users in the organization.

Generate a User Token​

  1. Log in to your Guru account at https://app.getguru.com.

  2. Navigate to the Manage menu in the top navigation bar.

  3. Select Apps & Integrations from the menu.

  4. Click the API Access tab.

  5. Click Generate User Token.

  6. Enter a name to identify this token (for example, "Nexla Integration"), then click Generate Token.

  7. Copy the generated token immediately and store it in a secure location. The token will not be displayed again after you leave this page.

Important

The User Token is displayed only once. If you navigate away from the page before copying the token, you will need to generate a new one. Store the token securely — treat it like a password, as it grants full API access on behalf of the associated user.

Generate a Collection Token​

  1. Log in to your Guru account at https://app.getguru.com.

  2. Navigate to the Manage menu in the top navigation bar.

  3. Select Apps & Integrations from the menu.

  4. Click the API Access tab.

  5. Click Generate a New Collection Token.

  6. From the dropdown list, select the Collection that this token should grant access to.

  7. Click Generate Token.

  8. Copy the generated token immediately and store it in a secure location. Collection Tokens are also shown only once.

Collection Tokens provide read-only access limited to a single Collection. For flows that require writing data to Guru or accessing content across multiple Collections, use a User Token instead.

For complete information about Guru API authentication, refer to the Guru Developer Network documentation.

Create a Guru Credential​

  • To create a new Guru credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. 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 to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

Authentication Settings​

  1. Enter your Guru account email address in the Username field. This is the email address associated with the Guru account that owns the API token.

  2. Enter the API token you generated in the Password field. Depending on your use case, this will be either a User Token (for read/write access) or a Collection Token (for read-only access to a single Collection).

    The Guru API uses HTTP Basic Authentication, where your email address is the username and the API token is the password. Nexla handles the encoding and transmission of these credentials securely.

Save the Credential​

  1. 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.

  2. 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.