> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/changelog.md).

# Changelog

What's new across tiun — the dashboard, the snippet, and the SDKs. Newest release first.

Every release has its own link: hover its heading and copy the link icon to share it. Subscribe with the RSS button at the top of the page to get new releases in your reader. Questions about a release? Ask in [#community-support on Discord](https://discord.gg/NCggN2ExZ9).

{% updates format="full" %}
{% update date="2026-11-04" tags="snippet,react-native" %}

## Product methods in the SDKs

Read your catalog and check a user's access — including repeatable purchases — straight from the web and React Native SDKs, plus fixes for remounting components.

### For developers

**Products and product access in the browser**

Four new methods mirror the [Product and Product Access APIs](https://docs.tiun.io/api/) on the client: `tiun.listProducts()` lists your products, `tiun.getProduct(productId)` returns a product with its localized pricing line, `tiun.listProductAccess()` lists the current user's active access with `referenceId`, `activatedAt`, and `expiresAt`, and `tiun.checkProductAccess(productId, { referenceId })` tells you whether the user has access to a product. Being logged out isn't an error — you get `[]` or `{ hasAccess: false, access: null }`. In React Native, the same four methods are on `useTiun()`. See [Core Methods / Products](/sdk/web-sdk/core-methods.md#products) and [Hooks and events](/sdk/react-native-sdk/hooks.md).

**Repeatable purchases can be checked in the browser**

Pass the same `referenceId` you used at checkout to `checkProductAccess()` to show the article, booking, or order the customer bought — or a "Purchased" badge instead of a buy button — without setting up a backend. If you have a backend, checking on your server stays the more secure option. See [Repeatable one-time purchases](/guides/one-time-purchases/repeatable-one-time-purchases.md#check-in-the-browser).

**`userChange` fires for more access changes**

`userChange` fires with `event: 'checkout'` whenever the user's access changes. It now also fires when a repeatable product is bought with a new reference ID, and when access changed in another tab, once the user comes back to this one. See [Events](/sdk/web-sdk/events.md).

In React Native, the `userChange` payload now includes `event`, the same as the web SDK.

**Fixes in the web SDK**

* Calling `tiun.init()` again after `tiun.destroy()` — for example when a component remounts — now works. Before, `checkout()`, `login()`, `start()`, and `setContent()` waited forever. After a re-init, `tiun.user` stays empty until the next login, logout, or checkout. See [Lifecycle and `destroy()`](/sdk/web-sdk/initialization.md#lifecycle-and-destroy).
* Parallel `tiun.getUserVerificationToken()` calls each get a token. Before, all but the last returned `null`.
* `tiun.waitForReady()` called before `tiun.init()` now resolves once the snippet is ready, instead of never.
* `tiun.isReady` now stays `true` after `tiun.destroy()`, since the snippet is still loaded.

Nothing else changes for existing integrations.

{% hint style="info" %}
**Packages in this release:** [`@tiun/sdk` 0.12.0](https://www.npmjs.com/package/@tiun/sdk/v/0.12.0) · [`@tiun/react-native-sdk` 0.5.0](https://www.npmjs.com/package/@tiun/react-native-sdk/v/0.5.0). The product methods and the React Native `event` field need these versions or later.
{% endhint %}
{% endupdate %}

{% update date="2026-11-02" tags="snippet,react-native,dashboard,api" %}

## November 2026

Repeatable one-time purchases, limited access for one-time products, and webhooks that tell your server when users sign up, gain or lose access, or withdraw consent.

### For merchants

**Repeatable one-time purchases**

One-time products can now be bought again and again — for single articles, bookings, tickets, or reports. Turn on **Repeat purchases** when you create or edit a one-time product under **Products**; the price is charged each time. Every purchase is tied to a `referenceId` your app passes to checkout, such as the article or order it's for. See [Repeatable one-time purchases](/guides/one-time-purchases/repeatable-one-time-purchases.md).

**Limited access for one-time products**

Turn on **Limited access** to make a one-time purchase last a set number of days, weeks, months, or years from the day of purchase — useful for passes and time-limited content. When it runs out, the product leaves the customer's `productAccess`. Nothing renews automatically. See [Products](/reference/generic/products.md#one-time-purchase).

### For developers

**`referenceId` at checkout**

`tiun.checkout({ productId, referenceId })` ties a purchase to your own reference ID, and is required for repeatable products — without it, checkout shows a configuration error. React Native's `checkout()` takes the same option. Check a purchase from your backend with `GET /live_api/s2s/v1/users/{userId}/product_access/{productId}?referenceId=…`, or list all of a user's access with `GET /live_api/s2s/v1/users/{userId}/product_access`. Checking a reference from the frontend SDK is coming soon.

**Newsletter opt-in on the user object**

The user object now includes `hasNewsletterOptIn`, in the SDKs and in the server-to-server user APIs.

**User verification v2**

Server-side verification now uses `POST /live_api/s2s/v2/users/verification`. The response carries the user under `user` instead of `userInfo`. See [Verify authentication server-side](/guides/authentication/verify-server-side.md).

**Webhooks**

Your backend can now react to changes in tiun without the user being in your app — for example to keep access in your own database in sync, send a welcome email, or delete a user's data. Add an endpoint under **API & Webhook → Webhooks** in the [dashboard](https://my.tiun.business/), pick the events it should receive, and tiun sends it a `POST` request whenever one happens. Four events are available: `user.create`, `user.revoke_consent`, `product_access.add`, and `product_access.remove`.

Events are deliberately simple: they carry IDs only and aren't signed, so confirm the current state with a server-to-server API call before acting on one. Failed deliveries are retried up to 10 times over about 48 hours, and the dashboard shows every delivery, lets you resend one, and sends test events so you can check your handler without real data. Sandbox and live have separate endpoints. Start with [Receive webhooks](/guides/webhooks/receive-webhooks.md), and see [Webhook events](/reference/webhooks/events.md) for every payload.

{% hint style="info" %}
**Packages in this release:** [`@tiun/sdk` 0.11.0](https://www.npmjs.com/package/@tiun/sdk/v/0.11.0) · [`@tiun/react-native-sdk` 0.4.0](https://www.npmjs.com/package/@tiun/react-native-sdk/v/0.4.0). `referenceId` and `hasNewsletterOptIn` need these versions or later.
{% endhint %}
{% endupdate %}

{% update date="2026-10-23" tags="snippet,react-native,dashboard,mcp,api" %}

## October 2026

Dark mode for the snippet, React Native in the dashboard, more control over subscriptions, tax and MCP access, and a server-to-server Product API.

### Highlights

**Dark mode for the snippet**

The snippet now comes in `light`, `dark`, or `auto`, so login, checkout, and paywall overlays match your site instead of always rendering light. `auto` follows the visitor's OS setting and re-themes live when it changes. Set `appearance` in `tiun.init()`, or switch it at runtime with `tiun.setAppearance()` — for example from your own theme toggle — with no reload; the React Native SDK has the same `appearance` option. It's a code setting, not a dashboard one, and the default stays `light`, so nothing changes until you opt in. See [Initialization](/sdk/web-sdk/initialization.md) for the web SDK and [Configuration](/sdk/react-native-sdk/configuration.md) for React Native.

**Mobile SDK, now in the dashboard**

You can now monetize your React Native app with tiun — subscriptions and one-time purchases, with login and checkout rendered inside the app. Register your app in the [dashboard](https://my.tiun.business/) under **Settings → Environment setup**: turn on **App** and enter your app scheme, for example `myapp://`, in each environment you use. Then follow [Integrate with React Native](/guides/app-integration/monetize-in-react-native.md) from setup through to going live.

### For merchants

**Daily and weekly subscriptions**

Subscriptions can now renew every day or every week, alongside monthly and yearly — useful for short passes, weekly plans, or testing renewals without waiting a month. When you create a subscription under **Products**, set the interval unit to day or week; the count works as before, so *every 2 weeks* is valid too. See [Products](/reference/generic/products.md#subscription).

**Prices with or without tax**

Subscription and one-time products now have a **tax behavior** setting, so the price you enter means what you intend. **Include tax** means the price customers see already includes tax, **Exclude tax** adds tax on top at checkout, and **Automatic** — the default — uses the customer's location to apply the usual convention for their region. Choose it when you create a product under **Products**. See [Tax behavior](/reference/generic/products.md#tax-behavior).

**MCP access controls**

You now decide how much of your account an AI agent can reach through the tiun MCP. When you connect it, choose which providers the agent can access and whether it gets read-only or read-write access — so an agent can, for example, read your catalog without being able to create or edit products. To add a provider later, reconnect the MCP and select it. See [Agent integration](/guides/agent-integration/agent-integration.md).

### For developers

**Server-to-server Product API**

Fetch your products and their pricing straight from your backend — for example to render your own pricing page or keep plan names in sync with the dashboard instead of hardcoding them. The API is read-only: list your products, or get a single product with its pricing, localized in English, German, or French. It authenticates with the same API keys you create under **API & Webhook** → **API Keys** in the dashboard, and works in both sandbox and live. See the [API reference](https://docs.tiun.io/api/).

{% hint style="info" %}
**Packages in this release:** [`@tiun/sdk` 0.10.1](https://www.npmjs.com/package/@tiun/sdk/v/0.10.1) · [`@tiun/react-native-sdk` 0.3.0](https://www.npmjs.com/package/@tiun/react-native-sdk/v/0.3.0). Dark mode needs `@tiun/sdk` 0.10.0 or later.
{% endhint %}
{% endupdate %}
{% endupdates %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tiun.io/changelog.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
