Environments
Kalima supports separate production and QA paths for clients that need a staging flow.
Production endpoints
| Surface | URL |
|---|---|
| Docs | https://docs.kalima.digital |
| Website | https://kalima.digital |
| Dashboard | https://app.kalima.digital |
| Translator app | https://translator.kalima.digital |
| Platform API | https://api.kalima.digital/api/v1 |
| Public SDK API | https://sdk-api.kalima.digital/api/v1 |
| Hosted SDK script | https://uni-sdk.kalima.digital/kalima.js |
QA endpoints
| Surface | URL |
|---|---|
| Platform API | https://qa-api.kalima.digital/api/v1 |
| Public SDK API | https://qa-sdk-api.kalima.digital/api/v1 |
QA access is useful when your team wants to validate an integration before production rollout. If your Kalima engagement only uses production, keep one environment everywhere.
Environment rules
- Do not mix a production project key with QA API hosts
- Do not point browser-facing integrations at raw
run.appservice URLs - Keep dashboard-generated snippets aligned with the environment you intend to ship
- When in doubt, ask Kalima which environment is provisioned for your account
Which API base should you use?
- Use
https://sdk-api.kalima.digital/api/v1for the JavaScript SDK and public client runtime endpoints - Use
https://api.kalima.digital/api/v1for platform workflows such as the current WordPress plugin defaults and other broader platform interactions
Support
Need help shipping this integration?
If you hit a blocker, contact Kalima with your project key, target environment, and a short description of what failed.