Custom Translations

The UP (MyFlight) passenger web app ships with default translations in several languages, but you can override any piece of passenger-facing text with your own wording. This is useful to:

• Match the tone of voice of your company.
• Add a custom policy text at the top of the pages.
• Adjust a sentence to your local market.
• Replace a system message with one that better fits your operation.

Custom translations are stored per language, so you can keep different wording for Dutch, French, German, English, Spanish… without affecting the others.

Before you start#

Editing translations requires an API key. The same API key controls the access to the Quick Release API, so it is created and managed in the API Settings.

Settings > API Settings > Generate API Key

See API Settings for details on creating the key.

Without a valid API key, the edit icons in the UP app will not appear and the translation modus cannot be activated. Treat the API key as a secret — anyone with the key can change your passenger-facing text.

Feature location#

Translation modus is launched from the admin app:

Settings > Operator Settings > Quick Release UP (Passenger App) > Translations

In this card you will find a button Update Translations. The button is disabled until an API key is generated.

Clicking the button opens the UP web app in a new browser tab, with your API key already attached. You are now in translation modus.

Editing a translation#

While in translation modus, browse the UP app the same way a passenger would: open a booking, navigate to the flight page, the passenger list, the chat, etc.

Next to every translatable piece of text you will see a small wrench icon:

Click the icon to open the translation editor. The editor shows:

• Preview — how the current text will be rendered for the passenger.
• Language — the language currently being edited (read-only).
• Default value — the system text shipped with Quick Release (read-only).
• Custom value — the field where you type your own version. Leave it empty to fall back to the default.

When you are happy with the result, click Save. The change is stored immediately and applies to all bookings in that language.

Editing other languages#

Each translation is bound to one language. To edit the same text in another language:

1. Open a booking that has a different contact language (see Language).
2. The UP app will switch to that language automatically.
3. Click the wrench icon next to the text and edit the custom value.

Repeat for every language you want to support. Languages you do not customize keep using the default Quick Release translation.

Removing a custom translation#

Open the editor for the translation you want to revert and click the red Delete button. The custom value is cleared and the default Quick Release wording will be shown again.

Markdown formatting#

Custom translations support Markdown, which lets you add light formatting:

• **bold** for bold
• *italics* for italics
• - item to create a bullet list
• Line breaks with an empty line between paragraphs

For security reasons, the editor will block the following content and show a validation error:

• Markdown hyperlinks ([text](https://...))
• HTML links (<a href="...">)
• <script> tags
• HTML event handlers (e.g. onclick=)

This protects your passengers against malicious content that could accidentally be pasted into a translation.

Parameters#

Some texts contain dynamic placeholders that are filled in at runtime, for example {{ name }} or {{ flightDate }}. The editor lists the available parameters below the custom value field.

You must keep the same parameter names in your custom value if you want them to be replaced. You may move them around or omit them, but you cannot invent new ones — unknown placeholders will be left as-is in the rendered text.

Example — default value:

Hello {{ name }}, your flight on {{ flightDate }} is confirmed.

A valid custom value:

Hi **{{ name }}**! 🎈 We are looking forward to flying with you on {{ flightDate }}.

Ending translation modus#

When you are done, click the red End Translate Modus button in the top navigation bar of the UP app. This clears the API key from the browser session and the wrench icons disappear. From that point on the UP app behaves exactly as it does for your passengers.

Closing the browser tab also ends the translation modus, because the API key is only kept for the current session.

Frequently asked questions#

Do I need to redeploy or restart anything after saving? No. Custom translations are loaded by the UP app for every booking, so they are visible to passengers immediately after saving.

Will my custom translations be lost when Quick Release updates the default texts? No. Custom values are stored separately in your tenant settings. If a default text changes, your custom version keeps overriding it until you delete it.

Who can edit translations? Anyone with access to your API key. Make sure to share it only with people you trust to change passenger-facing text. The role-based access controls of the admin app do not apply once the key has been distributed.

Can I translate a string that does not have a wrench icon? No. Only texts that have been wired up for customization show the wrench icon. If you would like a specific text to be customizable, please contact Quick Release support.