Messenger Platform · error code

Messenger error 1: Received invalid JSON reply

RetryableGeneric & request errors

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Received invalid JSON reply.

What error 1 means

Code 1 with subcode 1357046 means the Graph API front end received a reply from an internal service that it could not parse, so it handed you an error instead of a normal Send API response. The striking part is the scenario Meta's error-codes table uses to illustrate it: a developer sends a batch of messages containing two text messages and one video, "the messages are all sent successfully, but the endpoint returns an error," and the table adds that "there is a system delay in returning the error message."

Read that carefully, because it inverts the usual rule that an error object means nothing was delivered. With 1357046, the recipient may already have every message in the batch. A bot that blindly retries the whole batch can therefore send the text twice and the video twice, which is worse for the person than the original failure.

Treat the subcode as an unknown outcome rather than a failure. Compared with plain code 1, which is usually transient or permission-related, this variant points at the response path, especially on slow requests such as video attachments, not at your payload.

What it looks like

{
  "error": {
    "message": "(#1) Received invalid JSON reply.",
    "type": "OAuthException",
    "code": 1,
    "error_subcode": 1357046,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • Batched Send API calls that mix text with heavier attachments such as video, where the reply is slow to assemble.
  • Internal timeouts while Meta processes a large attachment, surfacing after the message was already accepted.
  • Long-running requests where the response path fails even though delivery succeeded.

How to fix Messenger error 1

  1. 1Do not retry immediately; first check whether the messages arrived by watching message_echoes and message_deliveries webhook events for that PSID.
  2. 2Retry only the items that have no echo after a reasonable wait, and attach an idempotency key in message metadata so duplicates are detectable.
  3. 3Send video attachments in their own request, separate from text, so one slow item cannot cloud the outcome of the others.
  4. 4Prefer uploading video once via the Attachment Upload API and sending the attachment_id, which shortens the send call.
  5. 5Log the full error object including fbtrace_id so recurring cases can be reported to Meta.

How to stop it recurring

Design sends to be idempotent: subscribe the app to message_echoes, store the outgoing metadata you attach, and reconcile on echoes rather than on HTTP responses alone. Keep heavy media out of mixed batches and upload it ahead of time. Throughput rules that interact with large sends are listed in the Messenger limits reference.

Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.

Related codes

Error 1 - quick answers

What does Messenger error 1 mean?

Code 1 with subcode 1357046 means the Graph API front end received a reply from an internal service that it could not parse, so it handed you an error instead of a normal Send API response.

How do I fix Messenger error 1?

1. Do not retry immediately; first check whether the messages arrived by watching message_echoes and message_deliveries webhook events for that PSID. 2. Retry only the items that have no echo after a reasonable wait, and attach an idempotency key in message metadata so duplicates are detectable. 3. Send video attachments in their own request, separate from text, so one slow item cannot cloud the outcome of the others. 4. Prefer uploading video once via the Attachment Upload…

Can I retry after error 1?

Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.

Stop debugging Messenger by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.