Migrating from V1 to V2

intro welcome to the latest version of intelliprove! our v2 api unlocks powerful new features and improvements if you’re familiar with intelliprove’s v1 api, upgrading to v2 will be straightforward—this guide walks you through what’s new and how to make the switch what's new ✨ a new look and improved experience enjoy an entirely new interface and ux during the face scan, including live results, dynamic progressbar, a smart assistant to guide users and personalized user inputs to finetune the health insights face scan docid\ mw6gpbzekcj lzrqjll 🧠 smarter insights insights now take into account more of the user's personal profile, including age and sex, making them much more personalized, engaging and smart overview docid 83ca0u016ddhbg6urwwwn 🧩 intelliwidgets easiliy embed ready made health insight tiles in your app's existing pages, including heart rate, respiratory rate and many more widgets docid\ sxvsw2jfsohr7xbxeyz j core concepts in the v2 api let's recap a few concepts not all of these are new, but they're now more formalized and used more consistenlty throughout the api, so it's good to do a refresher user represents an individual end user each user is created once and assigned a unique user id, which is used to track face scans and health insights ➡️ this replaces the older concepts of patient and performer you’ll use the user id to access all health related data face scan a single video based scan performed by the user each scan has a unique face scan id face scan docid\ mw6gpbzekcj lzrqjll biomarkers objective measurements from a single face scan (e g , heart rate, respiratory rate) biomarkers docid\ buhj nt45fuxcpges0qph metrics insights derived from analyzing multiple scans over time these are grouped into a user health profile metrics docid\ yeqwskx81eju z8n3djhy upgrading to v2 the overall approach is familiar you request a url from our api, embed the plug in in an iframe, and receive results either in the ui or via the api what’s new in v2? updated api structure endpoints reflect the new concepts introduced in v2 explicit user creation users must be registered before a plug in session is initiated user linked sessions each plug in session is now associated with a specific user id upgrade flow creating the user add an api call to register the user (if it’s their first scan and they haven't been registered yet) provide a unique user id this id will also be used to retrieve health insights later request the plug in url use the user id to obtain the url through the new api endpoint embed the plug in use the returned url in your frontend, as before (optional) request health insights via the api once the scan is complete, retrieve biomarker results through a separate api call retrieve metrics at any point using the user's user id refer to the section below on how to keep the result format compatible with what you have today 📘 full setup instructions—including api references—can be found in our getting started guide initial integration docid\ qghldn2mla8w9rpkeigwn compatibility with v1 results format if you want to keep using the existing v1 results format (e g for backward compatibility in your frontend or data pipeline), you can continue using the legacy results endpoint below this allows you to adopt the new v2 plug in for face cans, while keeping your business logic unchanged you can migrate to the new results format when ready