spec sheet · stores & files

App Store Connect and Transglot, localize your App Store listing.

Add your App Store Connect API key, select your app, and map its languages in project settings. Sync listing copy, review translations, and publish the mapped target-language fields.

Import and publish translations

Direction: Import and publish translations
Plan: Starter and up
Scope: one app listing, per App Store locale
Authentication: an App Store Connect API key file, with its issuer and key ids
Get started: Connect from your project’s CMS settings.

Create your project Setup

stores & files

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect App Store Connect
In the project’s CMS settings, choose App Store Connect and provide an App Store Connect API key file, with its issuer and key ids.
connect
Choose the content and locale mapping
Select the app and locale mapping. The connector reads one app listing, per App Store locale.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Publish to App Store Connect
Use Publish to CMS to send the translated values to the mapped target locales. Check the publish result in the project’s CMS settings.
deliver

Publish translated values back to the target locales you map in App Store Connect.

what moves

What you can translate and deliver.

Your whole App Store listing as one entry: name and subtitle at the app level, description, keywords, promotional text, what's new, marketing URL and support URL on the version that is still editable. Each target locale's localization is patched or created, never the source locale's.

What you can translate and deliver.
Surface	What to expect
Source and scope	one app listing, per App Store locale
Translated output	Publish translated values back to the target locales you map in App Store Connect.
Keep in mind	This connector localizes store-listing copy. It does not translate the strings inside your app binary or submit a new app build.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

an App Store Connect API key file, with its issuer and key ids.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project and configure its source and target locales.
In the project’s CMS settings, choose App Store Connect and provide an App Store Connect API key file, with its issuer and key ids.
Select the app and map its store locales to the project locales. Run Sync from CMS to import the listing copy.
Review the translations, then use Publish to CMS to write only the mapped target-locale listing fields.

same project, more possibilities