Can I share to Twitter/Facebook after a check-in? API for checkings/add contains a parameter broadcast which allows to sharing to connected Twitter account. But I don't know this information when sending a check-in, sharing to Twitter needs to be optional action after a check-in.
I have tried another checkings/add request with different broadcast afterwards, but it gets ignored (merged with previous check-in and it's not shared).
I need this for my app Glasquare (Foursquare for Glass). Implementation of my own Twitter/Facebook sharing would be tricky for me and the users, because it's not easy to authenticate a third party app on Glass (Glass doesn't have any keyboard to type username/password)
Unfortunately this functionality isn't currently supported in the Foursquare API. Perhaps have app-level user settings to let them toggle their broadcast option?
Related
I'm trying to send a notification out using Google Chats. But I have a few problems with the documentation I've been able to find:
It requires me to have a paid service account, which I do not have, and will not be getting
It requires using a chat bot, which (in my understanding) needs to be added to a room, and cannot just send out messages
Chat bots can't send out messages directly to personal accounts?
I'm already using Google OAuth2 authentication to access another Google API, so I'd like to use a Google API to send messages directly from the authenticated account. How would I do that?
So far:
All the documentation I can find is about making a chat bot.
I've considered some alternatives to sending out messages, but due to corporate device restrictions that will not be changing, google chats is my best option.
At the moment what you're trying to do is not possible, for multiple reasons.
You may know this already, but Google Chat is an upgrade to their old "Classic Hangouts" chat. In Google's own words, this is focused on enterprise (i.e. paid) accounts. While personal accounts are also able to upgrade and get some of the benefits, their documentation shows that Google Chat for personal accounts is very similar to the old Hangouts and most of the new features are meant for the paid accounts. This also includes the use of bots.
As you've observed, the Chat API currently only has methods to create and manage bots. There are no methods to send messages as your own account. This could be to prevent spam or because their Chat API is relatively new, since the Classic Hangouts did not have an API, and Chat hasn't fully replaced it yet. Even then, given that Chat is "enterprise-focused", it is uncertain whether or not personal accounts would get access to any new API features.
You could try to post feedback on their issue tracker or request the feature to see if you get a response, but for an immediate solution you may want to just use the Gmail API to send a regular email or reconsider the other alternatives that you had in mind.
For example, let’s say I wanted to create my own Instagram API (I’m aware Instagram has an API but let’s imagine they didn’t and I wanted to make my own for them). Could I make one to post, like photos, DM, etc? Or does Instagram themselves need to make an API to allow me to access these functionality and commands?
You can certainly make one but you could be in violation of the service's Terms of Service (ToS). If you violate the ToS, the service could shut down your access.
In the scenario where someone publishes an unofficial SDK, it can be taken down under DCMA. For example, such a private Instagram API was made and published on GitHub before Facebook filed a DCMA claim with GitHub to have it taken down:
Facebook DCMA Takedown Request:
https://github.com/github/dmca/blob/master/2020/01/2020-01-22-facebook.md
Discussion:
https://news.ycombinator.com/item?id=22209892
Here's an excerpt from the Takedown Request:
Instagram-API repository (and its forks) offers a tool expressly designed to circumvent the Company’s effective access controls and protection measures by avoiding, bypassing, removing, deactivating, or impairing the Company’s technological measures without the authority of the copyright owners or the Company. Mgp25’s Instagram-API is designed to emulate the official Instagram mobile app when communicating with Instagram’s servers, which allows users of mgp25’s Instagram-API to send and receive data (including receiving legitimate, copyrighted posts by Instagram’s users) through Instagram’s private API. Mgp25’s Instagram-API also permits other types of access to, and collection of, Instagram’s users’ copyrighted works in manners that exceed the scope of access and functionality that would be permitted by a user with a legitimate, authorized Instagram account.
I am trying to collect all media that use a specific hashtag from Instagram to run a hashtag contest for an event.
I have tried the Instagram API and I can collect the media through it, while in sandbox mode, but only the public ones. I want to be able to collect also those belonging to PRIVATE users that I already follow.
If my application passes the review process, will I be able to see the media that people I follow have posted? (like on the official Instagram APP?) Has the review process indeed paused due to the latest news?
Is there any 3rd party APP that has already been reviewed or any other solution that allows me to access the private data?
I just want to check for media that use a specific hashtag every 15-60 seconds and save them to a database based on submission time.
Edit: Another option would be to publish a minimal application that only reads the users' self media. This way everyone who participates would need to provide access to my Application and then I would be able to verify if they have posted using the hashtag.
My main concerns are:
Are applications requiring only the basic scope reviewed?
Can an application like this pass review? In the API terms it states they do not accept apps for one-off projects (like a campaign)*
Instagram is not accepting any new apps that use the public_content permission for review. So you won't be able to get your app out of Sandbox mode if you are using that permission. There are a few 3rd party apps that have been granted permission for that, but even they will stop working when the public_content permission is deprecated in December 2018.
As per https://instagram.com/developer and https://www.instagram.com/developer/changelog
Another option would be to use something like the hashtag campaign feature from SnapWidget that could be used to create a contest.
I am developing a new feature, which will listen to tip notifications on venues, and I am having trouble to test it.
As far as I could check, to create a venue, and subscribe it on my foursquare app, I need to pay.
Is there any alternative to simulate or test, tip notifications?
On the app there is a test button, that only send checkin notifications.
I need to test it on dev environment before sending an untested code to production.
You can only get venue notifications for venues that you are a manager of.
See info on the venue push API here. https://developer.foursquare.com/overview/realtime
This API is designed for applications whose users are managers of
venues, allowing the application to get a real-time view of activity
at their venues. The Venue Push API will push to your application
content from venues managed by any of your application's authorized
users (or at a home venue that was created by one of your
application's authorized users). Supported venue content are
check-ins, likes, tips, and photos at the venue.
It's important to stress that in order for your app to see pushes for
a venue, at least one of this venue's managers must have authorized
use of your app, otherwise you may see “Your app can't see pushes from
that venue” errors.
After exchanging several emails with api#foursquare.com, they set me as a manager of a venue I created on http://foursquare.com/add-place, and finally I could move on with my tests.
I strongly recommend to Foursquare to create some kind of test for all possible Real Time API notifications, or create some kind of sandbox.
Thanks.
We are doing an integration with DocuSign where users can submit documents stored in our system to DocuSign to get the documents signed. We have the DocuSign Connect feature working in our demo account. We can process messages from DocuSign successfully.
We were concerned that getting users to add a Connect Configuration themselves may be too challenging for some and it will be error-prone.
I see now in the documentation that it is possible to automatically get DocuSign to push notifications by passing the information in the EventNotification attribute when we call createEnvelope. Is this an acceptable way to get push notifications from DocuSign? Will this cause issues with getting the integration certified?
Is there any other way to get Connect configured easily in customer accounts?
This is an old question, but I wanted, for the record to have answers, since it's important to anyone who may be reading this.
We see now in the documentation that it is possible to automatically
get DocuSign to push notifications by passing the information in the
EventNotification attribute when we call createEnvelope. Is this an
acceptable way to get push notifications from DocuSign?
Yes, it is. It's a very good way in fact, to reduce polling and make your app better. We highly recommend that you use EvenNotification and sign-up for events going through a webhook to your app such that you can handle them in your code only when they occur, instead of polling DocuSign APIs repeatedly.
Will this cause issues with getting the integration certified?
The opposite is true. If you use polling you may have issues being certified. Using connect events with a webhook is one way to avoid the need for excessive polling which could cause issues with the certification.
Is there any other way to get Connect configured easily in customer
accounts?
You can configure connect like you suggested using EventNotification at the envelope level. This approach works well for ISVs since you don't need your customers to have admin access to their accounts.
The other option is account-level connect configuration, which does require admin level access and there are some other limitations. This approach adds the connect webhook for all envelopes in the account. So it may or may not be better, depending on your scenario.