File id invalid · file.id_invalid

Stable ID: file.id_invalid · Evidence: source derived

The server could not resolve the supplied file_id.

The generic fallback does not identify a malformed ID, a bot-specific access issue, or permanent unavailability.

When it matches

Every field in a rule must match. Alternative rules are joined with OR. Codes below are JSON response fields, not inferred HTTP statuses.

• JSON error_code: 400.

Exact description:

Bad Request: invalid file_id

See matching rules for parameter precedence and unknown or ambiguous results.

Illustrative methods: getFile.

Possible causes

• A remote-file lookup failed and the normalizer replaced its original error.

Before deciding what to do

Application decision: verify file identifier. Repeat request: after relevant change.

• Check that this bot received the exact file_id and that file_unique_id was not substituted.

These are application choices. Errorgram does not retry, suppress the error, or change bot state.

Facts

This condition adds no extracted facts; result.facts is empty.

Example

Synthetic examples derived from the cited source.

API method: getFile.

{
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: invalid file_id"
}

Python

from errorgram import classify

response = {
    "ok": False,
    "error_code": 400,
    "description": "Bad Request: invalid file_id",
}
result = classify(response, method='getFile')

assert result.id == 'file.id_invalid'
print(result.entry["summary"])

JavaScript and TypeScript

import { classify } from "errorgram";

const response = {
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: invalid file_id"
};
const result = classify(response, { method: "getFile" });

if (result.status === "matched" && result.id === "file.id_invalid") {
  console.log(result.entry.summary);
}

Framework names

Integration	Type or ID
Python	errorgram.FileIdInvalid
aiogram	errorgram.aiogram.FileIdInvalid extends TelegramBadRequest
grammY	EnrichedGrammyError with classification.id equal to file.id_invalid

Enrichment is explicit and keeps framework catch compatibility. Follow the Python and aiogram guide or JavaScript, TypeScript, and grammY guide.

Evidence

• Bot API 10.3 · telegram-bot-api/Client.cpp:7525–7527. Remote-file lookup errors receive the invalid file_id fallback. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
• Bot API 10.3 · telegram-bot-api/Client.cpp:85–108. The fallback replaces only errors normalized to code 400. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
• Bot API 10.3 · telegram-bot-api/Client.cpp:17032–17035. getFile uses this remote-file lookup. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
• Bot API 10.3 · telegram-bot-api/Client.cpp:165–205. Adds the code-specific prefix and lowercases only the initial character of ordinary messages. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.

Source references identify the reviewed revision, not the first release that introduced this response.

Data and versions

Catalogue 0.1.0 · schema 1.0.0 · reviewed 2026-09-16.

Markdown · Condition JSON · Full catalogue and sources · JSON Schema