10.10 GET /languages — supported locales

Flat list of locales the read API can actually serve. Use the code values here as the ?lang= parameter on every other endpoint.

A locale appears only when it is active in the platform AND wired to the web channel — i.e. it has post translations being produced. Asking for a ?lang= outside this list falls back to en-US silently (per §8), so the list is the partner-safe whitelist.

Example request:

curl -H "Authorization: Bearer zk_YOUR_KEY" \
     "https://zippfeed.com/api/v1/developer/languages"

Response:

{
  "languages": [
    {
      "code": "en-US",
      "name": "English",
      "native_name": "English",
      "country_code": "US",
      "direction": "ltr",
      "is_default": true
    },
    {
      "code": "tr-TR",
      "name": "Turkish",
      "native_name": "Türkçe",
      "country_code": "TR",
      "direction": "ltr",
      "is_default": false
    }
  ]
}

Fields: - code — BCP-47 tag, the value you pass as ?lang= - name — English name (for UI in english-speaking contexts) - native_name — endonym (e.g. Türkçe, Français) - country_code — ISO 3166-1 alpha-2, drives flag rendering - direction — ltr or rtl - is_default — exactly one row has true (the fallback when ?lang= is omitted or invalid)

No pagination — the list is small (≤14) and stable. Cached client-side for 30s per §5.