Read Public Page Photos
View all Facebook Public Data API endpoints →Supply page_id to request recent publicly accessible Page photos. For continuation, the documented contract requires both cursor and collection_id from the first response; keep the pair together for the same Page. This route has not been sampled, so photo fields, result envelope and ordering details are unverified. Inspect a representative response before defining a storage schema. Photo access does not grant download, redistribution or model-training rights, and cursor traversal does not promise a complete photo archive.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/facebook-scraper/pages-photos API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/facebook-scraper/pages-photos?key=<API_KEY>&page_id=<page_id>'
Query Result
Use Cases
- Create an internal reference index of a brand Page photo collection after validating returned fields.
- Review campaign imagery separately from Page videos in a visual-content audit.
- Test that a photo collector carries collection_id alongside cursor on subsequent requests.
- Maintain a bounded, deduplicated shortlist of Page images for licensed editorial review.
Frequently asked questions
Is cursor alone enough for the next page of Page photos?
The documented contract also requires collection_id, with both values coming from the same Page-photo response. Do not invent a collection value.
Have the photo response fields been validated?
Not yet. Inspect the actual photo fields, envelope and ordering before establishing collection and storage rules.
Can I use the returned images directly for advertising or training?
Accessibility alone does not establish permission. Separately confirm media rights, platform terms and permission for the specific use.