Can anyone tell me what is the equivalent of status.get of the Old REST API in the new Graph API.
The page http://developers.facebook.com/docs/reference/rest/ says "If you are new to the Facebook Platform, we recommend you use our new Graph API instead." so I'm trying to figure out the newer version.
Basically, what I want is to retrieve the status messages that a user has updated.
Thanks
http://graph.facebook.com/<USER_ID>/statuses
You can also use FBML or FQL.
Related
I am trying to use the Facebook Graph API to GET Instagram metrics such as post impressions. I was able to successfully pull my Instagram Follow Count by using this query
{instagram_user_id}?fields=follow_count
When I try to query my post impressions with
{instagram-media-id}/insights?fields=post_impressions
nothing shows up. Am I missing something or have I possibly not requested the correct permissions?
I am trying to follow the documentation at the below link. Is it even possible to pull the impressions through the Facebook Graph API?
https://developers.facebook.com/docs/graph-api/reference/instagram-media/insights/
Thanks!
I believe that it wasn't possible to pull insights using the older version of the API.
However now it is possible as instagram / facebook just released a new version of their Graph API that includes insights. The request would be:
v2.10/{instagram_media_id}/insights?metric=impressions
The new documentation can be found here
Have you tried to specify "period" parameter? By default it might not be a "lifetime" and if you did not generate any impression recently you will see nothing (empty array i assume). In case you missing some permissions, Facebook will make you aware in response.
How would I GET landmarks, like new job/ married/ moved, etc. from the facebook (or any other 3rd party) API??
I'm trying to make a timeline of 'big' moments using facebook, specifically on iOS
I found an answer here stackoverflow.com/questions/12400522/… that lets you use FQL instead of the graph API to send requests and then returns more exact information.
Facebook's FQL reference is here: https://developers.facebook.com/docs/technical-guides/fql/
Is it possible to create a Facebook Life Event via Open Graph API? Is it?
No, it's not possible. If it's not in roadmap and it's not in the documentation (documentation should reflect the latest changes to the API now, it's dynamically updated), then it's not available.
I am developing a Facebook application that will use Facebook events.
I want to be able to create and edit event as well as invite users friends to the event.
I prefer to use the new Graph API to handle all connections with Facebook and I many ways I am able too, but, the Graph API cannot send invites.
I saw that the Old Rest API got far more ways to interact with Facebook so I tried to use both systems on the same time but when I send the Access token that I have created with the Graph API a long with a call to the old API it says "Invalid OAuth 2.0 Access Token".
My question is, is there a way to convert the new Graph API access token to be used with the old rest API? Is there perhaps another way to get both systems to work in the same application?
Please help! All input are welcome.
I´d recommend against the old REST api. Support will be canceled sooner or later and then you will have to port to graph api anyway.
To send invites to your app you can use fbml/xfbml. try the http://developers.facebook.com/docs/reference/fbml/multi-friend-selector togehter with the JavaScript SDK as described here: http://www.takwing.idv.hk/tech/fb_dev/jssdk/learning_jssdk_11.html
good luck!
I started developing a Facebook app using the new Graph API.
I want to check if I have certain permissions, (say publish_stream for example) for a certain user. I know that the old REST API had users.hasAppPermission, but I don't see anything parallel to that in the new Graph API.
How can I do this?
You will need to run FQL on permissions table. If you are using JS SDK you can run it with FB.Data.query().
Yes. In the new Graph API use "/[user]/permissions". See also detailed explanation here and here.