Localization

Atlas is multi-locale by design. A single entry (or page) can hold values for several languages at once: one base value for the default locale plus any number of per-locale translations. The Public API returns the right values for the language you request, falling back to the base when a translation is missing.

How it fits together

Locale codes are short language tags such as en, id, or fr (2–10 characters).

Reading a specific locale

Request a language by adding ?locale= to any Public API list or detail endpoint.

curl "https://api.atlas.latellu.com/api/v1/public/entries/getting-started-with-headless-cms?locale=id" \
  -H "X-API-Key: atlas_live_abc123xyz"

?locale= is available on both entry endpoints:

Understanding the response

The entry's data object always contains default-locale values for every field. The translations.<locale>.data object contains values that override data for localizable fields only. Your frontend should merge these: use the translation value when present, otherwise fall back to data.

{
  "success": true,
  "data": {
    "slug": "getting-started-with-headless-cms",
    "status": "published",
    "data": {
      "title": "Getting Started with Headless CMS",
      "summary": "A beginner-friendly introduction to decoupled content management.",
      "cover_image": {
        "url": "https://cdn.atlas.latellu.com/blog/covers/headless-cms-intro.webp",
        "width": 1200,
        "height": 630
      },
      "published_at": "2026-05-10T08:00:00Z"
    },
    "translations": {
      "id": {
        "data": {
          "title": "Memulai dengan Headless CMS",
          "summary": "Pengenalan ramah pemula untuk manajemen konten terpisah."
        }
      }
    }
  }
}

In this example cover_image and published_at are not localizable — they have no per-locale override, so you always read them from the top-level data. title and summary are localizable and appear in translations.id.data for Indonesian.

Fallback behaviour

If you request a locale that the entry has no translation for, Atlas returns the default-locale values rather than an empty result. The single-entry endpoint flags this with is_fallback: true, so your frontend can show a "translation unavailable" hint when needed.

{
  "success": true,
  "data": {
    "slug": "getting-started-with-headless-cms",
    "status": "published",
    "is_fallback": true,
    "data": {
      "title": "Getting Started with Headless CMS",
      "summary": "A beginner-friendly introduction to decoupled content management."
    },
    "translations": {}
  }
}

Next Steps

• Entries — the full entry structure and data/translations shape.
• Pagination & Filtering — combine locale with paging and filters.