Abstract

The GC LAC Starter Genesys Cloud Load, Auth, Cache is a lightweight, browser-only base for rapid
Genesys Cloud Platform API prototyping. It removes authentication friction so you can start building POCs immediately.
LAC performs three jobs in order: it loads the Genesys Cloud JavaScript SDK, it performs OAuth 2.0 Implicit Grant authentication, and it caches the token for reuse.
No Node, no frameworks, no secrets in the browser.

How does it work?

The starter uses standard web pieces with the official SDK and OAuth flow:

Boot sequence

1. Detect or load the SDK from the official CDN.
2. Parse URL parameters, clientId, env, optional debug.
3. If a valid token exists in localStorage, reuse it. Otherwise, initiate loginImplicitGrant(clientId, redirectUri).
4. After redirect back, capture #access_token, compute expiry, set the token on the SDK client.
5. Expose window.gcClient and window.gcPlatformClient for immediate API calls.

How do I use it?

1. Create an OAuth client

1. In Genesys Cloud Admin, go to IT and Integrations then OAuth then Add a client.
2. Grant Type: Token Implicit Grant, Browser.
3. Authorized redirect URIs: exact URL of your hosted LAC HTML file, for example:
   https://www.talkingscientist.com/example/gc-lac-starter.html.
4. Scope: least privilege, for example:
   analytics conversations notifications presence routing:readonly users:readonly.
5. Save, copy the Client ID. The Client Secret is not used by Implicit in the browser, store it securely and never ship it.

Helpful references

• Create an OAuth client
• Scopes reference
• Regions and required domains
• Implicit Grant guide

2. Host the page

Serve gc-lac-starter.html from any HTTPS host, for example a static site, S3, or a local dev server.

3. Launch with parameters

https://<your-host>/gc-lac-starter.html?clientId=<YOUR_CLIENT_ID>&env=usw2.pure.cloud&debug=true

• clientId: your OAuth Client ID
• env: region base domain, for example usw2.pure.cloud, mypurecloud.com, mypurecloud.ie
• debug: optional, set to true for verbose logs

4. Verify authentication

Open the browser console and look for messages like, SDK available and Authentication complete, LAC ready.

Run a quick smoke test:

<script>
(async () => {
  if (!window.gcPlatformClient || !window.gcClient) {
    return console.error('LAC not ready. Check clientId, env, redirect URI, scopes.');
  }
  const api = new window.gcPlatformClient.UsersApi();
  const me = await api.getUsersMe();
  console.log('Logged in as', me.name, me.id);
})();
</script>

Where do we go from here?

LAC is an on-ramp. With a token in hand, explore the Genesys Cloud platform capabilities:

Next up: we will build a Reporting Dashboard POC that authenticates with LAC, subscribes to Notifications API topics, and visualizes queue metrics in real time. We will measure time to token, event lag, and update latency, then ship a minimal dashboard you can extend.