Config IDs
Generate and manage Config IDs to connect your applications to Hawcx
Overview
A Config ID is the credential that connects your application to Hawcx. It's scoped to a specific project and environment, and it's what you pass to the Hawcx SDK to initialize authentication.

Generate a Config ID
- Open your project and go to Settings > Config IDs
- Ensure the correct environment is selected (Development or Production)
- Click Generate Config ID
- Give it a descriptive name (e.g., "iOS Test App")
- Select the Platform: Web, iOS, or Android
- Click Generate
The full Config ID is displayed once upon creation. Development Config IDs remain visible in the list afterward.
Development vs Production
| Development | Production | |
|---|---|---|
| Who can create | Admin or Developer | Provisioned by the Hawcx team |
| Provisioning | Instant | Provisioned by Hawcx on request |
| Use case | Testing, staging, local dev | Live user-facing apps |
Moving to production
To go live, contact the Hawcx team to have your production environment provisioned. Once it's enabled, you generate production Config IDs the same way as in Development.
Revoke a Config ID
Revoking is permanent and immediately blocks all requests made with that Config ID.
- Find the Config ID in the list
- Click Revoke
- Confirm the action
Admins can revoke any Config ID in the organization. Developers can only revoke Config IDs they created.
Using Your Config ID
Pass the Config ID when initializing the Hawcx SDK:
// React
<HawcxProvider config={{ configId: 'your_config_id' }}>// Vanilla JS
const client = createHawcxAuth({ configId: 'your_config_id' });# Environment variable
VITE_HAWCX_CONFIG_ID=your_config_idBase URL
Your Base URL sits right next to the Config ID on the same Project Settings page in the Admin Console — copy it from there.
The base URL is unique to your environment — there is no universal default. Backend SDKs take it directly; the Web SDK's apiBase defaults to production, so for a sandbox project set it explicitly (frontend apiBase, backend base URL) or your PoC will silently talk to production.
Next Steps
- 5-Minute Integration to build a complete login flow
- Web SDK Quickstart for full frontend setup
Last updated on