Skip to main content
If your app uses React Native, Ionic, Android, iOS, or another framework with a WebView component, you can integrate by pointing it at the widget’s hosted page instead of embedding the web component directly.
Pass the session code and any other setting in the URL fragment — after #, not ?:
The fragment is never sent to any server, and the widget removes _co from the URL as soon as it reads it. The code works once and expires in 2 minutes, so request it from your backend right before you open the WebView.
Your app still sees the full URL before the widget cleans it up — in navigation callbacks like shouldOverrideUrlLoading or decidePolicyFor. Don’t log WebView URLs. The code is single-use, but it shouldn’t end up in your crash reports or analytics either.

React Native example

Native Android and iOS

The widget posts {"type": "ripio-session-expired"} to whichever bridge your app registers: To renew, either evaluate renew — evaluateJavascript on Android, evaluateJavaScript on iOS — with a new code, or load the same page with a new fragment (…/index.html#_co=<new_code>&_cu=ARS). A fragment-only change doesn’t reload the page; the widget picks up the new code on its own. See Session lifecycle for the full list of events.

Other frameworks

Font customization is done through the CSS custom property --ripio-font-family, not through a URL parameter — see Theming.