if i want to use Whatspp API to send official advertising or greeting.
is it consider abuse of the service?
is there any official way to interface with WhatsApp?
Yes it is abuse of the service to spam people.
And the official way to interface with whatsapp, is to install it on your phone and send messages to your pals. Unofficial APIs to interface with it are available however, but spammers are not supported by the API maintainers.
Related
I'm looking at my options to control the Sonos Port at https://developer.sonos.com/reference/. I read about some UPnP control of other Sonos devices, but I can't seem to find any official information about this online. Is UPnP control of the Sonos Port possible?
Sonos uses UPnP for some calls internally, but we never publicly supported this protocol. We encourage you to use the Control API to control Sonos devices. See Connected Home: Get Started for details. Let us know if you see anything missing that you'd like us to add.
You can control any Sonos device via UPnP. The documentation for this used to be on the musicpartners site but access was exceedingly difficult. much of it is standard UPnP, documented at https://openconnectivity.org/developer/specifications/upnp-resources/upnp/ . There are many open source codebases that use it. It is much more powerful than the documented Cloud API in most regards.
I have searched for the Whatsapp Business API but not found the official Whatsapp business API samples. What are the limitations of media messages and billing. If any one have information please provide.
The WhatsApp Business API Client supports a subset of the features provided by the WhatsApp applications you already know from Android, iOS, Web and other platforms including end-to-end encryption. The difference is that this application can be deployed on a server, providing a local API that allows you to programmatically send and receive messages and integrate this workflow with your own systems (CRMs, customer care, etc.).
You can check the media functionalities here. Also, you can start with the official doc.
I have some questions like how whatsapp server is working, though I read in internet, I want to understand much. And what is XMPP? how it is working, How can I send data through XMPP. how can I integrate XMPP with application, can anyone pls explain?
WhatsApp under the hood?
There are rumors WhatsApp uses a customized version of XMPP. Sources are closed so we can only guess.
Understanding XMPP will however give you all the tools to create your own WhatsApp clone.
What is XMPP?
According to Wikipedia (which hosts further references):
Extensible Messaging and Presence Protocol (XMPP) is a communications protocol for message-oriented middleware based on XML (Extensible Markup Language).
Which is to say that XMPP is an xml based convention for exchanging messages between parties. It's best known implementation is Ejabberd chat server.
XMPP can however be used for other things, among them the web of things.
How to send messages?
Assuming you want to create a chat application, you will need:
An Ejjaberd server up and running.
An appropriate xmpp SDK for you language/framework. Example: Smack for Java or agsXMPP for C#.
A good kick-starting tutorial about how xmpp works can he found here: part one and part two.
There is also the RFC which contains the most comprehensive documentation out there.
As stated in the Google Talk for Developers site, you can use the provided APIs to build a client that connects to the Google Talk service.
I would like to know if it's possible (or it will be in the near future) to build a similar client to the google hangouts.
What we pretend is to build something similar to cloud print, that provides printing services to the cloud, but for audio/video streaming: a camera and microphone would replace the
printer.
Thanks a lot.
Talk and all the XMPP stuff is going to be put down soon.
The new Hangouts infrastructure is proprietary. It only has API to integrate Hangouts into web pages and applications, but no API or protocol to create an alternative Hangouts client software.
https://github.com/tdryer/hangups is a library that does exactly that, with a command-line client for Linux.
https://github.com/xmikos/qhangups is a PyQt-based cross-platform app that aims to provide an open-source alternative to the Chrome-based official desktop app. Unfortunately it's not working at the time of posting, but the author is investigating the issue.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions asking us to recommend or find a tool, library or favorite off-site resource are off-topic for Stack Overflow as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it.
Closed 8 years ago.
Improve this question
I am looking for several SMS api.
Basically to receive sms messages from mobile phones.
Any suggestions?
There are two basic "SMS API's": SMPP and HTTP.
The SMPP interface is a world-wide standard used internally by cellular telephone companies as well as between SMS send/receive clients and those telcos and SMS Aggregators. I recommend reading the SMPP v5.0 specfication. The general international support for SMPP claims "SMPP v3.4 compliance", but operationally, SMPP v5.0 is little changed from 3.4 except that the documentation is much better. The SMPP v3.4 specification document was a bit sparse, and the SMS Forum greatly enhanced the specification document with version 5.0.
SMPP is the specification that documents a means of sending and receiving SMS between two nodes: the ESME or client side, which would be you, and the MC or "telco" side, which would be the telephone company or SMS aggregator with which you contract to be hooked into the international SMS infrastructure.
SMPP is needed if you are implementing for high volume, i.e.: multiple SMS per second. The SMPP protocol is a binary PDU request/response pair protocol that runs over TCP. The fundamental request/response pair protocol is relatively simple, but the SMPP specification has many extensions, and in the real world things get pretty complicated due to the sheer number of extensions and inconsistency in how various features of SMPP are implemented by various software and telcos. Using SMPP requires that you have a daemon / service running continuously to provide the real time SMPP peer communications facility, and cannot be implemented purely within web app code. Integrating SMPP into a web application requires developing a daemon / service to handle the ESME part of the SMPP ESME / MC pair, and then providing some kind of RPC mechanism between that daemon and your web app.
An example of an SMPP Library is Logica. Logica was a pioneer in development of SMPP SMSC's, and has released this library as open source. One of the very few that run on Windows. Most open source SMPP code runs on *nix.
Alternatively, one can use third party SMPP Gateway software. By far the most widely adopted open source SMPP server is Kannel. I know several SMS aggregators that use it. As you are asking about PHP and I presume Linux, integrating with Kannel may be your best bet. I do warn you that it is non-trivial to configure. There are several non-open source ones available too such as the Ozeki Message Server and Nordic Messaging Technologies' Enterprise Message Server (EMG). Both of these offerings provide a more "turn-key" solution than Kannel and may be more appropriate for your uses.
For lower volume applications, it is much simpler to implement an HTTP interface to an SMS Aggregator. There are many SMS Aggregators out there offering HTTP interfaces. There is no universal standard, but nearly all offer a relatively simple GET/POST HTTP interface that is quite simple to integrate into a web app or any software environment where HTTP GET/POST is well supported. The SMS Aggregators also generally offer some file or XML based interface for higher volume sending. As the above reader mentioned, Clickatell is an example of an SMS Aggregator, they are considered "pioneers in the industry." Another example, one I've used is Routo Messaging.
Each SMS Aggregator has their own HTTP API, though most all of them support the same services. Also, most of them offer a few free test credits. I have written code to test with several of them, and it is a simple few hour process, generally less than an hour once you have written one.
If you looking for a sms service provider? You could try Clickatell
If you looking at creating a sms api, look at the Twitter API
You can use SMSSync, a free and open source SMS gateway for Android.
It will receive SMS on your Android Phone, then do a HTTP POST to a URL you specify within the app.
However, note services like these will have a throughput limitation (around 1 sms per 6 sec) and you have to manage the "hosting" of the "SMS gateway". If you could afford, you might want to consider virtual SMS providers such as Nexmo and Hoiio API.
We are using smsapi.pl but so far there is only Polish support (it's gonna probably change quite soon). Maybe you should check this one - you'll find there https specification. They have also mail to sms interface.