Webwhatsapp-wrapper: [Suggestion] REST API

[coolnickname]

I'd like to use this software in my project but am not really experienced with the language.

Please consider making a REST API of this project for us who want to use it from another language :)

[mukulhase]

This project is for educational purposes only. It should be self-hosted for personal devices only. Not intended for online deployment and multiple devices. Hence, we should not create an API for this.

[chriso0710]

I think having a (simple) REST API would be cool :-)

Although this will be quite a lot of work, so it would be out of scope for this project:

• API controller, which handles all http requests
• database
• background processing/worker for outgoing webhooks
• wrapper and selenium controller, with docker remote control for scaling
• status, heartbeat
• media attachment store
• ...

[modcastro]

Hi @chriso0710 any advance about this ? You need help to start ?

[group2tts]

You can use api-messenger.com, but you have to pay for it.

[chriso0710]

@modcastro Building an API for this project was more an idea/concept rather than a real plan :-)

I moved to Twilio Whatsapp. Still in beta, not free, but very easy to use and the (sandboxed) API works great!

[mdedirudianto]

I built something like that. It just need patience to compose everything into REST API. I built it using Node js (Hapi) and Puppeteer. Let's talk in case you're interested :)

[fmsouza]

I think it would make much more sense to make it as a PubSub API instead, would be even easier.

Eg.: Whenever an unread message is detected, post it to unreadmessages channel. When the bot got a reply, post it to the reply channel so the server can receive it and send back to the conversation.

It'd be a good abstraction of all this work, and would allow devs to build APIs in every language. The only con would be the need for having the two services up and running.

[coolnickname]

I think it would make much more sense to make it as a PubSub API instead, would be even easier.

Eg.: Whenever an unread message is detected, post it to unreadmessages channel. When the bot got a reply, post it to the reply channel so the server can receive it and send back to the conversation.

It'd be a good abstraction of all this work, and would allow devs to build APIs in every language. The only con would be the need for having the two services up and running.

If anyone would decide to make this in pubsub I would definitely use it, but honestly I think a REST API would be better because otherwise you're just adding another relay to the packet stream.

[marcelocecin]

Flask based API to work with webwhatsapi

[coolnickname]

Closing since there is an API now. For discussion of the API please open a new issue.