You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the following error: Unrecognized field "field" (class com.whatsapp.api.domain.webhook.WebHookEvent), not marked as ignorable (2 known properties: "entry", "object"])
And it's different. This is expected due to the diffent versions (I'ts stated that the library supports 16)? Can the Webhook class be extended somehow to support this new type of payload?
Thanks in advance Mauricio.
The text was updated successfully, but these errors were encountered:
Hello and welcome! We're glad to see that you've opened your first issue. We appreciate your contribution and would love to hear more about the problem you're experiencing. Our team is actively monitoring this repository and we will do our best to respond to your issue as soon as possible. Thank you for using our project and we look forward to working with you!
I believe the JSON you posted is incomplete. In the payload, there are the fields 'object' and 'entry.' See the example below, which I also obtained from the v19 API
Hello. I'm currently building an application that needs to communicate with whatsapp api. In the meta panel, the version of the api it's 19
I'm trying to deserialize the test payload of a message webhook provided by meta, using the WebHook class.
I get the following error:
Unrecognized field "field" (class com.whatsapp.api.domain.webhook.WebHookEvent), not marked as ignorable (2 known properties: "entry", "object"])
I saw the payload you provided in the example: https://github.com/Bindambc/whatsapp-business-java-api/blob/main/src/test/java/com/whatsapp/api/examples/WebHookExample.java
And it's different. This is expected due to the diffent versions (I'ts stated that the library supports 16)? Can the Webhook class be extended somehow to support this new type of payload?
Thanks in advance Mauricio.
The text was updated successfully, but these errors were encountered: