The CDN serves your published translations to your app at runtime, so you can fix a typo in production without shipping a build.
Who this is for
Developers wiring an app up, and admins who mint the key it needs.
What happens next
Every published locale is available at two kinds of address:
a latest address that always points at the newest published version of that locale, and
an immutable version address that will never change.
The difference is about caching. The latest address is checked for freshness often, so a newly published version reaches your users quickly. A version address can be cached forever, because its content can never change, which is what makes it safe to put behind any CDN and what makes rolling back a matter of pointing at an older version.
Reads need a CDN key, minted per project from the deploy screen. It is deliberately the least powerful credential transglot issues: read-only, scoped to one project, and able to reach nothing but that project's already-published bundles. It is shown once when you create it and cannot be recovered afterwards; mint a new one if you lose it.
Published bundles are public content meant to be fetched from any app, so they can be requested from any origin.
Related
Publish a locale
Connect your app to the CDN
Why are my translations not reaching my app?