> For the complete documentation index, see [llms.txt](https://ston-fi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ston-fi.gitbook.io/docs/developer-section/omniston/sdk/migration-v0.7-to-v0.8.md).

# Migration v1beta7 → v1beta8

{% hint style="warning" %}
**Legacy API support notice**

Support for Omniston API `v1beta7` ends on `1 September 2026`.

Complete the React SDK `0.7` → `0.8` and API `v1beta7` → `v1beta8` migration before that date to avoid service interruption.
{% endhint %}

Use this guide when an existing React app uses `@ston-fi/omniston-sdk-react@0.7` with Omniston API `v1beta7` and needs to move to `@ston-fi/omniston-sdk-react@0.8` with Omniston API `v1beta8`.

This page is SDK-focused. For protocol terminology and API-level concepts, read the [Omniston glossary](/docs/developer-section/omniston/glossary.md), [Omniston API v1beta8](/docs/developer-section/omniston/v1beta8.md), and the [v1beta7 to v1beta8 migration guide](/docs/developer-section/omniston/v1beta7-to-v1beta8-migration-guide.md).

## Migration resources

* v1beta8 API terms glossary: [stonfi-proto GLOSSARY.md](https://github.com/ston-fi/stonfi-proto/blob/main/proto/stonfi/omni/GLOSSARY.md)
* v1beta7 to v1beta8 API migration guide: [v1beta7-to-v1beta8-migration-guide.md](https://github.com/ston-fi/stonfi-proto/blob/main/proto/stonfi/omni/v1beta8/v1beta7-to-v1beta8-migration-guide.md)
* v1beta8 SDK migration guide: [CHANGELOG.md, 17-04-2026](https://github.com/ston-fi/omniston-sdk/blob/main/CHANGELOG.md#17-04-2026)
* Reference SDK integration: [examples/react-app](https://github.com/ston-fi/omniston-sdk/tree/main/examples/react-app)

## AI-assisted migration prompt

This section is the **canonical** copy-paste prompt for React SDK 0.7 → 0.8 in this documentation set. The [API migration guide](/docs/developer-section/omniston/v1beta7-to-v1beta8-migration-guide.md) links here instead of duplicating the text.

Paste this prompt into an AI coding agent that has access to your app codebase:

```
Migrate this app from using @ston-fi/omniston-sdk-react@0.7, which works with omniston API v1beta7, to the newly released @ston-fi/omniston-sdk-react@0.8, which works with omniston API v1beta8

The STON.fi team provides the following resources that can be used during the migration:
- v1beta8 API terms glossary https://github.com/ston-fi/stonfi-proto/blob/main/proto/stonfi/omni/GLOSSARY.md. These terms should be used to correctly represent the data flow
- v1beta7 to v1beta8 API migration guide https://github.com/ston-fi/stonfi-proto/blob/main/proto/stonfi/omni/v1beta8/v1beta7-to-v1beta8-migration-guide.md. This file contains instructions on what changed in proto files that serve as structures for the API communications.
- v1beta8 SDK migration guide https://github.com/ston-fi/omniston-sdk/blob/main/CHANGELOG.md#17-04-2026. In this section of the SDK changelog file, SDK-specific changes are described with the pseudocode diffs that illustrate the migration process
- in case it is unclear how to migrate the current code base, besides the resources listed above, the reference SDK integration in a real app can be used. The example app code is open source and can be found in the SDK repo https://github.com/ston-fi/omniston-sdk/tree/main/examples/react-app

The migration steps should be as follows:
- upgrade @ston-fi/omniston-sdk-react to the latest available 0.8 version
- switch app to the API endpoint that supports v1beta8 API
- read the v1beta8 glossary and provide API and SDK migration guides
- apply necessary changes to the current codebase to start using the 0.8 SDK. Use terms from the glossary to correctly name variables and components during migration
```

## Manual checklist

Use this checklist whether migration is manual or AI-assisted:

1. Upgrade `@ston-fi/omniston-sdk-react` to the latest available `0.8` version.
2. Point the app to an Omniston endpoint that supports API `v1beta8`.
3. Review the glossary before renaming variables, components, UI labels, logs, or store fields.
4. Apply SDK-specific breaking changes from the changelog.
5. Compare unclear flow changes with the open-source React example app.
6. Test with limited amounts before production use.