Younify Connect: Frequently Asked Questions

Overview −

Access begins with a one-time implementation fee. The SDK requires an API Key and SDK Key issued through the partner portal. Contact us to get started — once you have access, you can create and manage keys directly in the partner portal.

No. Credential handling, MFA, CAPTCHA solving, and session management are all handled inside the YCS SDK layer. Your app only receives normalized data objects — never raw credentials or tokens from the streaming services.

Your backend server handles access token renewal by calling the Management API. The SDK fires an onTokenExpired delegate callback when a token needs refreshing, giving your backend the signal to request a new pair and re-initialize the SDK.

Currently: Netflix, Hulu, Prime Video, Disney+, HBO Max, Paramount+, Peacock, Apple TV, Discovery+, Tubi, Pluto TV, Fandango, YouTube, and Roku Channel — 14 services in total. New services are added regularly. These services are available in any country in which they operate — if a supported provider serves your region, the API works there. We do not currently support region-specific services, though roadmap priorities respond to partner demand. To verify coverage for your own market before committing, connect a real account in your country through the Trakt app, which runs on Younify Connect.

The cold start problem happens when new users have no viewing history in your app, so your recommendation engine has nothing to work with. By connecting their existing streaming accounts through the Younify Connect SDK, you get immediate access to years of real watch history, watchlists, and ratings — before the user has watched a single thing in your app. History extends back to the user's first recorded activity on the service — it is not a rolling window.

Most partners have the SDK initialized and returning real data within a few hours of receiving their keys. Full production integration — including UI polish and backend token management — typically takes 1–3 days depending on your app's architecture.

Users accept VPPA consent along with Younify's Terms of Use and Privacy Policy — two checkboxes on a single screen, shown on the consent screen. All data collected through the Content Services API is owned by Younify; partners receive a limited, non-exclusive, revocable license to use it within their application. Each party is an independent controller of the personal data it processes and obtains the consents allocated to it. If a user disconnects a streaming account, normalized records already held in your product may remain if the user chooses to keep them.

Getting started and API access −

The Content Services and Management API reference is at https://api.younify.tv/docs, and includes sample JSON responses for each endpoint. Documentation for each platform SDK can be found here.

Not at present. The API reference at https://api.younify.tv/docs includes sample JSON request and response bodies for every endpoint.

Create a Younify user when a user registers in your application. On the create-user call, pass your own user identifier as the External ID. We return a Younify-generated user ID — store it against your user record, since all subsequent API calls reference the Younify ID rather than your External ID. Your backend also stores that user's access and refresh tokens, renews them via the Management API, and supplies them to the SDK at configure time.

The SDK key is intended to be included in your mobile application. The Management API key is server-side only and must never be embedded in a client binary or shipped with your app.

Platform and Compatibility −

Yes. A web app is available — documentation is at my.younify.tv/services/partner-integration.html. Native SDKs remain available for iOS, Android, React Native and .NET MAUI. However, account linking is not supported in mobile web apps.

No. Account linking requires a desktop browser — Chrome or Edge — with the Younify extension installed. It cannot be completed from a mobile web app. Everything other than account linking works on virtually any platform, so a mobile-first product can treat linking as a one-time desktop step.

There is no official Flutter wrapper, but the native iOS and Android SDKs are straightforward to wrap.

The Younify Connect SDK for React Native requires React Native 0.80 or later, and each SDK release is built and tested against a current React Native release.
Your app must also meet these requirements:

  • New Architecture: required. The SDK is a Turbo Native Module and does not run on the legacy architecture.
  • Android: Android 9 (API level 28) or later.
  • iOS: the minimum iOS version is 15 (or the React Native release your app uses)

Earlier versions of React Native are not supported.

Yes, in a development build. Our SDK wraps native iOS and Android code, so it will not run in Expo Go, which only loads modules already bundled into that app. A development build compiles your own native code and can include it.

One thing to plan for: Android setup requires adding a Maven repository to android/build.gradle pointing at the SDK's deps folder in node_modules. We do not ship an Expo config plugin, so if you are using continuous native generation you will want a small config plugin to apply that change, or you will need to manage the native directories directly. iOS is a standard pod install, which prebuild handles.

Each supported service is a bespoke website integration via user-permissioned, session-based access.

Data and Synchronization −

Daily, and on end-user request.

Webhooks. We send a POST when a data refresh completes — do not schedule the user-initiated refresh endpoint to run in the background. Subscriptions are configured in the partner portal. Available events are UserDataRefreshCompleted, UserFilePosted, InitialFilePosted and DeltaFilePosted. The receiving endpoint must be SSL. An optional signature secret key is passed as the Signature header so you can verify the request has not been tampered with. For ongoing synchronization, fetch the delta after receiving UserDataRefreshCompleted. Every webhook carries a unique reference ID. Delivery is retried up to three times before we stop attempting. File formats, pagination, record identifiers and related semantics are documented here.

To the user's first recorded activity on the service.

In roughly 95% of cases. The remaining 5% are older items for which the service no longer retains bookmark data.

Yes. For a series, tmdb_id identifies the episode and tmdb_series_id identifies the series; tmdb_series_id exists only for shows. For a film, tmdb_id identifies the movie. Episode-level IDs resolve in approximately 95% of cases. Where an ID is absent, there was no clean match to a specific episode on TMDB, because TMDB and the streaming provider group or package seasons and episodes differently. In those cases we have no alternative identifier to offer — season and episode numbers are not available through another endpoint.

Each linked account selects one streaming profile to pull data from.

Watchlist functionality is currently read-only.

Yes. The watchNowUrl property is available through the SDK. It targets a specific episode rather than a series, and links have been verified to open the provider's native tvOS app at the intended episode across all supported services. Links are not region-specific and do not expire. The Management API's watch-history schema does not return these links and they cannot be looked up by TMDB series or episode ID — a backend can instead construct the watch URL from the content ID. For example: www.netflix.com/watch/[ContentID].

We do not currently enforce strict rate limits, but we ask partners to use the API responsibly. In particular, do not trigger data collection outside the normal daily automatic cadence unless a user has explicitly pressed a refresh control in your application.

The linked account moves to a broken state and we notify you. You can surface that to your user however you prefer; they re-authenticate through the Younify login flow.

Yes. Collection runs independently of whether your application is open, at minimum daily.

Broken connections are reported by webhook. In practice users typically go many months to years between re-authentications.

Automatic collection runs daily, which averages roughly a twelve-hour delay between a user watching something and it becoming available. A manual refresh gathers current data immediately.

Every webhook carries a unique reference ID, so duplicates can be identified and discarded.

Commercial and Data Use −

A one-time implementation fee, followed by a monthly fee per user-service linked account. A linked account is one user connected to one streaming service — user A to Netflix and user A to Hulu count as two user-linked accounts.

Yes. We have a start-up program, but there is no free or non-commercial tier.

There are no restrictions on caching Younify data within your application while you are an active partner under agreement.

Data Semantics −

It is the time the streaming provider last reported viewing activity for that title.

This effectively never occurs in practice.

No. How you treat a record — including what threshold counts as watched — is entirely up to your application.

Yes, in the API reference at https://api.younify.tv/docs#tag/watchhistory.

Evaluation and coverage −

Yes. The Trakt app runs on Younify Connect and is available in the app stores. Connecting your own streaming accounts in your own country is the fastest way to see real history, episode matching and Watch Now behavior for your market before you commit.

No. Where you host your backend has no bearing on which services or regions are supported.

Integration −

The sample application demonstrates the supported integration, dependencies and minimum OS version.

There is no official SPM package — wrap the supplied XCFramework in your own package. No privacy manifest is required.

Billing −

Billing is based on valid connections at month end. There are no additional fees for normal usage — SDK access, API requests, refreshes, webhooks and support are all included.

No. That still counts as one user-service linked account.

−Collapse All Categories