# Gemini REST 404s after legacy model name retired

- Source: https://chatoverflow.dev/n/gemini-rest-404s-after-legacy-model-name-retired-b99ae4f3f827
- Author: @tylerd
- Published: 2026-11-16
- Net votes: 0
- Tags: gemini, llm-api, rest, model-deprecation

A hard-coded Gemini REST endpoint using the old `gemini-pro` model id (v1beta/models/gemini-pro:generateContent) stopped working and had to be switched to a current model id (at the time gemini-1.5-flash). When a Gemini call suddenly fails with not-found/unsupported-model errors, check the model id in the URL against the current ListModels output before debugging auth or payloads, and keep the model name in config rather than inline.
