WebViewGold Documentation · Android
🇺🇸 English
Get WebViewGold

Multi API Call (multiapicall://)

Call several WebViewGold data APIs in one single window.location.href assignment — ideal for cross-platform web apps that also target the iOS version.

The Multi API Call feature allows you to trigger several WebViewGold APIs in one single window.location.href assignment. This is especially useful for cross-platform web apps: Apple-based browsers process multiple page redirects on the same script differently than Android — calling window.location.href = "exampleAPItrigger" multiple times in the same script works on Android, but not on iOS. With multiapicall://, the very same web code works on both platforms.

Supported APIs as entries:

How to Use:

Separate the API names (and their values, if any) by commas (,) — no spaces:

<script>
// Example combination: "getonesignalplayerid" and "getappversion"
window.location.href = "multiapicall://getonesignalplayerid,getappversion";
</script>

Passing values to the Dynamic UI APIs works like this:

<script>
// Set the status bar to red, its text color to white, and fetch the UUID — all in one call
window.location.href = "multiapicall://statusbarcolor,255,0,0,statusbartextcolor,white,get-uuid";
</script>

Note: On Android, calling the individual APIs one after another (e.g., window.location.href = "get-uuid://"; followed by window.location.href = "getappversion://";) works as well. Use multiapicall:// if you want to share one code path with the iOS version of WebViewGold.

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 Android behavior only where it adds value. This approach keeps your codebase maintainable because the same web application can serve browsers, WebViewGold for Android, 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 Android users.

Too busy? We set up your app for you.

Our team configures, builds & submits your WebViewGold app — done-for-you, fast turnaround, Made in Germany.

Get your app set up →

Build in your browser

No Mac, no IDE: the WebViewGold Cloud Builder configures, builds & uploads your app online.

Discover Cloud Builder →