translate.vertexapis.com docs conflict: /language/translate/v2 works, plain /v2 is 404

[obdagli]

Summary

Two repo sources disagree on translate.vertexapis.com endpoint support, and I live-tested the conflicting path families after opening this issue.

Live-verified results

Using a working local key on 2026-03-16:

• POST /language/translate/v2 -> 200, translated Hello world to Selam Dünya
• GET /language/translate/v2/languages -> 200
• POST /v2 -> 404
• GET /v2/languages -> 404
• POST /v2/detect -> 404
• POST /v3/projects/vertex/locations/us-central1:translateText -> 200
• POST /v3beta1/projects/vertex/locations/us-central1:translateText -> 200

Revised conclusion

The real distinction is not simply "v2 vs v3".

It looks like:

• the legacy Google-style path family under /language/translate/v2 works,
• the plain root /v2 family does not,
• and v3 / v3beta1 also work.

So the two repo sources may have tested different path families:

• vertexapis_research/vertexapis-workaround.md documents /language/translate/v2
• vertexapis-research/endpoints/translate-vertexapis-com.md reports 404 for /v2, /v2/detect, /v2/languages

Suggested fix

Update the docs to distinguish these explicitly instead of describing this as a generic "v2 unsupported" result.

[obdagli]

Follow-up: I attempted live revalidation after opening this issue, but the repository checkout only contains placeholder API keys (YOUR_CORTEX_API_KEY) and there is no usable VERTEX_API_KEY/CORTEX_API_KEY in the current environment.

So this issue should be read as a documentation/source-conflict report, not as a fresh live-API verification claim from my side.

If you have a working key, the missing final step would be to re-test these path families and then either:

1. confirm the newer deep-test report (v3/v3beta1 only), or
2. explain that v2 support changed over time and annotate the older workaround note as historical.