Markup invalid json · markup.invalid_json

Stable ID: markup.invalid_json · Evidence: source derived

The reply_markup argument is not valid JSON.

Valid JSON with the wrong shape or invalid button fields produces different errors.

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: can't parse reply keyboard markup JSON object

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

Illustrative methods: sendMessage, editMessageReplyMarkup.

Possible causes

• A nonempty reply_markup argument failed JSON decoding.

Before deciding what to do

Application decision: correct reply markup json. Repeat request: after relevant change.

• Serialize reply_markup as a JSON object with the structure required by the selected keyboard type.

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

{
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: can't parse reply keyboard markup JSON object"
}

Python

from errorgram import classify

response = {
    "ok": False,
    "error_code": 400,
    "description": "Bad Request: can't parse reply keyboard markup JSON object",
}
result = classify(response, method='sendMessage')

assert result.id == 'markup.invalid_json'
print(result.entry["summary"])

JavaScript and TypeScript

import { classify } from "errorgram";

const response = {
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: can't parse reply keyboard markup JSON object"
};
const result = classify(response, { method: "sendMessage" });

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

Framework names

Integration	Type or ID
Python	errorgram.MarkupInvalidJson
aiogram	errorgram.aiogram.MarkupInvalidJson extends TelegramBadRequest
grammY	EnrichedGrammyError with classification.id equal to markup.invalid_json

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:10504–10518. The reply_markup parser emits this literal only when JSON decoding fails. Revision e3e9dd8e5b3d7ab8537cd5a10dc31d5ffa8f82d1.
• Bot API 10.3 · telegram-bot-api/Client.cpp:13800–13803. Method validation errors are passed to the response normalizer. 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