Skip to main content

Authorization

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

FullStory

Prerequisites​

To connect Nexla to FullStory, you need a FullStory account with permission to create API keys. FullStory API keys are available to Standard, Architect, and Admin users on all FullStory plans. Architect-level keys — required for reading and exporting user data — are available on Enterprise plans only.

FullStory API Key Permission Levels​

FullStory API keys use three permission levels that form a hierarchy: Standard → Architect → Admin. A key at a higher level can access all endpoints available to lower levels. Choose the permission level appropriate for your Nexla integration:

  • Standard — Allows sending data into FullStory (events and users), listing sessions, viewing recording settings, and managing async operations. Use this level when Nexla will only write data to FullStory.

  • Architect — Includes all Standard permissions, plus the ability to view, export, and delete user data, access privacy settings, search exports, and manage raw data exports. Use this level when Nexla will read or export data from FullStory. Available on Enterprise plans only.

  • Admin — Includes all Architect permissions, plus the ability to create, update, and delete element block rules that control what FullStory captures. Use this level only when required for privacy-critical configuration.

FullStory recommends using a separate API key for each integration or tool, and assigning only the minimum permission level required for the intended use. For details, see Managing API Keys in the FullStory Help Center.

Generate a FullStory API Key​

  1. Sign in to your FullStory account at app.fullstory.com.

  2. Navigate to Settings (gear icon) in the left navigation.

  3. Under the Integrations section, select API Keys.

  4. Click the Create key button in the upper-right corner of the API Keys list.

  5. Enter a descriptive name for the key in the Key name field — for example, Nexla Integration.

  6. Select the appropriate permission level from the Permission level dropdown (Standard, Architect, or Admin) based on your intended use.

  7. Click Create key to generate the API key.

Important

A modal will appear displaying the new key's value immediately after creation. You must copy the key value at this time — FullStory will not display the key value again after you close the modal. Store the key in a secure password manager or secrets management system.

  1. Copy the API key value and keep it available for the next section.

If you need to revoke or regenerate a key at any time, return to Settings > Integrations > API Keys, locate the key in the list, and select the revoke option. After revoking a key, any integrations using that key will stop working until they are updated with a new key.

Create a FullStory Credential​

  • To create a new FullStory 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.

API Key​

  1. Enter the FullStory API key you generated in the prerequisite steps above into the API Key field. This key authenticates all requests Nexla makes to the FullStory Server API and should be treated with the same security as a password.

    The FullStory API key is sent in the Authorization HTTP header as Basic {YOUR_API_KEY} for every API request. Nexla handles this header formatting automatically — you only need to provide the raw API key value.

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.