GoApp configuration and events

GoApp is configured as part of the partner integration. Public client-side parameters must not be used as a substitute for server-side user creation or authentication.

User identification

Create the user through the REST API and use Abi’s returned id in the GoApp URL. Your partner-supplied uniqueId remains your system reference.

Branding and display

Abi can agree partner-specific colors, logos, and display behavior so the consultation experience fits naturally in your product. Your application may also manage the button or floating action that opens the GoApp iframe. Confirm customization with your account manager before relying on it in production.

Language and physician country

Set language and physicianCountry when creating or updating the user through the API. English is the default language. Available languages and clinician locations depend on the partner agreement.

GoApp can support an agreed consent journey where the user has already accepted the relevant terms and privacy notice in your product. Domain or IP allowlisting can restrict where GoApp is embedded, and usage controls can apply agreed limits to a user’s access. These arrangements must be reviewed with Abi before implementation.

Browser events

GoApp can communicate integration events with window.postMessage.

window.addEventListener('message', (event) => {
  if (event.origin !== 'https://goapp.abi.ai') return
  const message = event.data
  // Handle only documented message types and validated payloads.
})