The following permissions require approval through the App Review process. Once approved, you can use Facebook Login to ask Users to grant your app any approved permissions.
The default
and email
permissions do not require review but are listed here because they are automatically approved for all apps.
ads_management
Requires App Review.
Grants your app the ability to both read and manage the ads for ad accounts you own or have been granted access to by the owner or owners of the ad accounts through this permission. By default, your app may only access ad accounts that are owned by admins of the app when in developer mode.
Allowed Usage
Programmatically create campaigns, manage ads, and fetch metrics.
Build ad management tools that provide innovative solutions and differentiated value for advertisers.
Disallowed Usage
Businesses must not try to reverse engineer how Facebook's delivery engine works.
Businesses must not try to duplicate too many of the same ads to increase chance that ads are delivered.
ads_read
Requires App Review.
Grants your app access to the Ads Insights API to pull ads report information for ad accounts you own or have been granted access to by the owner or owners of other ad accounts through this permission.
Provide API access to your ad performance data for use in custom dashboards and data analytics.
Businesses must not try to identify an individual and target them with specific ads.
Businesses must not share audiences across products owned by different businesses.
Businesses must not share insights across products owned by different businesses.
business_management
Requires App Review.
Grants your app permission to read and write with the Business Manager API.
Manage business assets such as an ad account. Claiming ad accounts.
Performing general page management and administration only.
default
Does not require App Review.
Grants your app access to the default fields of the User object that are a subset of a person's public profile:
id
first_name
last_name
middle_name
name
name_format
picture
short_name
email
Does not require App Review.
Grants your app permission to access a person's primary email address.
Allow a person to use their Facebook email address to login to your app.
Spamming users. Your use of email must comply with both Facebook policies and the CAN-SPAM Act.
groups_access_member_info
Requires App Review.
Grants an app permission to publicly available group member information.
Allow apps to get content posted in their group with user details
Help admins get aggregated insights about activity happening in their group
Behavioral retargeting
Building or augmenting user profiles
Mapping user engagement across Groups
Sharing data between multiple businesses that you manage
Transfering or selling data obtained through third parties
instagram_basic
Requires App Review.
Grants your app permission to read Instagram Accounts users of your app manage.
Get basic metadata of an Instagram Business Account.
instagram_manage_comments
Requires App Review.
Grants your app permission to read Instagram Accounts users of your app manage.
Read, update, and delete comments of Instagram Business Accounts.
Read media objects, such as stories, of Instagram Business Accounts.
instagram_manage_insights
Requires App Review.
Grants your app permission to read insights of Instagram Accounts users of your app manage.
Get metadata of an Instagram Business Account.
Get data insights of an Instagram Business Account.
Get story insights of an Instagram Business Account.
leads_retrieval
Requires App Review.
Grants your app permission to retrieve all the information captured within a lead.
Leads are generally submitted by users in response to specific kinds of CTA (Sign ups, Get Quotes, etc.) shown on the ad. The information within the lead is used to reach out to the users to follow up on those CTA. For example, a dealer reaches out to a potential customer (lead) with quotes for a car.
By advertiser authorized CRM platforms to pull the lead data on behalf of the advertisers. The advertisers then use the lead information to reach out to the user.
Share the lead data with anyone outside of the advertiser who ran the ads for capturing the leads.
Store additional information of the user outside of what was submitted on the lead form.
manage_pages
Requires App Review.
Grants an app permission to retrieve Page Access Tokens for the Pages and Apps that the person administers.
Apps need both manage_pages
and publish_pages
to be able to publish as a Page.
Publish content to Pages owned by the people who use your app. Publishing also requires the publish_pages
permission.
Help people manage the posts, comments and likes published to their Pages.
pages_manage_cta
Requires App Review.
Allows app to perform POST
and DELETE
operations on endpoints used for managing a Page's Call To Action buttons.
Provides API access to manage call to actions on Pages that you manage
pages_manage_instant_articles
Requires App Review.
Grants an app permission to manage Instant Articles on behalf of Facebook Pages administered by people using your app.
Create and update Instant Articles for Pages owned by the people who use your app.
pages_messaging
(Send/Receive API)Requires App Review.
Grants your app permission to send and receive messages through a Facebook Page.
Creating user-initiated interactive experiences
Confirming bookings, purchases, orders, etc.
Sending customer support messages
Up-selling or cross-selling products or services
Sending brand advertising, newsletters, announcements or spam
Messaging people without their consent
pages_messaging_subscriptions
Requires App Review.
Grants your app permission to send messages using Facebook Pages at any time after the first user interaction. Your app may only send advertising or promotional content through sponsored messages or within 24 hours of user interaction.
Send subscription messages to a person on Messenger.
pages_show_list
Does not require App Review.
Grants your app access to show the list of the Pages that a person manages.
Provides API access to accounts for showing the list of the Pages that a person manages.
public_profile
Does not require App Review.
Grants your app permission to the default fields of the User object that are a subset of a person's public profile:
id
first_name
last_name
middle_name
name
name_format
picture
short_name
This permission is the same as the default
permission, which appears in the App Review submission interface. If you examine a User's access token, the default
permission will instead be listed as the public_profile
scope.
publish_pages
Requires App Review.
Grants your app permission to publish posts, comments, and like Pages managed by a person using your app. Your app must also have manage_pages
to publish as a Page.
Allow people to explicitly publish content from your app to any of the Facebook Pages they manage from within a custom composer.
Seamlessly like and comment from your app on behalf of the Pages a person manages.
Automatically publish stories without the person being aware or having control.
Pre-fill the message parameter of posts with content a person didn’t create, even if the person can edit or remove the content before sharing.
Publish to a Page as an individual personal account.
publish_to_groups
Requires App Review.
Grants an app permission to post content into a group on behalf of a User who has granted the app this permission.
Allow people to publish content from your app to their Facebook group.
Help people manage the content published to their group.
Automatically publish content without the person being aware or having control over said content.
publish_video
Requires App Review.
Grants an app permission to publish live videos to the app User's timeline.
Live video streaming to a User's timeline.
Streaming of advertisements, or any content which does not meet Facebook's content policies.
read_audience_network_insights
Grants an app permission to read-only access of the Audience Network Insights data for Apps the person owns.
Integrate Facebook's app Audience Network insights into your own analytics tools.
Transfer or sell insights data to third parties.
Provide any non-visible use of insights.
read_insights
Requires App Review.
Grants an app permissions to read-only access of the Insights data for Pages, Apps, and web domains the person owns.
Integrate Facebook's app, page or domain insights into your own analytics tools.
Transfer or sell insights data to third parties.
Provide any non-visible use of insights.
read_page_mailboxes
Requires App Review.
Grants an app permission to read from the Page Inboxes of the Pages managed by a person. This permission is often used alongside the manage_pages
permission.
Allow someone to manage the mailboxes of their Pages through your app.
This permission does not let your app read the page owner's mailbox. It only applies to the page's mailbox.
user_age_range
Requires App Review.
Grants an app permission to access a person's age range.
Your app includes content that is legally required to be age-gated, for example, gambling, gaming, or alcohol.
Your app includes content that is not suitable for the general Facebook audience, such as dating, mature, graphic, or violent content.
Your application includes content that is directed at kids or teens.
No visible impact to the User experience based on a person's age range.
user_birthday
Requires App Review.
Grants an app permission to access a person's birthday.
Provide age relevant content to people based on their date of birth.
Provide age relevant content for anything where the age range is not sufficient.
Determine whether a person says they are under 18, over 18, or over 21. Please use the age_range
instead.
user_events
Requires App Review.
Grants an app permissions to read-only access to the Events a person is a host of or has RSVPed to. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
Reduce friction in the visibility of calendar and event information, e.g., device apps, planner apps, concert apps, etc.
Create events.
RSVP to events using your app.
user_friends
Requires App Review.
Grants an app permission to access a list of friends that also use said app. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
In order for a person to show up in another's friend list, both people must have shared their list of friends with the app and not disabled this permission during login.
Use the list of friends to create a social experience in an app.
user_gender
Requires App Review.
Grants an app permission to access a person's gender.
Correctly render pronouns in certain languages, for example, when a bot messages a person.
Display a person's gender to other people, for example, for dating.
Personalized a User's experience based on gender, for example, in shopping or fashion.
No visible impact to the user experience based on gender.
Fill out a registration form or User profile without using the information to enhance the User experience.
user_hometown
Requires App Review.
Grants an app permission to access a person's hometown location set in their User Profile.
Help people connect to others from their hometown.
Personalize a person's experience based on where they lived or grew up.
user_likes
Requires App Review.
Grants an app permission to access the list of all Facebook Pages that a person has liked.
Create a personalized experience by correlating and surfacing content related to a person's interests.
Enable connections with other users based on mutual interests. The user must be informed why the other users are suggested.
Gate access to your app, or some content within your app, based on whether or not someone has liked a page.
user_link
Requires App Review.
Grants your app permission to access the Facebook Profile URL of User of your app.
Provide a way for someone who uses your app to visit the Facebook Profile of someone in their friends list who also uses your app, for example, for local listings.
Attempt to programmatically determine someone's Facebook username or canonical User ID.
user_location
Provides access to a person's current city through the location
field on the User object. The current city is set by a person on their Profile.
The current city is not necessarily the same as a person's hometown.
If your app requests this permission Facebook will have to review how your app uses it.
Personalize a person's experience based on their current city.
Surface content relevant to their city.
Help people connect to others from their city.
user_photos
Provides access to the photos a person has uploaded or been tagged in. This is available through the photos edge on the User object. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
Requesting this permission requires you to submit your app for Login Review.
Display a person's pictures on digital photo frame.
Help people export their photos for printing. Only offer this service for a person's personal and non-commercial use.
Access photos for use in a way that visibly enhances the in-app experience (e.g. photo editing, collage, slideshow, and face-in-hole apps).
Access a person's previous profile pictures.
Create albums on behalf of the user.
user_posts
Provides access to the posts on a person's Timeline. Includes their own posts, posts they are tagged in, and posts other people make on their Timeline. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
Requesting this permission requires you to submit your app for Login Review.
Provide creative content from Timeline posts.
Provide value to the user by visibly analyzing the content of the posts on their Timeline.
Non-visible use of this data such as sentiment analysis or guarding against spam bots.
user_tagged_places
Provides access to the Places a person has been tagged at in photos, videos, statuses and links. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
Requesting this permission requires you to submit your app for Login Review.
Provide tailored content based on the places a person has been.
Recommend places to visit based on the places a person has previously been tagged at.
Show someone their checkin history on a map.
user_videos
Provides access to the videos a person has uploaded or been tagged in. This permission is restricted to a limited set of partners and usage requires prior approval by Facebook.
Requesting this permission requires you to submit your app for Login Review.
Access videos for use videos in a way that visibly enhances the in-app experience: (e.g. editing, collage, portfolio, slideshow apps.)
Display a person's videos on a TV via a set top box, or display their videos on a digital photo frame.
Name | Deprecation Date |
---|---|
| Graph API v2.3 |
| April 4, 2018 |
| Graph API v2.3 |
| Graph API v2.3 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| Graph API v2.8 - Coincided with the deprecation of Custom Open Graph and Custom App Collections |
| April 4, 2018 |
| April 4, 2018 |
| Graph API v2.3 |
| Graph API v3.0 |
| April 4, 2018 |
| April 4, 2018 |
| April 4, 2018 |
| Graph API v2.3 |
| April 4, 2018 |
| April 4, 2018 |