According to facebook, as of April 30th 2014 the create_event method is no longer available which I assume means no ability to publish events?
https://developers.facebook.com/docs/apps/changelog
create_event is no longer available.
Is it still be possible using v1.0? (to be phased out April 30th, 2015). I haven't been able to find any examples and I want to publish event on behalf of a facebook page. Is this still possible?
https://developers.facebook.com/docs/graph-api/reference/v1.0/page/events
When I try it I get a depreciation warning and an impersonation for using a token for a page, but it also fails when I use my personal token. Probably because I don't have the create_event permission (despite requesting it, it doesn't show up in the facebook token debugger)
Deprecation warning: The REST API is now deprecated; please use the equivalent Graph API methods instead. See http://developers.facebook.com/blog/post/616/.
=> {"error_code"=>190,
"error_msg"=>"Impersonated access tokens can only be used with the Graph API",
Permissions:
[{"permission"=>"installed", "status"=>"granted"},
{"permission"=>"public_profile", "status"=>"granted"},
{"permission"=>"manage_pages", "status"=>"granted"},
{"permission"=>"publish_actions", "status"=>"granted"}]
Any application that has been active as a 1.0 application will still be able to create events until v1.0 is removed. If you just had a 1.0 application sitting around not doing anything, it probably lost the capability.
Example of an active app: Facebook for iOS can still create events.
Related
I'm creating an app that will allow me to manage my Instagram account, following the guide from here
Now I'm at the App Review stage and I have a conundrum:
theoretically I should not need the pages_messaging permission (the documentation is not mentioning this as required)
that being said, when I make my call to register a callback for Instagram messages `POST /v11.0/{page-id}/subscribed_apps?fields=messages&access_token={access_token} the call will fail with WWW-Authenticate: OAuth "Facebook Platform" "insufficient_scope" "(#200) To subscribe to the messages field, one of these permissions is needed: pages_messaging" (this call is the same they are making in the documentation)
so I've added the pages_messaging permission in my review
now I'm unable to pass review as they keep telling me that I don't need the pages_messaging permission for my use case (managing Instagram messages) - "We determined that your app's use case for the requested permission or feature is invalid or is not needed to support its core functionality."
Hmm.... what am I missing? Any guidance that you can provide?
After further attempts:
we could not find a technical way for not needing the pages_messaging permission
Facebook would not approve this permission for our Instagram app - we got no more details than "invalid or is not needed"
we resorted to actually increasing the scope of our app to also cover Facebook page messages, we re-recorded our demos to showcase interaction with a FB page.
with the new approach we managed to pass the pages_messaging approval process
It feels like we're doing something wrong - we shouldn't have had to support Facebook messages and go through the lengthy process of changing our app just to showcase FB page interaction. Not if we only wanted Instagram support.
Alas, as of October 2021, this is how we moved things along.
Hopefully something will change in the future to make things more clear & transparent in future.
We are building a mobile app on behalf of a corporation and the API needs to be able to return the corporation's Instagram feed. We have found that implementing what should be a simple requirement incredibly difficult.
We need to retrieve the following Instagram post data from the corporation's feed:
image url
caption
url to post
timestamp
With this in mind we identified that we need to use the Instagram Graph API which means there are strict requirements around permissions.
Note: We are open to using any method that returns us the required data.
Using the Instagram Graph API we need to use the following endpoints:
Media (to get a list of the latest IG Media objects for a user)
IG Media to get detail about each media object
This works fine but the problem lies with getting a long-lived User Access Token. To get this kind of token we need the instagram_graph_user_media permission. The Long-Lived Access Tokens documentation says:
Long-lived tokens are valid for 60 days and can be refreshed as long as they are at least 24 hours old but have not expired, and the app user has granted your app the instagram_graph_user_profile permission.
How can the app user (the corporation) grant the app the permission? As I mentioned this is for an app on behalf of a corporation.
Any help here would be really appreciated!
Thanks
Did you go through the App review process in Facebook? Whenever there are user permissions involved, you need to go through the App review process for your app. Even though you don't use user permissions, some user permissions are pre-requisites for some business permissions.
Read the article here for more information: https://developers.facebook.com/docs/app-review
Unsure if this will be of any help, but battling exactly the same thing today came across this and it made for some intresting reading https://solrevdev.com/2020/05/28/instagram-basic-display-api.html
I'm trying to make an app that will allow blog posts from my website to be published to a Facebook page which I am the admin of.
Obviously I need the publish_pages and manage_pages permission to do this and I need to provide a screencast showing how these permissions will be used.
From my understanding, I can still publish a post from my website to my Facebook page while the app is in development mode as long as I am the admin of the page (which I am) but the posts won't be visible to the public.
So I complete the authentication process here (see below).
Finally I add my blog post. However, I then get the following as an error message
"(#200) The permission(s) publish_actions are not available. It has been deprecated. If you want to provide a way for your app users to share content to Facebook, we encourage you to use our Sharing products instead."
Would this be an issue with the system I am using, making a depreciated API call?
Deprecation:
The publish_actions permission will be deprecated. This permission granted apps access to publish posts to Facebook as the logged in user. Apps created from today onwards will not have access to this permission. Apps created before today that have been previously approved to request publish_actions can continue to do so until August 1, 2018. No further apps will be approved to use publish_actions via app review. Developers currently utilizing publish_actions are encouraged to switch to Facebook's Share dialogs for web, iOS and Android.
From now on you can only publish to your own facebook profile not facebook page. For more information you can visit their official documentation
I have a app with some permissions that only exist on API V1.0 (I'm working on migrating them to V2.2),
but in the meantime I need a new permission "publish_actions". If I send a review to Facebook I can still use the API V1.0 permissions or I can't? how can keep my permissions "read_stream" of API V1.0 and add a new one?
Best,
You send in specific permissions, so you can just send in publish_actions without read_stream and it should be no problem. Just keep in mind that you will lose access to read_stream completely after April 2015. I assume you know that it will only get approved for platforms without a Facebook client.
From reading the open graph beta auth doc it seems like the intent of authenticated referrals is to provide tighter site integration with facebook for open graph beta Actions we define. However getting those permissions still seems to be tied to a user session/token which expires after 90min or so.
Is there a way to make calls to our open graph beta Actions without have to re-authenticate every 90min without request full offline permissions. It seems ridiculous to expect to re-authenticate that frequently for a defined Action.
No, you'll have to request full offline access. (Everyone else is doing it.)