Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-03-02-v9-1-22.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v9.1.22"
description: "Introduced Tago AI, a generative AI assistant and chat experience integrated into your account."
slug: "/tagoio-api/v9-1-22"
product: "tagoio-api"
version: "v9.1.22"
---

## Highlights

- Introduced Tago AI, a generative AI assistant integrated into your account. Use the AI chat to explore your data, build resources, and get context-aware help across the platform.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-03-25-v9-1-29.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v9.1.29"
description: "Added OIDC single sign-on support for TagoRUN portals."
slug: "/tagoio-api/v9-1-29"
product: "tagoio-api"
version: "v9.1.29"
---

## Highlights

- Added OIDC single sign-on (SSO) for TagoRUN, letting your end users authenticate through your own identity provider.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
20 changes: 20 additions & 0 deletions changelog/tagoio-api/2026-03-27-v9-1-30.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
title: "TagoIO API v9.1.30"
description: "Profile-level configuration for Tago AI and expanded AI agent capabilities."
slug: "/tagoio-api/v9-1-30"
product: "tagoio-api"
version: "v9.1.30"
---

## Highlights

- Added profile-level configuration for the Tago AI service, so AI behavior can be managed per profile.
- Expanded Tago AI agents with ordered search, batch data operations, and notification support.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-04-01-v9-1-33.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v9.1.33"
description: "Fixed timezone handling in aggregate data queries."
slug: "/tagoio-api/v9-1-33"
product: "tagoio-api"
version: "v9.1.33"
---

## Highlights

- Fixed timezone handling in aggregate queries so date grouping now respects the configured timezone.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-05-05-v10-0-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.0.0"
description: "Major platform modernization across the API and infrastructure, with no customer-facing breaking changes."
slug: "/tagoio-api/v10-0-0"
product: "tagoio-api"
version: "v10.0.0"
---

## Highlights

- Major platform modernization across the API and supporting infrastructure, including runtime and core service upgrades. No customer-facing breaking changes were made.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-06-01-v10-0-33.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.0.33"
description: "Added support for custom signup authorization parameters in OIDC SSO."
slug: "/tagoio-api/v10-0-33"
product: "tagoio-api"
version: "v10.0.33"
---

## Highlights

- Added support for custom signup authorization parameters in OIDC single sign-on configuration, giving you more control over the sign-up flow.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-06-02-v10-1-0.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.1.0"
description: "Custom domains can now be used on authenticated TagoRUN routes."
slug: "/tagoio-api/v10-1-0"
product: "tagoio-api"
version: "v10.1.0"
---

## Highlights

- Authenticated TagoRUN routes now accept profile-based URLs, enabling custom domains for your TagoRUN portals.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-06-02-v10-1-3.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.1.3"
description: "Security hardening for the data query path."
slug: "/tagoio-api/v10-1-3"
product: "tagoio-api"
version: "v10.1.3"
---

## Highlights

- Hardened the data query path with request limits and access-control fixes to protect your account against abuse.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-06-09-v10-1-4.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.1.4"
description: "Fixed immutable data retention removing one extra period per device."
slug: "/tagoio-api/v10-1-4"
product: "tagoio-api"
version: "v10.1.4"
---

## Highlights

- Fixed an immutable retention issue where one extra retention period could be dropped per device.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required
19 changes: 19 additions & 0 deletions changelog/tagoio-api/2026-06-16-v10-1-11.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,19 @@
---
title: "TagoIO API v10.1.11"
description: "Issued tokens now carry a type prefix so you can identify them at a glance."
slug: "/tagoio-api/v10-1-11"
product: "tagoio-api"
version: "v10.1.11"
---

## Highlights

- New profile, analysis, Run user, and network tokens are now returned with a type prefix (`p-`, `a-`, `u-`, `n-`), making tokens self-describing in logs, screenshots, and configuration files. Device tokens are unchanged. See [Account Token](/docs/tagoio/profiles/account-token#token-format-and-prefixes) for the full prefix reference.

## Breaking Changes

- None

## Upgrade Notes

- No special actions required. Existing tokens continue to work, and the API accepts tokens with or without a prefix on every request.
2 changes: 2 additions & 0 deletions docs/tagoio/devices/device-token.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,8 @@ Each time a device is created, the system automatically creates a device token.

:::

Unlike other [token types](/docs/tagoio/profiles/account-token.md#token-format-and-prefixes), device tokens are returned without a type prefix. They are provisioned into hardware and firmware where the token length is often fixed, so the raw form is preserved to avoid breaking those clients.

## Finding the Device Token

- Open the device in the TagoIO Console (see the Devices documentation for details).
Expand Down
16 changes: 16 additions & 0 deletions docs/tagoio/profiles/account-token.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,3 +41,19 @@ More than one token can be created for the same profile. Permissions and expirat
The expiration field defines the lifespan of a token; it can be set to a temporary period or left infinite (never expires).

A new token is automatically generated each time you log in to your account, or when someone with whom you have shared your profile logs in. These auto‑generated tokens are created with an expiration time of 3 months and will be deleted automatically after that period or when the user logs out of the account manually.

## Token Format and Prefixes

Tokens issued by TagoIO carry a short prefix that identifies their type, so you can recognize a token at a glance in logs, screenshots, and configuration files:

| Prefix | Token type |
| ------ | --------------------- |
| `p-` | Profile token |
| `a-` | Analysis token |
| `u-` | Run user token |
| `n-` | Network token |
| `at` | Service authorization |

[Device tokens](/docs/tagoio/devices/device-token.md) are returned without a prefix, because they are provisioned into hardware and firmware where the token length is often fixed.

Tokens created before prefixes were introduced keep working, and the API accepts tokens with or without a prefix on every request.
Loading