To access Pages API endpoints you may need a combination of the following permissions, features, or tasks.
For Pages that have been migrated to the New Page Experience, a Page access token is now required for all available endpoints with the follwing exceptions:
Most endpoints require one or more permissions which must be granted to your app by app users. Typically this can be done through Facebook Login but can also be done through the Business Manager, if your app has been claimed by a Business.
All Page-related permissions require App Review before an app user can grant them to your app while it is in Live mode. For Business apps, which do not have app modes, permissions must be approved for Advanced access before they can be granted to your app by an app user without a role on the app itself or a role in a Business that has claimed it.
Beginning October 14, 2020, the pages_show_list
permission will require App Review.
You will need to request access through App Review if:
pages_show_list
permission for the first time.pages_show_list
permission within the last 90 days.If your app has previously been approved for any of the following permissions through App Review no action is required:
Permission | Description |
---|---|
manage_pages Deprecated | |
The pages_messaging permission allows your app to manage and access Page conversations in Messenger. The allowed usage for this permission is to create user-initiated interactive experiences, send customer support messages or to confirm bookings or purchases and orders. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_show_list permission allows your app to access the list of Pages a person manages. The allowed usage for this permission is to show a person the list of Pages they manage. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_ads permission allows your app to manage ads associated with the Page. The allowed usage for this permission is to create and manage ads for the Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_cta permission allows your app to carry out POST and DELETE functions on endpoints used to manage call-to-action buttons on a Facebook Page. The allowed usage for this permission is to provide API access to manage call-to-action buttons on Pages that you manage. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_engagement permission allows your app to create, edit and delete comments posted on the Page. If you have access to pages_read_user_content, you can also use pages_manage_engagement to delete comments posted by other Pages. It also allows your app to create and delete your own Page's Likes to Page content. The allowed usage for this permission is to help manage and moderate content on the Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_instant_articles permission allows your app to manage Instant Articles on behalf of Facebook Pages administered by people using your app. The allowed usage for this permission is to create and update Instant Articles for Pages owned by the people who use your app. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_metadata permission allows your app to subscribe and receive webhooks about activity on the Page, and to update settings on the Page. The allowed usage for this permission is to help a Page Admin administer and manage a Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_manage_posts permission allows your app to create, edit and delete your Page posts. If you have access to pages_read_user_content, you can also use pages_manage_posts to delete Page posts created by a user. The allowed usage for this permission is to create and delete content on a Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_read_engagement permission allows your app to read content (posts, photos, videos, events) posted by the Page, read followers data (including name, PSID), and profile picture, and read metadata and other insights about the Page. The allowed usage for this permission is to help a Page Admin administer and manage a Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The pages_read_user_content permission allows your app to read user generated content on the Page, such as posts, comments, and ratings by users or other Pages, and to delete user comments on Page posts. It also allows your app to read posts that the Page is tagged in. The allowed usage for this permission is to read user's and other Page’s content posted on the Page if you need it to help manage the Page. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
publish_pages Deprecated |
Permission | Dependent on | Description |
---|---|---|
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
|
| To be approved for |
Deprecated Permission | Permission Use Cases |
---|---|
|
– Read data of your Page followers – Read metadata of your Page – Read insights of your Page
– Delete User comments on your Page posts – Read posts your Page is tagged in |
|
– Delete User posts on your Page ( pages_read_user_content needed)
– Delete comments posted by other Pages ( pages_read_user_content needed) – Create and delete likes posted by your Page |
Some endpoints require features which must be approved through the App Review process before your app can use them in Live mode. Refer to each endpoint's reference to determine which features it requires, if any.
Feature | Description |
---|---|
The Live Video API feature allows an app to manage live videos to Pages, Groups and User timelines when combined with the correct matching permission. | |
The Page Mentioning feature allows your app mention any Facebook Page when publishing posts on the Pages managed by your app. | |
The Page Public Content Access feature allows read-only access to public data on Pages for which you lack the manage_pages login permission. Readable data includes business metadata, public comments and posts. The allowed usage for this feature is to provide aggregated, anonymized public content for competitive analysis and benchmarking. You may also use this feature to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). | |
The Page Public Metadata Access feature grants your app permission to read public Page fields and the Pages Search API. The allowed usage for this feature is to analyze engagement with public Pages by viewing Like and follower counts, or aggregate public-facing About Page information from multiple, disparate pages. You may also use this permission to request analytics insights to improve your app and for marketing or advertising purposes, through the use of aggregated and de-identified or anonymized information (provided such data cannot be re-identified). |
Tasks allow app users to perform specific actions on Pages. When an app user interact with a Page, depending on the attempted action, we will first check if the app user has been approved for a task that permits that type of action.
You can approve individual users for the following tasks:
Task | Permitted Actions |
---|---|
|
|
|
|
|
|
|
|
|
|
Beginning February 1, 2019, Page tasks have replaced Page roles. Under the old role-based model, assigning a role to an app user granted that user permission to perform a set of actions. The new task-based model allows you to be more restrictive by only approving tasks that map to certain actions.
Use the table below to map roles to their equivalent actions:
Role | Equivalent Tasks |
---|---|
|
|
|
|
|
|
|
|
|
|