Registering Domains for SDK Integration
Register all required domains for proper SDK functionality across environments.
The Web SDK identifies your site to the Grovs backend by its origin: the scheme, host, and port the page is served from, such as https://app.example.com or http://localhost:3000. On every authentication the backend compares that origin exactly against the linked domains configured for your project, and rejects the SDK with "This Web app is not configured" when it is not listed. So every origin the SDK runs on must be registered, including local development and staging.
Register all domains, including localhost URLs for development. Missing domains will cause the SDK to fail in those environments.
Identify all environments
List every environment where your application is deployed or tested. Common environments include production, staging, test, and local development.
Collect full URLs
Gather the full URLs for each environment, including protocol (http or https) and port if applicable:
# Production
https://www.example.com
# Test
https://test.example.com
# Staging
https://staging.example.com
# Development
http://localhost:8080
http://localhost:3000Log in to the Grovs dashboard
Open the Grovs dashboard and navigate to the domain registration section for your project.
Add each domain
Add each origin exactly as the browser reports it: the same scheme, the same host, and the port when it is not the default. https://example.com and https://www.example.com are different origins, and so are http://localhost:3000 and http://localhost:5173.
Verify registration
Load your site in each environment with info logging on and confirm configure resolves true:
const ready = await Grovs.configure({
apiKey: 'your-api-key',
debugLevel: 'info',
onError: (code, message) => console.error(code, message),
});
console.log('Grovs configured:', ready);If it resolves false with an authenticationFailed error whose message says the web app is not configured, the message includes the exact origin string the SDK sent. Copy that string into the dashboard rather than retyping it.
If you add new environments later, register their domains in the Grovs dashboard before deploying to those environments.