Veltra is now available in nine languages
The Veltra docs, API reference, guides and dashboard are now published in Chinese, Korean, Japanese, Russian, Spanish, Portuguese, German and French alongside English.
Most of the people pulling wallet trade history are not reading English as a first language. Veltra is now published in nine languages: English plus Simplified Chinese, Korean, Japanese, Russian, Spanish, Brazilian Portuguese, German and French.
This is not a machine-translated overlay bolted onto the English pages. Each language has its own URLs, its own metadata, and its own copy written for developers who work in that language.
What's translated
- The full API documentation — quickstart, authentication, endpoint reference, errors and rate limits, plans, response times, and support.
- Every blog post, including each chain launch announcement.
- The step-by-step tutorial and the Veltra vs Helius comparison.
- The dashboard, sign-in, and the page that hands you your API key.
- Privacy policy and terms, each naming the English text as the controlling version.
How to read Veltra in your language
Every page carries a language picker next to the Veltra wordmark, and each language lives at its own path — /de/docs, /ja/blog, /ko/tutorial. Switching languages keeps you on the page you were reading rather than sending you back to a homepage, and the choice follows you into the dashboard.
There is deliberately no automatic redirect based on your browser language. You land on the page you asked for, and switching is always a visible, reversible choice.
What stays in English
Anything you type or parse is identical in every language. Field names like amountSol and tokenMint, error codes like RATE_LIMIT_EXCEEDED, query parameters, HTTP headers, and every curl example are byte-for-byte the same across all nine — because a translated identifier is a broken integration.
Chain names, plan names, and SOL / JSON / NDJSON stay put too. What gets translated is the prose around them, plus the comments inside code samples where they explain rather than execute.
The API itself is unchanged
One key, one endpoint, the same response shape on every chain. Localization changes how the documentation reads, not how the API behaves — your existing integration keeps working exactly as it did.