Перейти до вмісту
AstroWay/api v2.200.11 · docs
усі системи в нормі

Translate batch

POST
/translate/batch
request.sh
curl -X POST https://api.astroway.info/v1/translate/batch \
-H "X-Api-Key: aw_live_..." \
-H "Content-Type: application/json" \
-d '{ "items": [ "Mercury retrograde", "Full Moon in Leo" ], "target_lang": "pl", "domain": "western" }'

Translate up to 25 strings (≤2000 chars each, ≤20000 total) sharing one target language + domain. Credits: 15 + ceil(total_chars/40).

X-Provider
string
Allowed values: openai anthropic google groq mistral openrouter deepseek together

Bring your own model key: the LLM provider that should run this completion. Send together with X-Provider-Key or the request is refused: a key with no provider bills us for tokens you meant to pay for, and a provider with no key would look like it worked. The endpoint is fixed per provider on our side and is never taken from the request. There is no fallback to our own chain: if your key fails you get the provider’s status and message.

Example
anthropic
X-Provider-Key
string

Your own credential for X-Provider. Never logged, stored or cached: it travels in a header because the request body is hashed into two cache keys, and a BYOK turn bypasses both caches in each direction. A provider error that quotes the key back is redacted before it reaches our logs or your response. Such a turn costs 5 credits instead of the endpoint price, and only when a completion actually ran on your key.

Example
sk-ant-...
X-Provider-Model
string
<= 120 characters

Optional model id, overriding the default for that provider. Defaults: openai → gpt-4o-mini, anthropic → claude-sonnet-4-5, google → gemini-2.5-flash, groq → openai/gpt-oss-120b, mistral → mistral-large-latest, openrouter → meta-llama/llama-3.3-70b-instruct, deepseek → deepseek-chat, together → meta-llama/Llama-3.3-70B-Instruct-Turbo.

Example
claude-sonnet-4-5
fields
string

Comma-separated dotted paths, relative to data, to keep in the response. A path is applied to every element of an array, so planets.name means the name of each planet. Paths that match nothing come back in _fields_unmatched; a list where nothing matches at all is a 400, because an empty object would be a confident wrong answer.

Example
planets.name,planets.longitude
precision
integer
<= 15

Round every non-integer number in the response to this many decimal places. Integers are left alone, because an id is not a measurement. Ecliptic longitudes ship with fourteen decimals by default; 2 is about a tenth of an arcminute.

Example
4
Media type application/json
object
items required
Array<string>
>= 1 items <= 25 items
target_lang required
string
Allowed values: uk en de pl es pt hi fr ko it ja id tr nl cs ro vi ar el hu
source_lang
string
Allowed values: uk en de pl es pt hi fr ko it ja id tr nl cs ro vi ar el hu
domain
string
Allowed values: vedic western tarot numerology hd marketing generic
Example
{
"items": [
"Mercury retrograde",
"Full Moon in Leo"
],
"target_lang": "pl",
"domain": "western"
}

Successful calculation

Media type application/json
object
ok
boolean
data
object
items
Array<object>
nullable
object
translated
string
nullable
provider
string
nullable
source_lang
string
nullable
target_lang
string
nullable
domain
string
nullable
count
number
nullable
chars
number
nullable
credits
number
nullable
Example
{
"ok": true
}

Validation error

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_INPUT",
"message": "Validation failed: date: Date must be YYYY-MM-DD",
"details": [
{
"path": "date",
"message": "Date must be YYYY-MM-DD"
}
]
}
}

Missing or invalid API key

Media type application/json
Example
{
"ok": false,
"error": {
"code": "INVALID_API_KEY",
"message": "Invalid API key"
}
}
Корисно?