In our application users can synchronize his friends based on facebook relationships. User hit "sync" button in application, we call "friends" in graph api, and receive all user that use our application and synchronize friends in our application.
Is there a way to synchronize continuously his friends periodically, for example once a week, without user participation(no need to hit the button)?
Related
Lets say, I have a bot game which offers a user to share the result screen with other users of messenger. For this reason messenger has a 'Share' button. When user clicks on Share Button Facebook offers to choose which users to share with.
The question is how to get a callback if users successfully shared the screen with at least one user.
I am referring following links to the Facebook documentation for real time subscription.
https://developers.facebook.com/docs/graph-api/webhooks
https://www.facebook.com/marketingdevelopers/videos/883648801749520/
For the page, the graph api v2.6/{page-id}/subscribed_apps is used for subscribing the page to the app.
I am looking for the graph api for subscribing user to the app for the real time changes.
I am looking for the graph api for subscribing user to the app for the real time changes.
There is no such endpoint.
For updates from users, you don’t need to create an individual subscription for every single one, like you need to do with pages.
You just do the general setup, that subscribes your app to updates for certain fields/edges of the user object. You then will get updates automatically for the users of your app, when a change on those happens (provided that the users gave your app the necessary permissions to read that kind of data.)
I am trying to make a Facebook app that reads the events of an user (who permits the app to do so), and then shows a list of events. The user then chooses one of the events, and the app automatically sends a custom message or notify via Facebook notifcations to the guests of that event. Can I achieve this at all under the FB Graph API?
I realized that /invitable_friends is no longer supported (unless the app is a Canvas game) - however I am not sure if this will prevent me from doing the above
For my iPhone app, an user can logged in using Facebook, then the app can get list of friends that already on the app. Now I am wondering - when should the user's Facebook friends be pulled down. Should it be the time when the user start using the app and login with Facebook? Or should it be done periodically in the background thread? Or should it actually be done on my apps' web service side (with the access token received and sent over from the iPhone app) What's the best practice to go with?
The main concerns are
total # of friends could be a large number, which would require a lot of network traffic
time processing
A couple of options:
From your comments below your question, cache friends lists for a minimum of 24 hours. Friend listings rarely change often (unless the user is under 25 years of age, then it might change more frequently...statistically speaking).
Another option you can also subscribe to a user using the Real Time API. Store their friend information on your server and when Facebook tells you they've added a new friend you add it to your data store. Then you can query your own server rather that hitting the Graph API.
I am working on an app that is integrating the Facebook OpenGraph. I'm trying to subscribe to Real-Time Updates so that I can have my app automatically updated whenever friends of my users check in somewhere.
It appears that Connections are available in realtime with the User Object and checkins are a connection but through the OpenGraph Explorer I can only see checkins where people have tagged myself.
When you subscribe to realtime updates, Facebook only sends you data about the users who have taken actions in your app, not their friends.
But you will get all updates about a user which has added your app - which includes when one of their friends tags them in a checkin - along with that user's own checkins.