For the complete documentation index, see llms.txt. This page is also available as Markdown.

Migration to OzCapsula

This guide describes the migration to the latest OzCapsula architecture: the approach where you use an encrypted container to securely transmit data between frontend and backend.

Component version requirements

Before starting the migration, ensure that all components are updated to the minimum required versions:

  • API: 6.6.1.

  • Web SDK: 1.9.10.

  • Native SDKs (iOS / Android) and Flutter: 10.0.0.

We highly recommend using the latest versions of Oz software.

For best results, migrate all components simultaneously and avoid partial upgrades.

Authentication changes

All capture sessions now require a session_token issued by the backend.

  • The token must be obtained before starting video capture.

  • It is tied to the current session and the specific container.

  • The token has a limited lifetime.

Migration actions

  • Implement a backend call to obtain session_token.

  • Pass the token explicitly when creating the capture screen.

Flow changes

Before container (legacy flow)

  1. You launch media capture.

  2. Media is captured.

  3. Media along with required data is sent to Oz API (using your backend as intermediate if needed).

With container (new flow)

  1. You request session_token from backend.

  2. You put additional data like metadata (if needed) into container and launch video capture with session_token.

  3. SDK captures media, packages it into container, and returns an encrypted file.

  4. The encrypted file is sent to Oz API (using your backend as intermediate if needed).

Migration actions

API

  • Upgrade to v6.6.1 or newer.

  • Switch Content-Type of data you send to application/octet-stream.

  • For Instant API, obtain private and public keys as described here.

Web SDK

  • Upgrade to v1.9.10 or newer.

  • Ensure backend supports session_token.

  • In the configuration file, set use_wasm_container to true and api_use_session_token to api or client (please refer to this article for details).

  • Update initialization to pass token explicitly.

  • If you use the capture architecture type, ensure you receive and send to your backend and then to us a blob object (application/octet-stream).

Mobile SDKs

  • Upgrade to v10.0.0 or newer.

  • Ensure backend supports session_token.

  • Implement new interfaces as described below.

Please note: do not use "_" (underscore) in file names for the container flow.

Android

1

Launching capture screen

2

Subscription to media

3

Launching analysis

iOS

1

Launching capture screen

2

Subscription to media

3

Launching analysis

Flutter

1

Launching capture screen

2

Subscription to media

3

Launching analysis

Migration checklist

Last updated

Was this helpful?