API Portal
Portal localization
Translate your API Portal into another language: request the system-string file from support, translate the values, and return it named so Apiable can load the language, with English as the fallback.
You can translate your API Portal into another language. The portal's system strings are managed in a translation backend, and you supply the translated values through Apiable support. English is the fallback for anything left untranslated.
How do you localize the API Portal?
Email Apiable support for the language file, translate the values in it, and return it named for the language. Apiable loads the translations so developers see the portal's system strings in that language.
- Email support@apiable.io and ask for the portal language file.
- You receive a file listing every system-string key with its English value.
- Translate the values, leaving the keys unchanged.
- Return the file, naming the language in full, for example
en-US - English - United States.
What gets translated, and what does not?
The language file covers system strings: the buttons, labels, and built-in messages the portal ships with. It does not cover the content you author. Pages and products are translated separately in the dashboard.
| Text | Where it is translated |
|---|---|
| System strings | The portal's built-in buttons, labels, and messages. Translated in the language file you request from support. |
| User-generated content | Your pages, products, and articles. Translated in the dashboard where you author them. |
What happens to strings you do not translate?
They fall back to English. The portal's fallback language is English, so any key you leave untranslated renders its English value. A partial translation is safe: translated strings show in the new language, and the rest stay readable in English.
Is this the same as the dashboard's language?
No. This page is about the consumer-facing API Portal. The admin dashboard has its own language options for the people who run the portal. Translating the portal does not change the dashboard, and the reverse is also true.
Where to next
Theme
Set the colours, typography, and landing copy around your translated strings.
Portal pages
Author the page content you translate separately in the dashboard.
Markdoc components
The components you place in those pages.
API Portal overview
How pages, theme, navigation, and settings make up your portal.