WhatsApp API error 131021: Recipient cannot be sender
Error 131021 is simple: the recipient number in the request is the business number sending it. WhatsApp won't deliver a message from a number to itself.
Quick answer
You tried to message your own business number. Send to a different number; for testing, use a separate handset.What WhatsApp error 131021 means
Meta documents 131021 as: the sender and recipient phone number is the same, and the fix is to send to a phone number different from the sender.
Why error 131021 happens
Request errors come from the payload, so the cause is usually in how it was built. Look for these first:
- Testing by sending to the business number itself.
- The business number saved as a customer contact, for example from a website form test.
- A mix-up between the from and to fields in an integration.
- A shared test script whose default recipient is the business number.
How to fix error 131021
There is no request change that gets this message delivered; the work is in your data and your audience.
- Use a separate personal handset or test number as the recipient.
- Remove the business number from customer contact lists.
- Check the integration maps the recipient field from the customer, not from the account settings.
- Add a check in your send code that refuses any recipient matching one of your own business numbers.
Should you retry after 131021?
There is nothing to retry: a message to the sending number can never be delivered. Change the recipient.
How error 131021 shows up in InfiQ
If Meta rejects the send straight away, InfiQ's API answers with an HTTP error that carries Meta's own error object: error.code 131021, a message beginning "(#131021)" and Meta's explanation in error_data.details, plus an InfiQ_traceid. Keep the trace IDs with the failed message: they are what support needs to look it up.