Facebook Pages | Operate As Docs

Website: facebook.com/business/pages
Connects by: Signing in with Meta
Category: Social and video
Part of: Meta
Tools: 1

Service	Key	Base URL
Facebook Pages	`facebook-pages`	`https://graph.facebook.com/v23.0`

Connecting

Your client presses Connect on their link and approves on Meta's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "facebook-pages"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "facebook-pages"    ]  }]

Permissions

What the client reads	Permission it asks for
See the Pages you manage	`pages_show_list`
See your Pages' posts, comments and followers	`pages_read_engagement`
Post to your Pages	`pages_manage_posts`

Tools

Install Facebook Pages's typed package for your language:

pip install operate-as-facebook-pages

pip install operate-as-facebook-pages

Run facebook-pages.list_pages

curl -X POST https://api.operate.as/v1/actions/facebook-pages.list_pages \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "user_id": "<user_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/facebook-pages.list_pages \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "user_id": "<user_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/facebook-pages.list_pages

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://graph.facebook.com/v23.0. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../facebook-pages/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../facebook-pages/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Meta refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Meta access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Meta access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "meta",
    "services": [
      "facebook-pages"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "meta",    "services": [      "facebook-pages"    ],    "reconnectUrl": "https://…"  }}