Skip to main content

Authorization

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

Baton

Prerequisites​

To connect Nexla to Baton, you need an active Baton account and a Baton API key. The Baton API uses API key authentication — your key is passed as a Bearer token in the Authorization header of each request. You also need your Baton company identifier, which is the company-specific subdomain used to construct the base URL for all API calls (in the format https://app.hellobaton.com/api/{company}/).

Obtain Your Baton API Key​

Baton API keys are generated from within your Baton account. You will need sufficient account permissions to access the API settings area.

  1. Sign in to your Baton account at app.hellobaton.com.

  2. Navigate to your account or organization settings. Depending on your Baton account configuration, this may be accessible from your user profile menu in the upper-right corner or from a Settings option in the main navigation.

  3. Locate the API or Integrations section within Settings.

  4. Generate a new API key by clicking the appropriate Create or Generate button.

  5. Copy the generated API key immediately and store it in a secure location. This value is used to authenticate all API requests from Nexla to Baton.

For complete information about Baton API authentication and credential management, refer to the Baton API documentation. Your API key provides programmatic access to your Baton account data — treat it like a password and avoid sharing it with unauthorized parties.

Identify Your Baton Company Identifier​

The Baton API uses a company-specific identifier to scope all API requests. This identifier is the name of your company instance in Baton, used to form the base URL for API calls.

  • Your company identifier is typically the short name or slug associated with your Baton organization. It appears in the URL when you are logged into Baton — for example, in a URL like https://app.hellobaton.com/mycompany/, the company identifier would be mycompany.

  • Contact your Baton account administrator if you are unsure of your organization's company identifier.

Create a Baton Credential​

  • To create a new Baton 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 Configuration​

  1. Enter your Baton API key in the API Key field. This is the key generated from your Baton account settings (see Obtain Your Baton API Key above). Nexla will send this value as a Bearer token in the Authorization header of all API requests to Baton.
Important

The API key field is a password-type field — the value will be masked after entry. Ensure you have copied the correct API key from your Baton account before saving the credential.

Company Configuration​

  1. Enter your Baton company identifier in the Company field. This is the company-specific name used to construct the base API URL for your Baton instance (see Identify Your Baton Company Identifier above). The Baton API will use this value to scope all requests to your organization's data.

The company identifier is case-sensitive and must match exactly the value associated with your Baton organization. An incorrect company identifier will result in authentication or endpoint errors when Nexla attempts to connect to Baton.

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.