{ "version": "https://jsonfeed.org/version/1", "title": "Trackunit IrisX - Change Log", "home_page_url": "https://developers.trackunit.com/changelog/", "description": "New APIs, SDK updates and platform changes.", "items": [ { "id": "https://developers.trackunit.com/changelog/2026/08/03/iris-app-nx-23-upgrade/", "content_html": "

In this version of our Iris App SDK, we have upgraded NX to v23.1.0. This release also moves Iris App builds onto Vite 8.

\n

Make sure to upgrade your extensions to the latest version of NX.

\n
npx nx migrate 23.1.0
npx nx migrate --run-migrations
\n

Please refer to Maintaining Your Application for more information.

\n

Also included: Vite 8​

\n

@trackunit/iris-app-sdk-vite now depends on Vite 8.1.x (Rolldown-based bundler). Most Iris Apps need no Vite config changes after updating @trackunit/* packages.

\n

If you customized production minification with build.minify: \"esbuild\", switch to Vite 8's default (\"oxc\"), or install esbuild separately — generated Iris App workspaces do not include esbuild.

\n

Module Federation continues to work via @module-federation/vite 1.18+, which supports Vite 8.

", "url": "https://developers.trackunit.com/changelog/2026/08/03/iris-app-nx-23-upgrade/", "title": "trackunit/iris-app — NX upgraded to v23.1.0", "summary": "In this version of our Iris App SDK, we have upgraded NX to v23.1.0. This release also moves Iris App builds onto Vite 8.", "date_modified": "2026-08-03T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/07/27/webpack-rspack-removed/", "content_html": "

The @trackunit/iris-app-sdk-webpack, @trackunit/iris-app-sdk-rspack, and @trackunit/iris-app-webpack-plugin packages have been removed. Vite (@trackunit/iris-app-sdk-vite) is now the only supported build system for Iris Apps.

\n

This follows the deprecation notice published in June. If your Iris App was still using the Webpack or Rspack executors, it will no longer build — see the Vite migration guide to switch over.

\n

What changed​

\n\n

Action required​

\n

If you haven't migrated yet, follow the Vite migration guide before updating your @trackunit/* dependencies, since the old executors are no longer published as working packages.

\n

If you're unsure whether your app is affected, check your project.json for @trackunit/iris-app-sdk-webpack:* or @trackunit/iris-app-sdk-rspack:* executors.

", "url": "https://developers.trackunit.com/changelog/2026/07/27/webpack-rspack-removed/", "title": "Webpack & Rspack SDK build executors have been removed", "summary": "The @trackunit/iris-app-sdk-webpack, @trackunit/iris-app-sdk-rspack, and @trackunit/iris-app-webpack-plugin packages have been removed. Vite (@trackunit/iris-app-sdk-vite) is now the only supported build system for Iris Apps.", "date_modified": "2026-07-27T00:00:00.000Z", "tags": [ "Removed" ] }, { "id": "https://developers.trackunit.com/changelog/2026/06/26/device-health-issues-api-v1/", "content_html": "

The Device Health Issues API is now generally available. The endpoints have been promoted from v1beta1 to v1, and the API is no longer marked as beta.

\n

Below is a list of all available REST endpoints:

\n

Issue API​

\n
\n

➕ GET: /v1/assets/{assetId}/issues

\n
\n

Get issues by asset

\n
\n

➕ GET: /v1/issues

\n
\n

Get issues

\n
\n

➕ GET: /v1/issues/{issueId}

\n
\n

Get issue by id

\n

Breaking changes

\n
\n

⚠️ The v1beta1 endpoints have been replaced by v1. Update any integrations to use the /v1/... paths.

\n
\n
\n

⚠️ The issue type LOW_DEVICE_BATTERY_VOLTAGE has been renamed to LOW_DEVICE_BATTERY. Update any filtering or handling that relies on this value.

\n
", "url": "https://developers.trackunit.com/changelog/2026/06/26/device-health-issues-api-v1/", "title": "Device Health Issues API v1", "summary": "The Device Health Issues API is now generally available. The endpoints have been promoted from v1beta1 to v1, and the API is no longer marked as beta.", "date_modified": "2026-06-26T00:00:00.000Z", "tags": [ "Improved", "Removed" ] }, { "id": "https://developers.trackunit.com/changelog/2026/06/25/webpack-rspack-deprecation/", "content_html": "

The @trackunit/iris-app-sdk-webpack and @trackunit/iris-app-sdk-rspack build executors are deprecated and will be removed in the coming months. Vite is the supported path forward — migrate your Iris app to the Vite executor.

\n

We are consolidating the Iris App SDK build tooling on Vite (@trackunit/iris-app-sdk-vite) so we can focus our effort on a single, well-supported bundler.

\n

What this means​

\n\n

Action required​

\n

Migrate your Iris app to the Vite executor. See the Vite migration guide.

", "url": "https://developers.trackunit.com/changelog/2026/06/25/webpack-rspack-deprecation/", "title": "Webpack & Rspack SDK build executors are being removed — migrate to Vite", "summary": "The @trackunit/iris-app-sdk-webpack and @trackunit/iris-app-sdk-rspack build executors are deprecated and will be removed in the coming months. Vite is the supported path forward — migrate your Iris app to the Vite executor.", "date_modified": "2026-06-25T00:00:00.000Z", "tags": [ "Removed" ] }, { "id": "https://developers.trackunit.com/changelog/2026/06/01/telematics-device-configuration-job-rollback/", "content_html": "

The Telematics Device API now lets you roll back a previously executed configuration job. Rollback creates new configuration jobs that restore each device to the configuration it had before the original job ran.

\n

Devices that have had their configuration changed since the original job (manually, by another job, or by automation) are excluded from rollback so the rollback never silently overwrites a newer change. A rollback request can produce more than one rollback job because devices are grouped by the previous configuration they shared.

\n

Today, rollback is supported for CAN profile, Modbus profile, and Operating Mode changes. Other configurations the original job touched are excluded from the rollback's desired state — additional configurations will be announced as they become available.

\n
\n

➕ POST: /v2/configuration-jobs/{id}/rollbacks

\n
\n

Rollback a configuration job

", "url": "https://developers.trackunit.com/changelog/2026/06/01/telematics-device-configuration-job-rollback/", "title": "Telematics Device API: rollback a configuration job", "summary": "The Telematics Device API now lets you roll back a previously executed configuration job. Rollback creates new configuration jobs that restore each device to the configuration it had before the original job ran.", "date_modified": "2026-06-01T00:00:00.000Z", "tags": [ "Added" ] }, { "id": "https://developers.trackunit.com/changelog/2026/05/13/react-components-v2-accessibility/", "content_html": "

@trackunit/react-components and @trackunit/react-form-components include breaking accessibility, tooltip, and layout updates for component consumers. These changes were made to improve accessibility compliance and create more consistent tooltip and labeling behavior across components

\n

Breaking Changes​

\n\n

Codemods​

\n

This release ships automated codemods for breaking changes in @trackunit/react-components@2.0.0 and @trackunit/react-form-components@2.0.0, orchestrated by the @trackunit/migrations coordinator (modeled after nx migrate).

\n

Running the codemods​

\n

Run the two-step flow from your project root:

\n
    \n
  1. Bump @trackunit/* versions in package.json and collect pending migrations into trackunit-migrations.json\n\n
    2. \n
  2. Review trackunit-migrations.json, then execute the pending migrations\n\n
    3. \n
\n

Previously-applied migrations are tracked in trackunit-migrations.json and will not re-run.

\n

Included migrations

\n

@trackunit/react-components@2.0.0

\n\n

@trackunit/react-form-components@2.0.0

\n", "url": "https://developers.trackunit.com/changelog/2026/05/13/react-components-v2-accessibility/", "title": "Breaking: React component accessibility and tooltip updates", "summary": "@trackunit/react-components and @trackunit/react-form-components include breaking accessibility, tooltip, and layout updates for component consumers. These changes were made to improve accessibility compliance and create more consistent tooltip and labeling behavior across components", "date_modified": "2026-05-13T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/05/12/datefield-locale-picker-behavior/", "content_html": "

DateField in @trackunit/react-form-components now displays, parses, and hints dates using the user's regional locale while continuing to emit canonical YYYY-MM-DD values to consumers.

\n

What changed​

\n

DateField now uses the browser's region-qualified locale, such as en-GB, en-US, or da-DK, for visible date formatting and placeholders. This means users see date formats that match their regional preference, for example dd/mm/yyyy in the United Kingdom and mm/dd/yyyy in the United States.

\n

Change and blur events still expose canonical date-only values through event.target.value, so existing integrations can continue storing and sending YYYY-MM-DD values.

\n

New DateField options​

\n

locale​

\n

Override the locale for a specific field when a fixed regional format is required.

\n
<DateField label=\"Start date\" locale=\"en-GB\" />
\n

openOnFocus​

\n

Open the date picker automatically when the input receives focus, for example when users tab through a form.

\n
<DateField label=\"Start date\" openOnFocus />
\n

onPickerClose​

\n

Run logic when the calendar picker closes, without waiting for the input itself to blur. The callback receives the canonical value and a close reason: apply, clear, cancel, or outside.

\n
<DateField
  label=\"Start date\"
  onPickerClose={(event, reason) => {
    if (reason === \"cancel\") return;
    validateDate(event.target.value);
  }}
/>
\n

Picker accessibility​

\n

The DateField calendar picker has improved focus handling and keyboard navigation. Keyboard users can move between dates with arrow keys and commit the focused date from the picker.

\n

Popover focus support​

\n

PopoverContent in @trackunit/react-components now supports an initialFocus prop for cases where popover content should receive focus when opened.

", "url": "https://developers.trackunit.com/changelog/2026/05/12/datefield-locale-picker-behavior/", "title": "Improved: DateField locale formatting and picker behavior", "summary": "DateField in @trackunit/react-form-components now displays, parses, and hints dates using the user's regional locale while continuing to emit canonical YYYY-MM-DD values to consumers.", "date_modified": "2026-05-12T00:00:00.000Z", "tags": [ "Improved", "Fixed" ] }, { "id": "https://developers.trackunit.com/changelog/2026/05/06/aemp-iso-faults-accept-language/", "content_html": "

The AEMP ISO Diagnostic Trouble Codes time-series endpoint now honors the Accept-Language request header when enriching fault codes with descriptions.

\n

When an Accept-Language header is provided, the language is threaded through to the fault interpretation lookup, so the returned CodeDescription is localized to the caller's preferred language (for example, Accept-Language: da-DK,da;q=0.9,en;q=0.8 returns Danish descriptions) — but only if a translation for that language actually exists for the given fault code.

\n

If no translation exists for the requested language — or if the header is omitted — the response falls back to the fault code's default description (typically English). The set of available languages depends on what the OEM provides and varies by manufacturer; common languages include English (en), German (de), French (fr), Italian (it), Spanish (es), Dutch (nl), Polish (pl), and Japanese (ja).

\n
\n

📝 GET: /15143/-3/Fleet/Equipment/ID/{oemISOIdentifier}/Faults/{startDate}/{endDate}/{pageNumber}

\n
\n

Get diagnostic trouble codes time-series, with fault descriptions localized via the Accept-Language header.

", "url": "https://developers.trackunit.com/changelog/2026/05/06/aemp-iso-faults-accept-language/", "title": "AEMP ISO Faults: localized fault descriptions via Accept-Language", "summary": "The AEMP ISO Diagnostic Trouble Codes time-series endpoint now honors the Accept-Language request header when enriching fault codes with descriptions.", "date_modified": "2026-05-06T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/04/20/modal-sheet-mode/", "content_html": "

useModal in @trackunit/react-modal has been updated with sheet mode support and container scoping. Modals can now automatically adapt to a sheet presentation when rendered inside a narrow container.

\n

Changes to useModal​

\n

New return values​

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
NameTypeDescription
mode\"card\" | \"sheet\"Current presentation mode
dismissfunctionProgrammatically dismiss with options
onCloseCompletefunctionCallback fired after close animation finishes
containerelementThe scoping container element
stackarrayModal stack state
\n

Removed return values​

\n\n

New prop: container​

\n

Pass a container element to useModal to scope the modal to that element. When the container's width is less than 480 px, the modal automatically switches to sheet mode.

\n

Updated: ModalDismissOptions​

\n

ModalDismissOptions now extends the shared DismissOptions type from @trackunit/react-components, aligning dismiss behaviour across overlay components.

", "url": "https://developers.trackunit.com/changelog/2026/04/20/modal-sheet-mode/", "title": "Improved: useModal now supports sheet mode and container scoping", "summary": "useModal in @trackunit/react-modal has been updated with sheet mode support and container scoping. Modals can now automatically adapt to a sheet presentation when rendered inside a narrow container.", "date_modified": "2026-04-20T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/04/20/remove-swipeable-drawer/", "content_html": "

SwipeableDrawer, DrawerPuller, and useSwipeHandlers have been removed from @trackunit/react-drawer. The react-swipeable peer dependency is also gone.

\n

Migration​

\n

Replace SwipeableDrawer with the new Sheet component from @trackunit/react-components.

\n

Before:

\n
import { SwipeableDrawer } from \"@trackunit/react-drawer\";

<SwipeableDrawer open={open} onClose={() => setOpen(false)}>
  {children}
</SwipeableDrawer>
\n

After:

\n
import { Sheet, useSheet } from \"@trackunit/react-components\";

const sheet = useSheet();

<Sheet {...sheet}>
  {children}
</Sheet>
\n

Use useSheet for open/close state management instead of manual open/onClose props. See the Sheet component changelog for the full API.

", "url": "https://developers.trackunit.com/changelog/2026/04/20/remove-swipeable-drawer/", "title": "Removed: SwipeableDrawer from @trackunit/react-drawer", "summary": "SwipeableDrawer, DrawerPuller, and useSwipeHandlers have been removed from @trackunit/react-drawer. The react-swipeable peer dependency is also gone.", "date_modified": "2026-04-20T00:00:00.000Z", "tags": [ "Removed" ] }, { "id": "https://developers.trackunit.com/changelog/2026/04/20/sheet-component/", "content_html": "

A new Sheet component is now available in @trackunit/react-components. It provides a bottom-sheet UI with snap points, gesture support, and container-scoped rendering — suitable for mobile and responsive layouts.

\n

New exports​

\n

Sheet component​

\n

A bottom-sheet overlay with snap points and gesture-driven open/close/expand behaviour.

\n

useSheet hook​

\n

Manages open/close state and dismiss options for a Sheet.

\n

useSheetSnap hook​

\n

Controls the snap point of an open sheet: dock, fit, expand, or close.

\n

useOverflowBorder hook​

\n

Detects top/bottom scroll overflow in a container and applies CSS border classes — useful for indicating scrollable content inside a sheet.

\n

Shared overlay-dismissible types​

\n

The following types are now exported from @trackunit/react-components and shared across overlay components:

\n\n

Sheet-specific types and constants​

\n", "url": "https://developers.trackunit.com/changelog/2026/04/20/sheet-component/", "title": "New: Sheet component in @trackunit/react-components", "summary": "A new Sheet component is now available in @trackunit/react-components. It provides a bottom-sheet UI with snap points, gesture support, and container-scoped rendering — suitable for mobile and responsive layouts.", "date_modified": "2026-04-20T00:00:00.000Z", "tags": [ "Added" ] }, { "id": "https://developers.trackunit.com/changelog/2026/03/24/react-widgets-widget-kpi-interactive/", "content_html": "

The WidgetKPI component now supports an onClick prop, making KPI cards interactive with a hover effect, chevron indicator, and keyboard accessibility.

\n

Breaking Change​

\n

WidgetContent padding has changed for KPI widgets using the onClick prop. If your widget previously used padding=\"responsive\", you should update it to padding=\"none\" — the WidgetKPI component now handles its own padding internally.

", "url": "https://developers.trackunit.com/changelog/2026/03/24/react-widgets-widget-kpi-interactive/", "title": "trackunit/react-widgets 2.13.4 - Interactive WidgetKPI", "summary": "The WidgetKPI component now supports an onClick prop, making KPI cards interactive with a hover effect, chevron indicator, and keyboard accessibility.", "date_modified": "2026-03-24T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/02/26/migrate-from-rspack-to-vite/", "content_html": "

Iris Apps have been migrated from Rspack to Vite as the build system. Vite provides near-instant dev server startup, fast HMR using native ES modules, and optimized production builds.

\n

Affected packages:

\n\n

Old executors removed:

\n\n

Step 1: Update all Trackunit dependencies​

\n

Make sure you are on the latest Trackunit dependencies:

\n
npx npm-check-updates \"/@trackunit/\" -u
\n

Then install:

\n
npm install
npm install @trackunit/iris-app-sdk-vite -D
\n

Step 2: Update project.json​

\n

Replace the Rspack executors with the Vite equivalents.

\n

Before:

\n
{
  \"targets\": {
    \"build\": {
      \"executor\": \"@trackunit/iris-app-sdk-rspack:build\",
      \"options\": {
        \"rspackConfig\": \"apps/{app-name}/rspack.config.ts\",
        \"outputPath\": \"dist/apps/{app-name}\"
      },
      \"outputs\": [\"{options.outputPath}\"]
    },
    \"serve\": {
      \"executor\": \"@trackunit/iris-app-sdk-rspack:serve\",
      \"options\": {
        \"rspackConfig\": \"apps/{app-name}/rspack.config.ts\"
      }
    }
  }
}
\n

After:

\n
{
  \"targets\": {
    \"build\": {
      \"executor\": \"@trackunit/iris-app-sdk-vite:build\",
      \"options\": {
        \"outputPath\": \"dist/apps/{app-name}\"
      },
      \"outputs\": [\"{options.outputPath}\"]
    },
    \"serve\": {
      \"executor\": \"@trackunit/iris-app-sdk-vite:serve\",
      \"options\": {}
    }
  }
}
\n

Key changes:

\n\n

Step 3: Replace rspack.config.ts with vite.config.ts​

\n

Delete your existing rspack.config.ts file.

\n

If you had no customizations in your rspack config (i.e., it just returned the default configuration), you can skip creating a vite config entirely — it works out of the box.

\n

If you need custom configuration, create a vite.config.ts in your app root:

\n
import { defineConfig, UserConfig } from \"vite\";

export default defineConfig(async (configuration: UserConfig): Promise<UserConfig> => {
    return configuration;
});
\n

You can extend the default configuration by spreading and adding your overrides:

\n
import { defineConfig, UserConfig } from \"vite\";

export default defineConfig(async (configuration: UserConfig): Promise<UserConfig> => {
    return {
        ...configuration,
        define: {
            ...configuration.define,
            __MY_CUSTOM_FLAG__: JSON.stringify(true),
        },
    };
});
\n

Then reference it in your project.json:

\n
{
  \"serve\": {
    \"executor\": \"@trackunit/iris-app-sdk-vite:serve\",
    \"options\": {
      \"viteConfig\": \"apps/{app-name}/vite.config.ts\"
    }
  },
  \"build\": {
    \"executor\": \"@trackunit/iris-app-sdk-vite:build\",
    \"options\": {
      \"viteConfig\": \"apps/{app-name}/vite.config.ts\",
      \"outputPath\": \"dist/apps/{app-name}\"
    }
  }
}
\n

Step 4: Remove tailwind.config.js (if present)​

\n

If your app has a tailwind.config.js file, delete it. Tailwind CSS v4 is now configured automatically by the Vite plugin using PostCSS — no manual Tailwind config is needed.

\n

See the Tailwind 4 upgrade changelog for more details on the Tailwind migration.

\n

Step 5: Clean up old dependencies​

\n

Remove unwanted packages from your NX's package.json (if present):

\n\n

Then install to update your lockfile:

\n
npm install
\n

Step 6: Verify​

\n

Run serve and build to verify everything works:

\n
# Start dev server
npx nx run {app-name}:serve

# Production build
npx nx run {app-name}:build
\n

The dev server will start on a port in the range 22220–22229 and print a link to open your app:

\n
✨ Iris App is now started, check it out ✨
https://new.manager.trackunit.com/goto/iris-app-dev
\n

New executor options​

\n

Serve options​

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionTypeDefaultDescription
viteConfigstring—Path to custom Vite config file (optional)
portnumberauto (22220-22229)Dev server port
hoststringlocalhostDev server host
skipTypeCheckingbooleanfalseSkip TypeScript type checking during dev
\n

Build options​

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
OptionTypeDefaultDescription
viteConfigstring—Path to custom Vite config file (optional)
outputPathstring—Output directory (required)
skipTypeCheckingbooleanfalseSkip TypeScript type checking during build
\n

Bundle analysis​

\n

To analyze your bundle size, set the BUNDLE_ANALYSE environment variable:

\n
BUNDLE_ANALYSE=true npx nx run {app-name}:build
\n

This generates a stats.html file in the output directory using rollup-plugin-visualizer.

\n

Troubleshooting​

\n

CORS errors during development​

\n

The Vite dev server automatically sets CORS headers for Trackunit domains. If you see CORS errors:

\n
    \n
  1. Verify the Vite server is running
    2. \n
  2. Check that \"Use Local Apps\" is enabled in developer settings
    3. \n
  3. Ensure no proxy is interfering with requests
    4. \n
", "url": "https://developers.trackunit.com/changelog/2026/02/26/migrate-from-rspack-to-vite/", "title": "Iris Apps now use Vite instead of Rspack", "summary": "Iris Apps have been migrated from Rspack to Vite as the build system. Vite provides near-instant dev server startup, fast HMR using native ES modules, and optimized production builds.", "date_modified": "2026-02-26T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/02/19/iris-app-v1-11-45-nx-upgrade/", "content_html": "

In this version of our Iris App SDK, we have upgraded NX to v22.4.4.\nMake sure to upgrade your extensions to the latest version of NX.

\n
npx nx migrate 22.4.4
npx nx migrate --run-migrations
\n

Please refer to Maintaining Your Application for more information.

", "url": "https://developers.trackunit.com/changelog/2026/02/19/iris-app-v1-11-45-nx-upgrade/", "title": "trackunit/iris-app v1.11.45 - NX upgraded to v22.4.4", "summary": "In this version of our Iris App SDK, we have upgraded NX to v22.4.4.", "date_modified": "2026-02-19T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/tailwind-4-upgrade/", "content_html": "

In this version we upgraded the foundation for our tailwind to use tailwind 4.1.18 instead of 3.x.

\n

Effected packages:

\n\n

Also, many of the React libraries have changed, so make sure to update all Trackunit dependencies.

\n

Use this command to make sure you are updated with all latest Trackunit dependencies

\n
npx npm-check-updates \"/@trackunit/\" -u
\n

Now you need to install the latest tailwind dependencies

\n
npm install @tailwind/postcss@4.1.18 --save-dev
npm install tailwindcss@4.1.18 --save-dev
\n

After this the 'serve' command will use the correct tailwindcss/postcss and all Trackunit dependencies are updated.

\n

For more information on how it might effect your own tailwind classes in your codebase - check this Migration guide

", "url": "https://developers.trackunit.com/changelog/tailwind-4-upgrade/", "title": "Tailwind upgraded from v3 to v4", "summary": "In this version we upgraded the foundation for our tailwind to use tailwind 4.1.18 instead of 3.x.", "date_modified": "2026-02-16T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2026/01/15/assets-api-stable-version-v2/", "content_html": "

Released stable version v2 of Assets API.

\n

The Assets API v2 builds on the foundation of v1 with expanded querying, improved asset lifecycle management, and enhanced flexibility. In addition to onboarding, offboarding, and updating asset specifications, v2 introduces advanced filtering and pagination, asset querying by multiple identifier types, asset hiding and unhiding, and dedicated support for asset notes. The API also streamlines telematics device attachment flow, providing a more consistent and scalable way to manage assets across accounts and fleets. For more information, see the updated endpoint documentation.

\n

Below a list of all available endpoints:

\n
\n

➕ GET: /asset/v2/assets

\n
\n

Get assets

\n
\n

➕ GET: /asset/v2/assets/{assetId}

\n
\n

Get asset

\n
\n

➕ POST: /asset/v2/assets

\n
\n

Create assets

\n
\n

➕ PATCH: /asset/v2/assets

\n
\n

Update assets

\n
\n

➕ DELETE: /asset/v2/assets/{assetId}

\n
\n

Delete asset

\n
\n

➕ POST: /asset/v2/assets/query

\n
\n

Query assets by identifiers

\n
\n

➕ PATCH: /asset/v2/assets/hidden

\n
\n

Hide or unhide assets

\n
\n

➕ PATCH: /asset/v2/assets/note

\n
\n

Update asset note

\n
\n

➕ POST: /asset/v2/assets/notes/query

\n
\n

Fetch asset notes

\n
\n

➕ POST: /asset/v2/assets/{assetId}/telematics-devices

\n
\n

Attach telematics device

", "url": "https://developers.trackunit.com/changelog/2026/01/15/assets-api-stable-version-v2/", "title": "Assets API v2", "summary": "Released stable version v2 of Assets API.", "date_modified": "2026-01-15T00:00:00.000Z", "tags": [ "Added" ] }, { "id": "https://developers.trackunit.com/changelog/2025/11/26/rackunitiris-app-vxxxxx-node-upgraded-to-v24/", "content_html": "

In this version of the App SDK, we have upgraded Node to the current LTS version 24.11.1. Make sure to upgrade your workspace to at least that version.

\n

If using volta, you can install the latest LTS version of Node by running:

\n
volta install node@lts
\n

or by adding the following to your root package.json

\n
package.json
\"volta\": {
  \"node\": \"24.11.1\"
}
\n

Otherwise, you can download the latest LTS version of Node from the Node.js website.

", "url": "https://developers.trackunit.com/changelog/2025/11/26/rackunitiris-app-vxxxxx-node-upgraded-to-v24/", "title": "trackunit/iris-app v1.7.96 - Node upgraded to v24", "summary": "In this version of the App SDK, we have upgraded Node to the current LTS version 24.11.1. Make sure to upgrade your workspace to at least that version.", "date_modified": "2025-11-26T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2025/10/06/filters-filter-bar-v1-7-90/", "content_html": "

Filter URL Synchronization​

\n

Filter states are now automatically synchronized with URL parameters, allowing users to bookmark or share filtered views. When filters are applied, the URL updates to reflect the current filter state, and the filters are restored when navigating back to that URL.

\n

Breaking Change​

\n

TanStack Router is now required for Iris app extensions using the filter bar.

\n

Your app entry point must be wrapped with TanStack Router's RouterProvider. See the iris-app-with-router-example for a complete implementation example showing how to set up the router in your Iris app extension.

", "url": "https://developers.trackunit.com/changelog/2025/10/06/filters-filter-bar-v1-7-90/", "title": "trackunit/filters-filter-bar v1.7.90 - Filter URL Synchronization", "summary": "Filter URL Synchronization", "date_modified": "2025-10-06T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2025/09/04/custom-fields-def-key/", "content_html": "

We enhanced the endpoint for setting custom field values to support definition keys as an alternative to definition UUIDs. This improvement eliminates the need to hardcode UUIDs in your integration code, making your implementations more maintainable and readable.

\n
\n

➕ POST: /api/custom-fields/v1/set-values/

\n
\n

Set custom field values

", "url": "https://developers.trackunit.com/changelog/2025/09/04/custom-fields-def-key/", "title": "Set custom fields values using definition key", "summary": "We enhanced the endpoint for setting custom field values to support definition keys as an alternative to definition UUIDs. This improvement eliminates the need to hardcode UUIDs in your integration code, making your implementations more maintainable and readable.", "date_modified": "2025-09-04T00:00:00.000Z", "tags": [ "Improved" ] }, { "id": "https://developers.trackunit.com/changelog/2025/06/24/day-ranger-picker-popover/", "content_html": "

The DayRangePickerPopover component is being deprecated in favor of the new DayRangeSelect component. The new DayRangeSelect component replaces it with all the same functionality but with a more user friendly user experience.

", "url": "https://developers.trackunit.com/changelog/2025/06/24/day-ranger-picker-popover/", "title": "Deprecation of Day Range Picker Popover Component", "summary": "The DayRangePickerPopover component is being deprecated in favor of the new DayRangeSelect component. The new DayRangeSelect component replaces it with all the same functionality but with a more user friendly user experience.", "date_modified": "2025-06-24T00:00:00.000Z", "tags": [ "Removed" ] } ] }