MultiAPICall Feature
Chain multiple WebViewGold API calls in a single request with the MultiAPICall feature for iOS.
This is an optional feature for iOS since Apple-based browsers process multiple page reloads on the same script differently to Android-based browsers.
This means calling window.location.href = "exampleAPItrigger" multiple times on the same web page script will not work on iOS, unlike on Android.
The MultiAPICall feature allows you to call multiple APIs in a single window.location.href assignment at the end of your web page script. This may be useful to you if you wanted to pre-load more than one data feature from the app, ready to be used on a page.
MultiAPICall supports the following data collection APIs as entries:
"get-uuid", "user-disable-tracking", "getonesignalplayerid", "getappversion", "__haptics (light, medium, heavy, success, warning, error)"
Use JavaScript to this kind of URL to call multiple APIs at once (make sure to include a check to only use on the iOS platform):
<script>
// Example combination: "getonesignalplayerid" and "getappversion"
if (getMobileOperatingSystem() == "iOS") {
// iOS: Use MultiAPICall feature, separate API names by commas (","), NO spaces
window.location.href = "multiapicall://getonesignalplayerid,getappversion";
} else {
// Android: Can handle multiple calls at once, use normal API call structure
window.location.href = "getonesignalplayerid://";
window.location.href = "getappversion://";
}
</script>Click here to view a demonstration web page for this feature. Inspect the page to view the example code.
SDK-style implementation notes
Treat this feature as a native capability exposed to your web layer: keep your production website or PWA as the source of truth, then use the documented WebViewGold configuration flags, URL commands, and JavaScript bridge calls to opt in to native iOS behavior only where it adds value. This approach keeps your codebase maintainable because the same web application can serve browsers, WebViewGold for iOS, and the other WebViewGold platforms with minimal conditional logic.
For reliable results, prefer HTTPS endpoints, stable route names, explicit success/error states in your UI, and small JavaScript helper functions that wrap native calls. For example, a web app built with jQuery Mobile, Lovable, Base44, Bolt, WordPress, Bubble, a custom React/Vue/Angular stack, or static HTML can expose a single button or event handler that triggers the native WebViewGold API while still showing a graceful browser fallback.
- Recommended integration pattern: detect the app context, call the WebViewGold API, then update your web UI after the native callback or route change.
- Testing checklist: validate the feature on a real device or packaged build, verify permissions and store review text, and confirm that browser-only users still receive a useful fallback.
- SEO benefit: keep feature pages, route titles, and structured content indexable on your website while WebViewGold delivers the native app shell for iOS users.