WhatsApp error 131052: Media download error
Last verified against Meta for Developers - Cloud API error codes
Unable to download the media sent by the user.What error 131052 means
Code 131052 is an inbound error: a WhatsApp user sent your business a media message, and the platform was unable to retrieve or process that media for delivery to you. You will usually see it inside the incoming messages webhook as an errors array on the message, rather than as a response to anything you called. The text of the message, the sender, and the message ID still arrive; only the media is missing.
Meta's documentation points to error_data.details in that webhook for the specific reason and suggests asking the user to send the file by a non-WhatsApp method. Causes tend to be on the user's side (an unusual file format, a very large file, a client problem mid-upload) or transient on the platform's side.
This is not 131053, which is about media you are uploading to send. Nothing about your configuration produced 131052, and retrying a download of a media ID that never materialized will fail.
Why it happens
- The user's media was in a format the platform could not process.
- The upload from the user's device failed or was interrupted.
- A transient platform fault while fetching the media from the user's client.
- The file exceeded limits the platform applies to inbound media.
How to fix WhatsApp error 131052
- 1Read error_data.details on the inbound webhook message to see the stated reason.
- 2Acknowledge the webhook with 200 and record the message as received without media, so the conversation is not lost.
- 3Reply to the user and ask them to resend the file, or to share it another way such as email or a link.
- 4Do not repeatedly call GET /{media-id}; if the media was never stored there is nothing to fetch.
- 5If the pattern repeats for many users at once, check the platform status page.
How to stop it recurring
Handle inbound messages defensively: treat media as optional, surface a friendly prompt when it is missing, and never let a missing attachment break the conversation flow. Log 131052 occurrences with the details field so you can spot a systemic pattern, and give agents a way to request the file again without leaving the chat. Inbound media sizes and formats the platform accepts are listed in the media limits table; if webhooks themselves are not arriving, that is a different problem - see the webhook debugging guide.
Official reference: Meta for Developers - Cloud API error codes. See all WhatsApp error codes or the WhatsApp limits and quotas.
Related codes
Error 131052 - quick answers
What does WhatsApp error 131052 mean?
Code 131052 is an inbound error: a WhatsApp user sent your business a media message, and the platform was unable to retrieve or process that media for delivery to you. You will usually see it inside the incoming messages webhook as an errors array on the message, rather than as a response to anything you called. The text of the message, the sender, and the message ID still arrive; only the media is missing.
How do I fix WhatsApp error 131052?
1. Read error_data.details on the inbound webhook message to see the stated reason. 2. Acknowledge the webhook with 200 and record the message as received without media, so the conversation is not lost. 3. Reply to the user and ask them to resend the file, or to share it another way such as email or a link. 4. Do not repeatedly call GET /{media-id}; if the media was never stored there is nothing to fetch. 5. If the pattern repeats for many users at once, check the platform…
Can I retry after error 131052?
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 WhatsApp by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.