Public keys are specifically designed for authenticating the Retell Chat Widget when embedded on your website. Unlike API keys, which should never be exposed in client-side code, public keys are safe to include in frontend applications for this specific purpose.
Public keys are used exclusively for:
For security reasons, public keys are restricted to specific domains. This prevents unauthorized use of your public key on other websites.
To configure allowed domains:
example.com
, app.example.com
)Testing on localhost
To test your integration locally, add localhost
to your allowed domains list. This enables development and testing on your local machine before deploying to production.
While public keys are specifically designed for use with the Retell Chat Widget in client-side code, you should still follow these best practices:
You can create, view, and manage your public keys from the Retell dashboard:
Public keys are specifically designed for authenticating the Retell Chat Widget when embedded on your website. Unlike API keys, which should never be exposed in client-side code, public keys are safe to include in frontend applications for this specific purpose.
Public keys are used exclusively for:
For security reasons, public keys are restricted to specific domains. This prevents unauthorized use of your public key on other websites.
To configure allowed domains:
example.com
, app.example.com
)Testing on localhost
To test your integration locally, add localhost
to your allowed domains list. This enables development and testing on your local machine before deploying to production.
While public keys are specifically designed for use with the Retell Chat Widget in client-side code, you should still follow these best practices:
You can create, view, and manage your public keys from the Retell dashboard: