A Facebook Reels API permission error means your access token is missing a Page permission the Reels endpoint requires, or the person who granted it no longer has a role on the Page. Reels publishing needs pages_manage_posts and pages_read_engagement on a Page you admin, granted through Facebook Login, then checked against your token’s actual scopes.
POST /{page-id}/video_reels
|
v
[ 1 ] token has pages_manage_posts? --no--> re-auth, add scope
|
yes
v
[ 2 ] token has pages_read_engagement? --no--> re-auth, add scope
|
yes
v
[ 3 ] user still admin/editor on Page? --no--> fix Page roles
|
yes
v
[ 4 ] app has the permission approved? --no--> App Review
|
yes
v
[ 5 ] token is a Page token, not a user token --no--> exchange it
|
yes
v
Reel upload acceptedWhat causes the Facebook Reels API permission error
The message usually names a permission, not a bug in your code. Read the exact code and the exact scope it mentions before you change anything.
The common causes, in the order they actually happen:
- The token was minted without pages_manage_posts, which the Reels publishing call requires.
- The token has pages_read_engagement but not the write scope, so reads work and uploads fail.
- The user who authorized your app lost admin or editor rights on the Page, so the grant no longer applies.
- Your app is in development mode and the permission has not been through App Review for the accounts you are posting with.
- You are calling the Page endpoint with a user token instead of a Page token.
Two of these are configuration, three are consent. Fixing consent problems by changing code wastes an afternoon.
Which Facebook API permissions you need to post reels on a Page
Reels publishing is a write action on a Page, so you need the Page write permission plus enough read access to resolve the Page.
| Permission | Why the Reels call needs it | Symptom when missing |
|---|---|---|
| pages_manage_posts | Creates and publishes content on the Page, including Reels | Permission error on the upload start call |
| pages_read_engagement | Reads the Page and its content so the upload has a valid target | Page lookup returns empty or denied |
| pages_show_list | Lets your app see which Pages the user manages | The Page never appears in your account list |
| business_management | Needed when the Page is owned by a Business Manager | Works for personal Pages, fails for business ones |
If you are wiring Facebook into an agent or a scheduler, decide once which Page each connection points at. Creator OS pins every API key to one workspace, so an agent holding that key posts to that Page and nothing else. That limits the blast radius of a misconfigured token.
How to check your Facebook Graph API access token and scopes
Ask Facebook what your token can do instead of guessing from your login code.
Call the debug endpoint with the token and the app access token, then read two fields: scopes and expires_at. If pages_manage_posts is not in scopes, re-run the login flow and request it. If expires_at is in the past, every call will fail no matter what the scopes say.
Confirm the token type as well. A user token and a Page token look similar in a log line and behave completely differently. Exchange the user token for the Page token, then print the first and last six characters of the token you are actually sending. A large share of “permission” errors are a stale token from a shell variable or a .env file that was never reloaded.
Write the check into your pipeline as an assertion, not a manual step:
# before any Reels upload
assert "pages_manage_posts" in token_scopes
assert "pages_read_engagement" in token_scopes
assert token_expires_at > now()
For the REST side of this, the authentication docs explain how Creator OS keys and workspace scoping work, and the posts API reference shows the request shape you would send instead of raw Graph calls.
Fix pages_manage_posts and pages_read_engagement grants on your Facebook Page
Most fixes are a Page role correction plus a fresh consent, not a code change.
- Open the Page settings and check that the account you authorized is an admin or editor. A user removed from the Page keeps a valid token that no longer has Page rights.
- Remove the app from the user’s Facebook settings, then reconnect so consent runs again with both scopes requested.
- If the Page belongs to a Business Manager, confirm the user has the Page asset assigned inside Business Manager, not just a Page role.
- Retry with the Page token, not the user token.
There is a full walkthrough of the error in the post on the pages_manage_posts permission error fix, including the exact re-auth sequence. If reads work but engagement data never arrives, the pages_read_engagement missing permission error post covers that case.
How the Facebook review API and app review unblock reels publishing
App Review is what turns a permission you requested into a permission you can use on other people’s accounts.
In development mode, an app can use most permissions for accounts with a role on the app. The moment you post to a Page run by someone who has no role on your app, Facebook requires the permission to be approved. That is the “Facebook review API” step people mean: you submit each permission with a screen recording of the exact flow and a written description of what your app does with it.
Practical advice from the field: submit one permission at a time, record the full flow from login to a published Reel, and describe the write action plainly. A rejection usually means the reviewer could not reproduce the flow, not that the permission was wrong.
If waiting on review blocks your launch, you can keep posting manually until review clears, or use a tool that already handles the connection and publishing for you. Creator OS connects Facebook Pages as accounts you sign in to, so publishing a Reel does not mean writing Graph calls yourself. See the Facebook Reels API guide for what the connection covers.
Can you post reels with an open API Facebook test app?
Yes for testing, no for production traffic. A test app is fine for validating your upload code against a Page you admin.
Test apps exist to prove the request sequence: start the upload, send the video, publish, handle the response. They are not a shortcut around permissions for real Pages owned by other people, and permissions granted inside a test app do not transfer to your live app.
Two things to verify while you are in test mode: the video format your account accepts, and how long the processing step takes from your network. Reels uploads are asynchronous, so a request that looks successful may still fail later. Handle the status poll before you call it done. For platform behaviour beyond permissions, the Reels API reference post is the place to check.
Facebook reels upload API checklist before you retry
Run these six checks in order. Each one eliminates a class of error, and the order matters because a later check cannot pass while an earlier one fails.
| # | Check | How to confirm |
|---|---|---|
| 1 | Token is a Page token | Debug endpoint shows type PAGE |
| 2 | Token is not expired | expires_at is in the future |
| 3 | Both scopes present | pages_manage_posts and pages_read_engagement in scopes |
| 4 | Author still has a Page role | Admin or editor in Page settings |
| 5 | App holds approved permissions | App Review status shows approved for both |
| 6 | Upload sequence matches docs | Start, transfer, publish, then poll status |
If you would rather skip the token dance entirely, an agent with Creator OS can publish a Reel from a plain instruction and report back. The MCP server at https://mcp.creatoros.ca/mcp takes a connection, and tools like create_post and get_post_analytics do the posting and the reading. Set up instructions live in the MCP docs, and you can watch the walkthroughs on the KevBuildsApps YouTube channel if you prefer video.
FAQ
How do I fix a Facebook Reels API permission error?
Check your token’s scopes first. If pages_manage_posts or pages_read_engagement is missing, reconnect the app so consent runs again with both scopes, then confirm the authoring user still has an admin or editor role on the Page. If both scopes are present and the role is fine, exchange the user token for a Page token and retry.
What permission do I need to post reels on a Facebook Page via API?
You need pages_manage_posts to publish content on the Page and pages_read_engagement to read the Page and its content. pages_show_list is needed for your app to list the Pages a user manages, and business_management matters when the Page sits inside a Business Manager.
Why does my Facebook API post fail with pages_manage_posts?
The usual reason is that the permission was never granted in the login flow, so the token carries the read scope only. The second reason is a user who was removed from the Page after authorizing your app. Re-request the scope and rebuild the token; do not patch the request body.
Do I need app review to publish Facebook reels through the API?
You need App Review once your app posts to Pages managed by people who have no role on your app, which is normal production traffic. While you test with a Page you admin yourself, you can usually publish without it. Submit the permissions with a clear recording of the full publish flow.
How do I get a Facebook API key with the right Page permissions?
Create an app in Meta’s developer console, add Facebook Login, request pages_manage_posts and pages_read_engagement, then have a Page admin authorize the app and pick the Page. Store the resulting Page token server side and never ship it to a browser or a public repo.
Get started
Creator OS connects Facebook Pages as accounts you sign in to, then publishes Reels and reads the results from the same workspace. Creator OS plans start at $14.99/month for 11 platforms plus Skool, with the API, the MCP server and the CLI included.
Start a free trial at creatoros.ca/sign-up. If you are still deciding, the Reels API guide and the docs cover the rest, and the launch video shows the whole thing running.
Get started for $0
Free trial for new subscribers. Cancel anytime.