Languages
21 bundled languages — pass lang and localized names arrive in the same structured shape.
Add lang to any request (body field on POST endpoints, query param on GET) and translatable strings — sign names, nakshatra names, yoga and dosha names, panchanga labels — come back localized. The response shape never changes: same fields, same numbers, translated display strings.
curl -X POST https://api.astroask.app/v1/planets \
-H "X-API-Key: ak_your_key_here" \
-H "Content-Type: application/json" \
-d '{ "date": "1990-01-15T10:30:00", "lat": 28.6139, "lng": 77.2090, "lang": "hi" }'Supported languages
| Code | Language | Code | Language | Code | Language |
|---|---|---|---|---|---|
en | English (default) | hi | Hindi | bn | Bengali |
ta | Tamil | te | Telugu | kn | Kannada |
ml | Malayalam | mr | Marathi | gu | Gujarati |
pa | Punjabi | or | Odia | es | Spanish |
pt | Portuguese | fr | French | de | German |
it | Italian | ru | Russian | ar | Arabic |
ja | Japanese | ko | Korean | zh | Chinese |
Fallback behavior
An unsupported lang code falls back to English silently — the request still succeeds. If a specific term has no translation in the requested language, that term stays in English while the rest translates; your parsing never breaks on a missing dictionary entry.
What is (deliberately) never translated
Machine-readable values — error codes, plan slugs, field names, ISO timestamps and all numbers — are locale-independent by design. Only human-facing display strings translate.