I am attempting to get events from a specific page, through a person who is administrator of the site and the host of the events. This will not work unless i make the administrator a tester on my Facebook App. Anyone who knows which permission i am missing?
I have the following permissions already:
business_management
manage_pages
public_profile
publish_pages
user_friends
EDIT
Facebook API Explorer
Facebook API Explorer
Access Token Info
https://developers.facebook.com/docs/graph-api/reference/page/events:
This is a restricted edge. You cannot request access at this time.
Facebook has restricted this to specific partners; as a normal 3rd-party app developer you can not get page events at this time.
Related
I have an app that programmatically make post on a configured Facebook Page.
My app obviously have both the manage_pages and publish_pages permissions approved and I'm using pages access token
Everything work well since now, but recently when I POST on page feed
https://graph.facebook.com/v3.1/234002440799692/feed
I get this error:
{"error": {
"message":"(#200) Requires either publish_to_groups permission and app being installed in the group, or manage_pages and publish_pages as an admin with sufficient administrative permission",
"type":"OAuthException",
"code":200,
"fbtrace_id":"HEVcI\/Tq3fW"
}}
I know that Facebook has deprecated publish_actions scope, so that it's not possible anymore to post programmatically on the personal feed, but I can't find out why the post on a page return this kind of error.
Some further infos:
posting with a developer account actually work
the user by which the page access token is obtained, created the page on Facebook (so I think it's an admin for the page)
i recently migrated from graph_api v2.12 to v.3.1
Any suggestion will be appreciated
Thanks
I figured it out what the problem with some pages is.
It seem that now, if the user grant the manage_pages and publish_pages permission, that will be valid only for already existing pages!
New pages haven't the permission granted by default.
The only way I can fix the problem was to remove my app from the user profile (Facebook Settings > Business Integrations > Select the app > Remove) and then prompt the user again with the Facebook OAuth permission dialog.
I don't know if there is a way to force the app removal programmatically, but I can't find out.
You can use the following URL:
https://graph.facebook.com/v7.0/234002440799692/feed?&access_token={access_token}
I'm trying to connect to a Facebook app that is requesting following permissions:
Access profile and posts from instagram business connected to your page
access insights for the instagram business connected to your page
** manage your pages**
show a list of pages you manage
access your page and app insights
The purpose of the app is to compile post and profile insight stats. If that is the case, why does it need "manage your pages" permission, which gives permission to manage/post/change my page settings?? Or is that legitimately needed just to analyze insights?
https://developers.facebook.com/docs/graph-api/reference/v2.12/insights#reading
Reading page insights requires a page access token, and the only way to get a page access token is to have a page admin grant manage_pages permission to the app first.
manage_pages is the baiscpermission to grant an app access to anything related to a page.
So yes, that an app that analyzes your page insight data asks for this permission, is legit. Of course you will have to trust it, that it won’t abuse it for anything else.
It won’t be able to post in your page’s name though, that would require publish_pages permission as well.
I'm quite confused about Facebook's new publish_pages permission.
My Facebook app allows our CMS users to post to their Facebook pages via our CMS, posing as the page.
We have been granted (via the login review process) the manage_pages and publish_actions permissions.
The API change log states this:
publish_pages Permission - This new permission is required to publish as a Page. Previously publish_actions was required. People who granted manage_pages and publish_actions before v2.3 have automatically been granted publish_pages. If anyone logs in via v2.3, you'll need to request publish_pages explicitly in addition to manage_pages.
We have not been granted the publish_pages permission automatically.
The blog post here states:
For Page developers, we've added the ability to deliver more content on a Page via real-time updates (RTUs). A new Login permission, publish_pages , is now required for apps to publish on behalf of Pages; previously, this required publish_actions.
So it sounds to me like if we upgrade to use API 2.3, our service will no longer work, because we haven't been granted publish_pages.
The documentation states this:
A user access token with publish_actions permission can be used to publish new posts on behalf of that person. Posts will appear in the voice of the user.
A page access token with publish_pages permission can be used to publish new posts on behalf of that page. Posts will appear in the voice of the page.
We do want to post in the voice of the page, as we do currently.
Therefore I opened a new login review request and summarised all of the above, quoting their changelog. Facebook's response was this:
You don't need the publish_pages permission because you already have the publish_actions and manage_pages permissions granted. Publish_pages is a new feature that allows an app to publish to a managed Facebook fan page, but your previously granted permissions contain this functionality already.
Is it just me, or does that response conflict with everything else they've written?
So my question is simply, do we need this new permission going forward or not, and have they wrongly not automatically granted it to us?
Well apparently Facebook's supports response is in some manner wrong.
If you want to post on Page on behalf of the user manage_pages and publish_actions publish permissions are passable for post action.
If you want to post on behalf of the page you also need publish_pages permission, without this all v2.3 api calls will return OAuth Error. There might be other privileges for managing your pages under this permission i don't know
I'm trying to get statistics on my facebook ad campaigns. I've followed Facebook own guide, and I've created an app and so on. However I'm unable to get ads_management permission. If I use the Graph Explorer and its "Get Access Token", I cannot select ads_management under extended permissions, the option is simply not there.
I've also tried just sending a request to the Facebook api as follows:
https://www.facebook.com/v2.0/dialog/oauth?client_id=MY_CLIENT_ID&redirect_uri=MY-REDIRECT_URI&scope=ads_management&response_type=token";
Which does get me a access token, but not one with ads_management permission
Any thoughts?
Edit: My app is not whitelisted, but unless I've misunderstood the guide, it does not have to be, as long as I'm a developer on the app, is this correct?
From what I understand of the Facebook Ads API guide is that the ads_management extended permission is only granted to whitelisted apps. So if the Graph endpoint you're hitting requires that permission then you'll have to get your app approved. Check out the getting started overview https://developers.facebook.com/docs/reference/ads-api/overview
I am using the JavaScript SDK to login in the user on my website via Facebook, requiring the publish_actions permission. If I am getting it right, Open Graph stories published by using publish_actions are only visible for users who have their timeline enabled.
Is it possible to automatically activate the users' timeline after he logged in to my application and gave me the publish_actions permissions. I've seen authentication dialogs around the web where applications request the publish_actions permission and after granting the permission and logging in, the user automatically has the new timeline enabled.
I already searched a lot, but unfortunately I could not find anything in the developer documentation about how to do that.
How do I accomplish this?
If you request the publish_actions permission from the user and you have the action approved by Facebook, the message you talk about will appear in the login popup. Facebook automatically adds this message in as the features are only available with the new timeline profile. There isn't a setting you need to configure to add this message in.
What you describe is the intent of modifying user settings, and you can't do that.