I got an error about auto replay not coming, I tested it through webhook and I got results in 2 different formats as below

---

Result 1

curl --request POST \

--url 'xxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 577' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"hio","bufferImage":null,"from":"91xxxxxxxx89","name":"Hit","participant":"91xxxxxxxx89@c.us","data":{"key":{"remoteJid":"91xxxxxxxx89@s.whatsapp.net","fromMe":false,"id":"xxxx","senderLid":"xxxxx@lid"},"messageTimestamp":xxxx,"pushName":"Hit","broadcast":false,"message":{"extendedTextMessage":{"text":"HIO","contextInfo":{"mentionedJid":[],"groupMentions":[],"ephemeralSettingTimestamp":{"low":1764504638,"high":0,"unsigned":false},"disappearingMode":{"initiator":0,"trigger":1,"initiatedByMe":false}},"inviteLinkGroupTypeV2":0}}}}'

---

Result 2

curl --request POST \

--url 'https://xxxxxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 419' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"","bufferImage":null,"from":"169153075896473","name":"jjay61065","participant":"[email protected]","data":{"key":{"remoteJid":"169153075896473@lid","fromMe":false,"id":"ACCD04A323EE1C161B97EBB0EFA8CFCA","senderPn":"[email protected]"},"messageTimestamp":1765459355,"pushName":"jjay61065","broadcast":false,"messageStubType":2,"messageStubParameters":["No matching sessions found for message"]}}'

---

In Result 1, the response is found, the correct number is in from (91xxxxxxxxx89), but in Result 2, the from is in '169153075896473', something like this

12 hours ago, Hit Solanki said:

I got an error about auto replay not coming, I tested it through webhook and I got results in 2 different formats as below

---

Result 1

curl --request POST \

--url 'xxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 577' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"hio","bufferImage":null,"from":"91xxxxxxxx89","name":"Hit","participant":"91xxxxxxxx89@c.us","data":{"key":{"remoteJid":"91xxxxxxxx89@s.whatsapp.net","fromMe":false,"id":"xxxx","senderLid":"xxxxx@lid"},"messageTimestamp":xxxx,"pushName":"Hit","broadcast":false,"message":{"extendedTextMessage":{"text":"HIO","contextInfo":{"mentionedJid":[],"groupMentions":[],"ephemeralSettingTimestamp":{"low":1764504638,"high":0,"unsigned":false},"disappearingMode":{"initiator":0,"trigger":1,"initiatedByMe":false}},"inviteLinkGroupTypeV2":0}}}}'

---

Result 2

curl --request POST \

--url 'https://xxxxxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 419' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"","bufferImage":null,"from":"169153075896473","name":"jjay61065","participant":"[email protected]","data":{"key":{"remoteJid":"169153075896473@lid","fromMe":false,"id":"ACCD04A323EE1C161B97EBB0EFA8CFCA","senderPn":"[email protected]"},"messageTimestamp":1765459355,"pushName":"jjay61065","broadcast":false,"messageStubType":2,"messageStubParameters":["No matching sessions found for message"]}}'

---

In Result 1, the response is found, the correct number is in from (91xxxxxxxxx89), but in Result 2, the from is in '169153075896473', something like this

You can get these 2 results in the following way

1. The result of WhatsApp Web to WGateway is that the cellphone number will be read.

2. the second result is from android device to wagateway phone number is hidden as LID ID

I have explained this problem above

If there is any solution to this, please share it with me.

33 minutes ago, Hit Solanki said:

If there is any solution to this, please share it with me.

waiting for updates from the developer

Kirim Pesan Melalui API Gagal terus, tetapi Auto reply terkirim. Mohon bantuan nya.
API Key sudah di generate ulang, dan tetap saja tidak berfungsi.

Edited December 12, 2025Dec 12 by SkyLab

whstapp business ban all time

2 hours ago, alal said:

whstapp business ban all time

Who said that?

What is the reason why the message on the webhook is also showing blank, if you have any solution, please let me know.

{"message":"","bufferImage":null,"from":"169153075896473","name":"jjay61065","participant":"[email protected]","data":{"key":{"remoteJid":"169153075896473@lid","fromMe":false,"id":"ACCD04A323EE1C161B97EBB0EFA8CFCA","senderPn":"[email protected]"},"messageTimestamp":1765459355,"pushName":"jjay61065","broadcast":false,"messageStubType":2,"messageStubParameters":["No matching sessions found for message"]}}

On 12/11/2025 at 5:04 AM, cvcahaya bukitqof said:

WhatsApp telah menyelesaikan pembaruan Local Identifier (LID). LID adalah ID unik yang ditetapkan untuk setiap pengguna (seperti JID) tetapi bukan nomor telepon (PN).

Fungsi: Tujuannya adalah untuk memastikan anonimitas pengguna dalam grup besar (misalnya, menampilkan +43.......21 alih-alih nomor telepon) dan mengakomodasi sistem username (@username) yang akan datang.

Prioritas: WhatsApp (dan Baileys) kini memprioritaskan penggunaan LID untuk mengidentifikasi dan berkomunikasi dengan pengguna. Nomor telepon (PN) dianggap kurang andal.

Perubahan di Baileys:

• MessageKey kini memiliki kolom remoteJidAlt (untuk DM) dan participantAlt (untuk Grup) yang akan berisi PN jika ID utamanya adalah LID (dan sebaliknya).

• Tipe GroupMetadata kini memiliki pasangan ID: owner (LID) dan ownerPn (PN).

• Fungsi isJidUser dihapus dan diganti dengan isPnUser (karena baik PN maupun LID sama-sama JID).

• Baileys menyediakan store internal sock.signalRepository.lidMapping untuk memetakan PN $\leftrightarrow$ LID.

Perubahan Arsitektur Proyek (ESM)

• Pindah ke ESM: Baileys versi 6.8.0 dan seterusnya meninggalkan CommonJS dan beralih ke ESM (ECMAScript Modules).

• Implikasi: Jika Anda menggunakan Baileys dalam proyek Node.js, Anda harus:

  • Mengubah proyek Anda menjadi ESM (disarankan) dengan menambahkan "type": "module" di package.json dan menggunakan import alih-alih require().

  • Atau, menggunakan Dynamic Import (await import('baileys')) dari dalam CommonJS.

Penghapusan Pengiriman ACK

• Tindakan: Baileys tidak lagi mengirimkan ACK (Acknowledgment) pada pengiriman pesan yang sukses.

• Alasan: WhatsApp tampaknya melarang pengguna yang melakukan tindakan ini.

Protokol Buffers (Protobufs)

• Reduksi Ukuran: Untuk mengurangi ukuran bundle Baileys, beberapa metode di paket proto telah dihapus.

• Penggunaan: Hanya menyisakan .create(), .encode(), dan .decode(). Anda harus menggunakan utilitas BufferJSON saat encoding atau decoding objek berbasis proto untuk mencegah error.

apakah akan ada update yang bisa menyesuaikan perubahan baru ini?

hal ini saat ini sangat menggangu sekali nomor pengirim manjadi xxxxxxxxx@lid, sehingga pesan tidak terkirim..mohon dilakukan update segera mr @Magd Almuntaser

On 12/11/2025 at 9:59 PM, Hit Solanki said:

I got an error about auto replay not coming, I tested it through webhook and I got results in 2 different formats as below

---

Result 1

curl --request POST \

--url 'xxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 577' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"hio","bufferImage":null,"from":"91xxxxxxxx89","name":"Hit","participant":"91xxxxxxxx89@c.us","data":{"key":{"remoteJid":"91xxxxxxxx89@s.whatsapp.net","fromMe":false,"id":"xxxx","senderLid":"xxxxx@lid"},"messageTimestamp":xxxx,"pushName":"Hit","broadcast":false,"message":{"extendedTextMessage":{"text":"HIO","contextInfo":{"mentionedJid":[],"groupMentions":[],"ephemeralSettingTimestamp":{"low":1764504638,"high":0,"unsigned":false},"disappearingMode":{"initiator":0,"trigger":1,"initiatedByMe":false}},"inviteLinkGroupTypeV2":0}}}}'

---

Result 2

curl --request POST \

--url 'https://xxxxxx/' \

--header 'accept: application/json, text/plain, /' \

--header 'accept-encoding: gzip, compress, deflate, br' \

--header 'content-length: 419' \

--header 'content-type: application/json; charset=utf-8' \

--header 'user-agent: axios/1.12.2' \

--data-raw '{"message":"","bufferImage":null,"from":"169153075896473","name":"jjay61065","participant":"[email protected]","data":{"key":{"remoteJid":"169153075896473@lid","fromMe":false,"id":"ACCD04A323EE1C161B97EBB0EFA8CFCA","senderPn":"[email protected]"},"messageTimestamp":1765459355,"pushName":"jjay61065","broadcast":false,"messageStubType":2,"messageStubParameters":["No matching sessions found for message"]}}'

---

In Result 1, the response is found, the correct number is in from (91xxxxxxxxx89), but in Result 2, the from is in '169153075896473', something like this

saya mengalami hal yang sama juga, kebetulan saya sangat memerlukan Payload Webhook yang sesuai untuk menjalankan n8n saya, mr @Magd Almuntaser heeeaallp pleasee..

Mr @Magd Almuntaser If possible, please resolve the webhook issues, our customers are very frustrated.

On 12/8/2025 at 2:58 PM, ADS SOLUTIONS said:

Ai chat bot not working help me

Any solution to fix the AI not responding?

amazing script amazing system... but always have someone that gain acces to my server....... security is bad... sorry :/// i hope developer support this and maintenance with a yearly fee so we can use it :///

@Juxhin It would be perfect if they charged a recurring fee for official developer support, since their CRM is very well-built; the only issue is the lack of support.

On 12/12/2025 at 11:05 PM, Hit Solanki said:

What is the reason why the message on the webhook is also showing blank, if you have any solution, please let me know.

{"message":"","bufferImage":null,"from":"169153075896473","name":"jjay61065","participant":"[email protected]","data":{"key":{"remoteJid":"169153075896473@lid","fromMe":false,"id":"ACCD04A323EE1C161B97EBB0EFA8CFCA","senderPn":"[email protected]"},"messageTimestamp":1765459355,"pushName":"jjay61065","broadcast":false,"messageStubType":2,"messageStubParameters":["No matching sessions found for message"]}}

hi, in webhook API codes, what I did just DROP/IGNORE for any incoming webhook with blank message
of course this is temporary solusion, while waiting for any update.

1 hour ago, Profit BinaryBot said:

hi, in webhook API codes, what I did just DROP/IGNORE for any incoming webhook with blank message
of course this is temporary solusion, while waiting for any update.

Please guide me on how I can improve it?

Tidak bisa scan QR lagi ya.. Tiba tiba disconnect

tinggalin aja thread ini, sebab yang developer versi custom script ini udah bilang mau tinggalin script ini.
kalo ga salah orang nya ada di komunitas juga, awalnya dia bikin ini sebagai mpwa customize yang berbayar, tapi banyak yang pada pake aja sedangkan baileys yang dia pake bukan dari whiskey jadinya butuh perawatan. kan capek harus merawat yang butuh effort waktu dan pikiran tapi ga ada user yang perhatian sama yang merawat dan taunya pada make. wkwkwk

But this is just my assumption.

1 hour ago, Ultraboot said:

tinggalin aja thread ini, sebab yang developer versi custom script ini udah bilang mau tinggalin script ini.
kalo ga salah orang nya ada di komunitas juga, awalnya dia bikin ini sebagai mpwa customize yang berbayar, tapi banyak yang pada pake aja sedangkan baileys yang dia pake bukan dari whiskey jadinya butuh perawatan. kan capek harus merawat yang butuh effort waktu dan pikiran tapi ga ada user yang perhatian sama yang merawat dan taunya pada make. wkwkwk

But this is just my assumption.

Apalagi banyak pembaruan dari pihak whatsapp dan gemini yang limit 🤣

36 minutes ago, Imanudin said:

Apalagi banyak pembaruan dari pihak whatsapp dan gemini yang limit 🤣

yes.. jadi lebih rekomendasi pakai mpwa versi asli dari m-pedia aja.

54 minutes ago, Ultraboot said:

yes.. jadi lebih rekomendasi pakai mpwa versi asli dari m-pedia aja.

Sebuah kemunduran dong kalau balik ke mpwa m-pedia 🤣

8 minutes ago, Imanudin said:

Sebuah kemunduran dong kalau balik ke mpwa m-pedia 🤣

ya nggak lah, tinggal di custom sendiri kalau emang mau beda dan mau fitur-fitur yang dibutuhkan tersedia.

Just now, Ultraboot said:

ya nggak lah, tinggal di custom sendiri kalau emang mau beda dan mau fitur-fitur yang dibutuhkan tersedia.

di encrypt 😌

Just now, Imanudin said:

di encrypt 😌

dulu pernah ada yang share versi yang ga di encrypt, kalau pakai itu untuk update di local tetep bisa dan file baru nya tetep ga di encrypt. kalo ga salah ya.

4 minutes ago, Ultraboot said:

dulu pernah ada yang share versi yang ga di encrypt, kalau pakai itu untuk update di local tetep bisa dan file baru nya tetep ga di encrypt. kalo ga salah ya.

Ada 😆