Language support

AstroWay is building a multilingual API — text interpretations, reports, and daily horoscopes are available in the user’s language. The canonical list is 21 languages, derived from astrology-market demand research (search volume, competitor coverage, revenue potential).

Current status

Two axes: Quality tier (translation readiness) × Demand score (market priority, 48–95+).

#	Code	Language	Q-tier	Demand	Reports	Site
1	`uk`	Ukrainian	✅ Master	—	✅ Full	✅
2	`en`	English	✅ T0	95+	✅ Full	✅
3	`de`	German	✅ T0	72	✅ Full	📋
4	`ru`	Russian	✅ T0	70	✅ Full	📋
5	`pl`	Polish	🚧 T1	64	🚧 Beta	📋
6	`es`	Spanish	🚧 T1	88	🚧 Beta	📋
7	`pt`	Portuguese	🚧 T1	84	🚧 Beta	📋
8	`hi`	Hindi	🚧 T1	81	🚧 Beta	📋
9	`fr`	French	🚧 T1	78	🚧 Beta	📋
10	`ko`	Korean	🚧 T1	77	🚧 Beta	📋
11	`it`	Italian	📋 T2	73	📋	📋
12	`ja`	Japanese	📋 T2	67	📋	📋
13	`id`	Indonesian	📋 T2	62	📋	📋
14	`tr`	Turkish	📋 T2	60	📋	📋
15	`nl`	Dutch	📋 T3	58	📋	📋
16	`cs`	Czech	📋 T3	56	📋	📋
17	`ro`	Romanian	📋 T3	54	📋	📋
18	`vi`	Vietnamese	📋 T3	53	📋	📋
19	`ar`	Arabic	📋 T3	52	📋	📋
20	`el`	Greek	📋 T3	50	📋	📋
21	`hu`	Hungarian	📋 T3	48	📋	📋

Legend:

✅ Full / ✅ — production-ready, full coverage
🚧 Beta / 🚧 — AI translation in progress, glossary in review, some inaccuracies possible on complex terms
📋 — planned, not started yet

Quality Tier — what it means

T0 (Master + Manual) — every report string, every interpretation has a manual translation reviewed by professional astrologers. The glossary (~800 terms) is verified by an expert native speaker. This is the quality baseline.
T1 (AI Beta) — translation via AI (Gemini Flash / Claude Haiku) with a consistent glossary. Manual review on the most sensitive parts (Lal Kitab, Vedic Sanskrit, Hellenistic Greek). Quality 85–92% vs T0.
T2 / T3 (Planned) — on the roadmap, waiting for per-language glossary bootstrap. Released in batches of 3–4 languages, highest demand score first.

Demand Score — how it’s calculated

A composite index built from:

Google Trends 12-month volume on astrology keywords in the country
Coverage by top-5 competitors (Co–Star, AstroSeek, Astro.com, Prokerala, DivineAPI)
Estimated population × estimated paid-app penetration
Revenue-per-user delta (PPP-adjusted)

Not a precise metric — a ranked priority that helps decide “what’s next” objectively rather than by impression.

How to call

curl -X POST https://api.astroway.info/v1/interpret/aspects \
  -H "Authorization: Bearer aw_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "lang": "es",
    "aspects": [
      { "body1": "Sun", "body2": "Moon", "type": "conjunction", "orb": 2.1 }
    ]
  }'

Reply (sample for lang=es):

{
  "ok": true,
  "data": {
    "interpretation": "El aspecto Sol-Luna en conjunción simboliza...",
    "lang": "es",
    "tier": "T1-Beta"
  }
}

The tier field in the response explicitly signals the status — use it to render a UX indicator in your app (“Beta translation” badge).

If you need a language not on the list

Email hello@astroway.info with demand evidence (sample users, projected volume). We review the list quarterly — a language with real external demand can be added as Tier 4 (opt-in).

Some languages on the short-list are permanently skipped — da, fi, no, bg, sk, hr, zh-CN, fa, tl — due to small market or absent astrology tradition. ?lang=X for them returns 400 Invalid lang.

Translation pipeline

T1 translations flow through a dashboard glossary editor (modeled on the astroway.info WP plugin). Workflow:

AI provider (Gemini Flash 2.5 / Claude Haiku 4.5) translates to target lang with glossary context
Cache in astroway_dbapp.translations_cache (TTL 90 days, invalidate when source changes)
Manual review in dashboard /dashboard/admin/translations for high-sensitivity strings
Export to reports-renderer.ts I18N constant and api-calc/src/locales/*.json

See the implementation plan: docs/LANGUAGE-PLAN.md.

Calculation accuracy — numerical calculations are language-neutral, only text is localized
Reports — multilingual PDF reports
Idempotency — cache discounts work independently of lang

Was this helpful?

Suggest an edit

Last updated: May 11, 2026