evolution-api
evolution-api copied to clipboard
Pairing Code
Welcome!
- [x] Yes, I have searched for similar issues on GitHub and found none.
What did you do?
Criei a instância whatsagenda-131 e apliquei configurações para priorizar pairing code:
POST /instance/create
POST /settings/set/whatsagenda-131 com:
{ "preferQr": false, "preferPairingCode": true, "linkingMode": "pairing", "qrcode": true, "pairing": true, "mode": "pairing" }
Disparei o pareamento usando as bases local e manager, testando GET e POST de /instance/connect/whatsagenda-131, sempre com o número em E.164:
Flags testadas: type=pairing, pairing=true, mode=pairing, loginType=pairing, usePairingCode=true, method=code.
Fiquei consultando /instance/connect/whatsagenda-131 e /instance/connectionState/whatsagenda-131 por ~90s e escutando webhooks em /webhook/evolution para QRCODE_UPDATED e CONNECTION_UPDATE.
Também testei endpoints legados/alternativos que alguns forks expõem (GET/POST): /instance/pairing/whatsagenda-131, /instance/whatsagenda-131/pairing, /instance/code/whatsagenda-131, /instance/whatsagenda-131/code.
What did you expect?
Ao solicitar o modo de pareamento com número válido em E.164 (loginType=pairing / usePairingCode=true), esperava receber um código de pareamento de 6 dígitos (ex.: 123456) na resposta do /instance/connect ou nos eventos de webhook (CONNECTION_UPDATE/QRCODE_UPDATED).
What did you observe instead of what you expected?
{ "success": true, "count": 1, "pairingCode": null, "qrOrCode": "data:image/png;base64,iVBORw0KGgoAAA..." }
Screenshots/Videos
No response
Which version of the API are you using?
2.2.0
What is your environment?
Windows
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
No response