Bluetally

BlueTally is a cloud-based IT asset management platform that helps organizations track hardware, software licenses, accessories, components, consumables, and employee assignments. The BlueTally REST API enables programmatic access to create, read, update, and delete assets, employees, accessories, licenses, components, consumables, locations, audits, and activity records, supporting end-to-end asset lifecycle automation.

Power end-to-end data operations for your Bluetally API with Nexla. Our bi-directional Bluetally connector is purpose-built for Bluetally, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Bluetally or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Bluetally workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

The Bluetally connector authenticates with the BlueTally REST API using an API key passed as a Bearer token in the Authorization header. To create a Bluetally credential in Nexla, you must first generate an API key from your BlueTally account.

Generate a BlueTally API Key

1. Sign in to your BlueTally account at https://app.bluetallyapp.com.

2. Click the Profile icon in the top right corner of the screen.

3. Click the Settings link in the dropdown menu to open the account settings.

4. Click the API Keys link on the left side of the settings screen.

5. Click the Create API Key button to generate a new API key.

6. Provide a descriptive name for the key (e.g., "Nexla Integration") and confirm creation.

7. Copy the generated API key and store it in a secure location. This key will be used to authenticate Nexla with the BlueTally API.

   Important

   The API key is displayed only once at creation time. Copy and store it securely before navigating away. If the key is lost, you will need to create a new one.

For complete information about BlueTally API authentication, base URLs, rate limits (10,000 requests per hour, up to 1,000 results per request), and multi-tenant considerations, refer to the BlueTally API documentation.

Multi-Tenant Accounts

If your BlueTally account is configured for multi-tenant use, you must include the tenant_id query parameter in API requests. Several endpoint templates in this connector expose a Tenant ID field for this purpose. Identify the correct tenant ID for the data you intend to read or write before configuring endpoints that require it.

Authenticate

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. The Bluetally connector uses API key authentication. Nexla automatically sets the Authorization header to Bearer <your-api-key> for all requests to the BlueTally API. Paste the API key generated in the Prerequisites section into the API Key field. This value is stored securely and used as the Bearer token for all API calls to your BlueTally account.

   Treat your BlueTally API key as a sensitive credential. Anyone with access to the key can create, read, update, and delete records in your BlueTally account through the API.

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

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Bluetally connector tile, then select the credential that will be used to connect to the Bluetally instance, and click Next; or, create a new Bluetally credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common BlueTally endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

List Assets

Retrieves all assets from the BlueTally API. Use this endpoint to ingest your complete asset inventory—including hardware devices, equipment, and other tracked items—for reporting, analytics, or downstream syncs.

• This endpoint automatically paginates results using the BlueTally offset and limit query parameters, fetching up to 100 records per request until all assets have been retrieved.
• Records are extracted from the $.assets[*] path in the response, so each asset object becomes an individual record in the resulting Nexset.

Refer to the List Assets reference in the BlueTally API documentation for the complete list of returned fields and filter options.

Get Asset

Retrieves a single asset by its unique BlueTally ID. Use this endpoint when you need detailed information about a specific asset record.

• Enter the unique identifier of the asset in the Asset ID field. Asset IDs can be discovered by first running the List Assets endpoint or by locating the asset in the BlueTally UI.
• The response is treated as a single record using the root path $.

List Employees

Retrieves all employees from the BlueTally API. Use this endpoint to ingest your complete employee directory and assignments.

• Results are paginated automatically using offset-based paging, returning up to 100 employee records per page from the $.employees[*] path.
• No additional configuration is required beyond selecting this endpoint template.

Get Employee

Retrieves a specific employee by ID. Use this endpoint when you need detailed information about a single employee record.

• Enter the unique identifier of the employee in the Employee ID field. Employee IDs can be obtained from the List Employees endpoint or from the BlueTally UI.

List Accessories

Returns all accessories tracked in BlueTally (e.g., chargers, cables, peripherals).

• Results are paginated automatically, returning up to 100 records per page from the $.accessories[*] path.

Get Accessory

Retrieves details for a specific accessory by ID. Supports an optional tenant ID for multi-tenant accounts.

• Enter the accessory identifier in the Id field.
• If your BlueTally account is multi-tenant, enter the tenant identifier in the Tenant Id field; otherwise leave this field blank.

The tenant ID is only required for multi-tenant BlueTally accounts. Single-tenant accounts can leave this field empty.

List Components

Returns a list of all components tracked in BlueTally. Components represent parts that can be checked out to assets (e.g., RAM modules, drives).

• Results are paginated automatically, returning up to 100 records per page from the $.components[*] path.

List Consumables

Returns a list of all consumables in BlueTally (e.g., printer toner, batteries).

• Results are paginated automatically, returning up to 100 records per page from the $.consumables[*] path.

List Licenses

Returns all software license records tracked in BlueTally.

• Results are paginated automatically, returning up to 100 records per page from the $.licenses[*] path.

List Locations

Returns a list of all locations configured in BlueTally. Locations are used to organize assets by physical or logical site.

• Results are paginated automatically, returning up to 100 records per page from the $.locations[*] path.

List Products

Returns all products in BlueTally. Products represent catalog entries (make/model) that assets are created from.

• Results are paginated automatically, returning up to 100 records per page from the $.products[*] path.

Get Product

Retrieves a specific product by ID. Use this endpoint when you need detailed information about a single product catalog entry.

• Enter the unique identifier of the product in the Product ID field. Product IDs can be obtained from the List Products endpoint.

List Activity

Returns a paginated list of activity events from BlueTally with optional filtering by date range, activity type, user, employee, and related resources (assets, accessories, components, consumables, licenses). Use this endpoint to ingest audit and event data for compliance reporting or change tracking.

• All filter parameters are optional. Leave any field blank to omit that filter from the request:

  • Tenant Id — Required only for multi-tenant accounts.
  • Sort Field / Sort Order — Field name to sort by and direction (asc or desc).
  • Date From / Date To — Restrict results to a date range.
  • Activity Type / Event — Filter by activity type or specific event name.
  • User ID / User Email — Filter by the acting user.
  • Employee ID / Employee Email — Filter by employee affected.
  • Asset ID, Accessory ID, Component ID, Consumable ID, License ID — Filter by related resource.
• Records are extracted from the $.data[*] path and paginated automatically.

Combining date range filters with resource ID filters is the most efficient way to retrieve activity for a specific entity over a specific period.

List Audits

Returns a paginated list of audits from BlueTally with optional filtering by date, status, asset, location, and user. Use this endpoint to ingest scheduled and completed audit records for compliance and lifecycle reporting.

• All filter parameters are optional. Common filters include:

  • Tenant Id — Required only for multi-tenant accounts.
  • Sort / Order — Field name and direction.
  • Audit Date / Next Audit Date — Restrict by audit scheduling dates.
  • Scheduled / Completed — Filter by audit status.
  • Asset ID, Location ID, User ID — Filter by related resource.
  • Notes, Audit Status, Audit Failed Reason — Additional content filters.
• Records are extracted from the $.audits[*] path and paginated automatically.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Bluetally data sources can also be manually configured to ingest data from any valid BlueTally API endpoint not covered by the pre-built templates, including chained API calls or custom request parameters such as multi-tenant tenant_id values. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

The base URL for the BlueTally API is https://app.bluetallyapp.com/api/v1; append the resource path (e.g., /assets, /employees, /licenses). BlueTally list endpoints wrap their results in a top-level array named after the resource type, so set the path to data accordingly (for example, $.assets[*] or $.employees[*]). For multi-tenant accounts, include the tenant_id query parameter in the URL. Date/time macros in the API URL are useful for the List Activity and List Audits endpoints, which accept date_from, date_to, and audit_date filters. You do not need to add the Authorization header—Nexla automatically attaches the Bearer token from your selected credential to every request.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Bluetally data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the Bluetally destination, and select the Send to Destination option from the menu. Select the Bluetally connector from the list of available destination connectors, then select the credential that will be used to connect to the Bluetally organization, and click Next; or, create a new Bluetally credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common BlueTally endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Create Asset

Creates a new asset record in BlueTally. Send a Nexset whose records contain the asset attributes (e.g., name, serial number, model, status, location) you want to track.

• The Nexset record is serialized as JSON and posted to POST /api/v1/assets with content type application/json.
• Map your incoming data attributes to the field names expected by the BlueTally Create Asset API. Refer to the BlueTally API Reference for the complete schema.

Update Asset

Updates an existing asset by ID. Use this endpoint to push attribute changes (status, location, custom fields, etc.) from upstream systems into BlueTally.

• Enter the unique identifier of the asset to update in the Asset ID field. This is typically mapped from an upstream Nexset attribute.
• The Nexset record is sent as a JSON body to PUT /api/v1/assets/{id}.

See the Update Asset reference for the list of updatable fields and any required attributes.

Delete Asset

Deletes or retires an asset by ID. The request body is empty—only the asset identifier is required.

• Enter the unique identifier of the asset to delete in the Asset ID field.
• The action is performed via DELETE /api/v1/assets/{id}.

Deleting an asset in BlueTally is typically irreversible. Verify the source data before activating this destination.

Create Employee

Creates a new employee record in BlueTally. Use this endpoint to onboard employees from an HRIS or directory system.

• The Nexset record is serialized as JSON and posted to POST /api/v1/employees.

Update Employee

Updates an existing employee by ID. Use this endpoint to synchronize employee attribute changes from authoritative HR systems.

• Enter the unique identifier of the employee in the Employee ID field.
• The Nexset record is sent as a JSON body to PUT /api/v1/employees/{id}.

Delete Employee

Deletes/offboards an employee by ID. The request body is empty—only the employee identifier is required.

• Enter the unique identifier of the employee in the Employee ID field.

Create Accessory

Creates a new accessory record in BlueTally (e.g., cables, chargers, peripherals).

• The Nexset record is serialized as JSON and posted to POST /api/v1/accessories.

Update Accessory

Updates an existing accessory with new details and attributes.

• Enter the accessory identifier in the Id field.
• The Nexset record is sent as a JSON body to PUT /api/v1/accessories/{id}.

Delete Accessory

Deletes a specific accessory by ID. Supports an optional tenant ID for multi-tenant accounts.

• Enter the accessory identifier in the Id field.
• If your BlueTally account is multi-tenant, enter the tenant identifier in the Tenant Id field; otherwise leave this field blank.

Create Component

Creates a new component record in BlueTally. Components represent parts (e.g., RAM modules, drives) that can be checked out to assets.

• The Nexset record is serialized as JSON and posted to POST /api/v1/components.

Create Accessory (alias) — Create License

Creates a new software license record in BlueTally.

• The Nexset record is serialized as JSON and posted to POST /api/v1/licenses.

Checkout Asset

Checks out an asset to an employee or location. Use this endpoint to record asset assignments in BlueTally.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/asset. The body should reference the asset and the target employee or location per the BlueTally API specification.

Checkin Asset

Checks an asset back in from an employee or location, ending the current assignment.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkin/asset.

Checkout Accessory

Checks out an accessory to an employee.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/accessory.

Checkin Accessory

Checks an accessory back in from an employee.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkin/accessory.

Checkout Component

Checks out a component to an asset (e.g., installing a RAM module into a tracked device).

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/component.

Checkout Consumable

Checks out a consumable to an employee.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/consumable.

Checkout License

Checks out a license to an employee or asset.

• The Nexset record is serialized as JSON and posted to POST /api/v1/checkout/license.

Refer to the BlueTally API Reference for the request body schema expected by each checkout/checkin endpoint.

Manual configuration

Bluetally destinations can also be manually configured to send data to any valid BlueTally API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

The base URL for the BlueTally API is https://app.bluetallyapp.com/api/v1, and the API expects the application/json content format. For update/upsert operations, include the ID of the object to be updated at the end of the URL (e.g., https://app.bluetallyapp.com/api/v1/assets/12345); for multi-tenant accounts, append the tenant_id query parameter. You do not need to add the Authorization header—Nexla automatically attaches the Bearer token from your selected credential, and the Content-Type header is set based on the selected data format. Most BlueTally write endpoints operate on a single record per request, so verify that the target endpoint supports batched payloads before enabling record batching. You can also enable the response webhook option to capture the API response—including newly created BlueTally IDs—as a new Nexla webhook data source.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send data to the configured BlueTally endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to BlueTally until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.