File url fetch failed · file.url_fetch_failed

Stable ID: file.url_fetch_failed · Evidence: source derived

Telegram could not retrieve content from the HTTP URL.

The response does not distinguish DNS, network, TLS, HTTP, or origin-access failures.

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: failed to get HTTP URL content

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

Illustrative methods: sendPhoto, sendDocument.

Possible causes

• Retrieving content from the URL failed.

Before deciding what to do

Application decision: inspect url retrieval. Repeat request: after relevant change.

• Check that Telegram can retrieve the resource without browser sessions or private-network access; retry only under a bounded policy.

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: sendPhoto.

{
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: failed to get HTTP URL content"
}

Python

from errorgram import classify

response = {
    "ok": False,
    "error_code": 400,
    "description": "Bad Request: failed to get HTTP URL content",
}
result = classify(response, method='sendPhoto')

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

JavaScript and TypeScript

import { classify } from "errorgram";

const response = {
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: failed to get HTTP URL content"
};
const result = classify(response, { method: "sendPhoto" });

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

Framework names

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

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:116–117. WEBPAGE_CURL_FAILED is rewritten to this description. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
• Bot API 10.3 · telegram-bot-api/Client.cpp:85–106. The rewrite runs only after the error is normalized to code 400. 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