The Pages API is a set of Facebook Graph API endpoints that apps can use to create and manage a Page's settings and content. If you are unfamiliar with the Graph API, please read our Graph API documentation before proceeding.
API authentication is handled through Access Tokens. Most endpoints require Page access tokens, which are unique to each Page, app user, and app, and have an expiration time. In order to get a token from an app user, the app user must own or be able to perform a Task on the Page.
You can get access tokens from your app users by implementing Facebook Login.
Most endpoints require one or more Permissions which must be granted by your app users through the use of Facebook Login. Refer to each endpoint's reference to determine which Permissions it requires. Almost all Permissions require App Review before your app can use them in Live Mode.
Grants an app permission to retrieve Page Access Tokens for the Pages and Apps that the app user administers. Apps that allow users to publish posts and comments must also have the
Grants an app permission to publish posts and comments, to like Pages, and to view, post, and delete videos for Pages managed by the app user. Also requires the
Grants an app permission to manage and access Page conversations in Messenger.
Grants an app permission to retrieve a list of Pages and Page Access Tokens that the person administers.
Grants an app permission to perform
Grants an app permission to manage Instant Articles on behalf of a Facebook Page administered by people using your app.
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.
Tasks allow Users to perform specific actions on a Page. When a User uses an app to interact with a Page, depending on the attempted action, we will first check if the User has been approved for a task that permits that type of action.
You can approve individual Users for the following tasks:
Create ads and unpublished Page Posts
Create Posts as the Page
Approve and manage Page tasks for Users
Respond to and delete comments, send messages as the Page
Beginning February 1, 2019, Page tasks have replaced Page roles. Under the old role-based model, assigning a role to a 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:
When a User visits a Page, an ID is returned for that person for that specific page. The Pages API returns this Page-scoped ID, a PSID, for a User allowing your app to connect a customer's interactions with the Page across both Pages API and Messenger API. This will allow your app to connect public conversations that happen through Messenger for a given User and Page.
Before May 1, 2018, the Pages API returned App-scoped IDs, ASIDs. If your app used the Pages API and ASIDs before this date, you will need to migrate from your ASIDs to Page-scoped IDs within 180 days of your App Review approval at which time your ASIDs will no longer work. Only after you have completed the migration will your app receive PSIDs instead of ASIDs.
To facilitate the ASID to PSID migration process, use the Page-scoped ID API. This API allows you to map an ASID and a page to a PSID. You can then prepare your systems to be able to support PSIDs. Once your migration is complete we can then enable PSIDs to be returned via the Pages API endpoints.
The Page-scoped ID API will be available for 180 days from the date that your app passed App Review. The Pages API Migration section in your app's App Dashboard (Settings > Advanced > Pages API Migration) will display the number of days remaining for your app.
All Pages endpoint requests are subject to Rate Limiting. You can see your app's current call count consumption in the App Dashboard.
This is a typical flow for accessing the Pages API:
/me/accountsendpoint to get the ID and Page Access Token of the Page the app user has permitted your app to access.
Note that in some cases the app user may grant your app access to more than one Page, in which case you should capture each Page ID and its respective token, and provide a way for the app user to target each of those Pages.
Follow our Get Started guide to learn how to create a Page and post to it using the Pages API.