> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/integrations/translations/lokalise.md).

# Lokalise

<div align="left"><figure><img src="/files/KXZvOfcPgNmj70lhYNLB" alt=""><figcaption></figcaption></figure></div>

## Set up

### Navigate to the Integration settings view

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Integrations** in the sidebar

### **Connect Lokalise**

1. Find the **Lokalise** integration module under the **Translations** section.
2. Click the **Connect** button.
3. Enter a Lokalise API token.

{% hint style="info" %}
You can find or create a new Lokalise API token by visiting your **Profile settings > API tokens** page in the Lokalise dashboard. Note that the API token must have the following permissions:

* Read and write access to your projects
  {% endhint %}

{% hint style="warning" %}
&#x20;Lokalise API tokens are scoped at the user level – when creating an API token, we recommend using a service account user to avoid losing access to your connected API tokens if the user associated with an API token leaves your company.
{% endhint %}

### Configure the Lokalise integration

1. Select a Lokalise **Project** from the dropdown. All translations in this project will be pulled into Runway and cross referenced with your app's codebase.
2. Select a **Metadata Translations** project (optional): If you keep your metadata translations in a separate project from the project specified in the first step, select the project you use to manage metadata translations. Read more about how Runway can help you manage metadata translations [here](/using-runway/release-steps/metadata.md#metadata-translations).

For more details on how the translations integration populates the data found on the Translations step, visit the [Translations step documentation](/using-runway/release-steps/translations.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.runway.team/integrations/translations/lokalise.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.