API Reference
Understand the public website widget boundary before connecting customer-specific or private account information.
The standard website widget is a public entry point. A visitor-entered name, email address, or a browser-stored conversation ID does not establish an authenticated customer identity.
Keep private account lookups behind your own authenticated server. Validate the signed-in user and authorize access to each requested record there. Never place an API key or signing secret in website code.
For a customer-specific identity or authorization requirement, contact the Enterprise team to confirm a supported design before deployment.
See API Authentication for server API keys, Embed Guide for the public widget, and Security and Privacy for account controls.