is there any existing software (web based application), which allows to have all incoming emails (to wildcard email *#domain.com) to be posted via REST API to my web application?
The same thing Tumblr or Posterous does, it assigns you an email (for example trrehret3453#tumblr.com) where you can send text and pictures and it automatically posts it to your blog, I need exactly the same.
Maybe there's a mail server which can do that? I'm running Debian Linux.
Thanks!
Found this service: http://www.emailyak.com, they provide REST API for incoming emails.
Related
I have seen some providers on internet where you can send Whatsapp messages using an API. Its not official WA API integration.
These providers will spawn a instance for you, show you a QR code. You need to scan the QR code in your WA app. Once scan is completed, that instance is added as linked device in your app.
Now they provide an API which you can use to send messages. API accepts instanceId, mobile number and message as query param.
These messages are send using your WA account and number. You can see those sent messages in your app.
Basically everything is happening from your account via web whatsapp but from a remote setup and using an API.
Here are a screenshot to help you understand what I am trying to convey.
Sample API call:
https://DOMAIN-HERE/api/send.php?number=84XXXXxxx&type=text&message=test%20message&instance_id=6XXXXXXXXXX&access_token=XXXXXXXXXXXX
I want to setup something similar. I searched the Internet on how does this work and how I can create my own similar setup but could not find anything.
Can someone please point me in the right direction.
What all these providers are doing is hosting a running instance of a whatsapp web client using your phone number, this is why they ask you to scan the QR code (same as whatsapp web does).
Users of this kind of services must be crazy to allow running an unattended instance of whatsapp against their own phone account, as on the host there's full access to your whatsapp encryption keys, contacts, history of messages,... but the security implications are for a different topic.
If you want to have a headless instance of whatsapp-web like the one they offer, you should have a look at repos like this one here: https://github.com/tulir/whatsmeow (there are others similar, for different languages).
I have a web application / website written in ASP.NET Core. The website is for use by one company and will be accessible over the internet. Because it is for a specific company it therefore has to have authentication for that client only (no public registration).
Is there a service with a C# API that allows me to define what domain is allowed to register and sign in? For example all emails in a specific domain or specific emails in a specific domain e.g. #someCompany.com under google or outlook? I am not yet aware of what email client the customer uses. I am also new to setting up authentication for a web app.
This may seem like a 'whats the best solution' kind of question but what I am asking for is a solution to a very technical problem. There will be opinions on best solution but I think the question is valid here. Happy to be convinced otherwise.
Does bluemix (https://console.ng.bluemix.net/) have any incoming mail system for their apps which is similar to Google App Engine's Receiving Mail system (https://cloud.google.com/appengine/docs/python/mail/receivingmail).
Thanks.
PS: If possible, please share some links so I can begin exploring!!
as already suggested on the previous response Bluemix provide a outgoing email service using SendGrid
https://console.ng.bluemix.net/catalog/sendgrid/
For incoming email service, there is no service provided on Bluemix, but there isn't any limitation in integrating your application on Bluemix with an external email service, using its own POP/IMAP interface
How to integrate your app with an external email service is depending from the language/technology you wish to use, for example with PHP you could use its IMAP extension
http://php.net/manual/en/intro.imap.php
to read from an external service using IMAP or POP3
Moreover using an external email service may allow you to use that service for sending email through SMTP, instead of using SendGrid: for example using PHP runtime you could use
https://github.com/PHPMailer/PHPMailer
to integrate with an external SMTP service (usually available with an email account as well as the POP3/IMAP one)
I am trying to create an interface that alerts us of users doing strange stuff on our websites. One feature would be to present a challenge page to specific ip-addresses. But I could not find a way to do that with the api.
I have found a way to blacklist a specific ip-address, but it would be nice to be able to just challenge them through the api.
You could most certainly do so in the UI (may not be available via the API just yet). The Firewall app settings allow you to block, challenge or whitelist.
We are developing a REST API and, in addition to various resources which developers can access, our application sends information to listener scripts on client servers.
Our API documentation lists all of the "Resources" which client applications can access. That part is easy.
But how should we list the various %???% in which our application will POST content to client listener scripts?
As developers, how would you expect these %???% to be named?
Thanks
Note 1: I've used %???% because I don't know what to call them.
Note 2: First time I post to stackoverflow, so apologies if I've failed to follow protocol.
EDIT
Sorry for the lack of clarity.
Our API receives requests from clients. It also sends requests to clients.
For example, when the client receives a message, we will send that message to their server. Or when the status of one of the messages they sent earlier have been updated, we send the update to their server.
Or, to use Twitter as example (imagining we were Twitter), that when you were mentioned in a tweet, we sent the details of that tweet to your server
When a client sends a request to our API, that is being described as "Accessing a Resource" and the documentation lists "Resources".
But what do we call it when our API sends a request to a client? e.g. API-Originated Method?
Parameters?
I don't care how they are named as long as there is some convention to it!