Quickstart

Use this page when you want to connect a client product to Kalima for the first time.

What you need before you start

Item	Why it matters	Where to get it
Project key	Identifies the Kalima project your integration should read from or send to	Dashboard guide
API base URL	Tells your integration which Kalima environment to call	Environments
Default language	Defines the source locale for your project	Your project setup in Kalima
Supported locales	Controls which languages you expose to end users	Your project setup in Kalima

Pick the fastest path

Script Tag

Use this when you want Kalima to translate a website or web app with minimal engineering work.

1. Create or open your project in Kalima.
2. Copy the project key.
3. Add the SDK script to your site.
4. Set window.KalimaConfig if you need to override defaults.
5. Load the page in a target locale and confirm translations resolve.

Public API / SDK API

Use this when your frontend or backend needs direct control over how translations are fetched or applied.

1. Create or open your project in Kalima.
2. Store the project key in your application config.
3. Call the public API to fetch project info and approved translations.
4. Apply returned strings inside your app.
5. Add phrase extraction or instant translation only if your workflow needs it.

WordPress

Use this when the site is managed in WordPress and your team wants a plugin-first setup.

1. Install the Kalima Localization plugin.
2. Open Settings -> Kalima.
3. Set the project key and confirm the API base URL.
4. Save the default language and supported locales.
5. Verify that the SDK loads on the public site.

Shopify

Use this when the storefront runs on Shopify and you want Kalima settings controlled via the app and theme embed.

1. Install the Kalima Shopify app.
2. Save your project key, API base URL, and SDK script URL.
3. Enable the theme embed.
4. Confirm locale behavior on the storefront.
5. Verify that translations and language switching behave correctly.

First verification checklist

• Project key is present and points to the correct Kalima project
• Production or QA API base URL matches the environment you intend to use
• Default language is correct
• Supported locales reflect the languages you want to expose
• One known phrase renders correctly in a non-default locale

After the first install

• Read Integrations for path-specific configuration
• Read API & SDK overview if you need custom behavior
• Read Troubleshooting if the first page does not translate as expected

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.

Contact KalimaEmail info@kalima.digital