Do I need to register a Facebook app or use OAuth to call the Facebook Page Reels endpoint?

No. SocialAPIs handles upstream auth on our side; you only send a bearer token (your SocialAPIs API token). No Facebook app review, no OAuth scope dance, no expiring user access tokens. This is the primary reason most teams move off the Graph API to us.

How much does a single call cost in credits?

One credit per successful response by default; some compound endpoints (those returning enriched profiles with media + posts inline) cost 2-3. The exact cost is shown in the dashboard and in the X-Credits-Consumed header on every response. Failed requests (4xx errors caused by bad input) do not consume credits.

Can I call this endpoint from Claude Desktop or another AI agent?

Yes. The SocialAPIs MCP server exposes every endpoint as an MCP tool, so any MCP-aware client (Claude Desktop, ChatGPT Custom Integrations, Cursor, Cline) can call it directly inside a chat. Uses the same API token as direct HTTP calls.

What happens if my call fails or returns unexpected data?

Every response includes a request_id in both the body and the x-request-id header. Email it to support and we can pull the full request log within minutes. We retain logs for 30 days on standard plans and indefinitely on enterprise.

SocialAPIs

Back to Sources

Facebook Page Reels

Retrieve short-form video content (Reels) from a Facebook Page.

PagesAvailablereelsvideosshorts

Ready to try this API?

Edit parameters and send a live request from your browser

Introduction

Facebook Reels Scraper is a powerful tool that allows you to extract short video content (Reels) and their metadata from Facebook pages. With just the URL of a Facebook page, you can easily collect relevant Reels data for content analysis, trend tracking, or archiving.

What data can i extract from facebook reels?

This scraper can retrieve the following data points from Reels published on a Facebook page:

🎥 Video Title	📝 Description	🧾 Video ID
🕒 Created Time	💬 Comments Count	❤️ Reactions Count
🔁 Shares Count	▶️ Video URL	⏳ Duration (sec)
📸 Thumbnail URL	📄 Text Content	🔗 Post URL

Input options

link (Required): The full Facebook page URL to scrape data from.
end_cursor (Optional): Used for pagination.

json

1{
2  "link": "https://www.facebook.com/mancity"  
3}

Output and dataset sample

bash

1[
2  {  
3    "video_id": "1234567890",  
4    "title": "A touching moment in NYC",  
5    "description": "Watch how this man changed a stranger’s day.",  
6    "text": "Real stories that inspire.",  
7    "created_time": "2024-03-01T15:22:00Z",  
8    "comments_count": 120,  
9    "reactions_count": 3500,  
10    "shares_count": 210,  
11    "video_url": "https://video.fb.com/watch/1234567890",  
12    "duration_seconds": 45,  
13    "thumbnail_url": "https://image.fbcdn.net/thumbnail.jpg",  
14    "post_url": "https://www.facebook.com/reel/1234567890/"  
15  }  
16]

Your feedback

If you encounter any issues or want to suggest improvements for Facebook Reels Scraper, please share your feedback or report bugs in the support tab.

Conclusion

Whether you are analyzing social media trends or archiving content, Facebook Reels Scraper provides an efficient and easy way to gather valuable video data.

About the Facebook Page Reels API

The Facebook Page Reels endpoint is part of SocialAPIs' unified REST API for public social-media data. Retrieve short-form video content (Reels) from a Facebook Page. It belongs to the Pages category and follows the same auth, pagination, and error-handling conventions as every other endpoint on the platform — so any code you write for one transfers cleanly to the others.

reelsvideosshorts

What you can do with this endpoint

The Facebook Page Reels endpoint is most often combined with other SocialAPIs endpoints to power the workflows below. Each one is achievable on the Free tier for evaluation; scale up to Pro or Ultra when you move to production.

Building a unified dataset

Pipe the GET response straight into BigQuery, Postgres, Airtable, or a Google Sheet via n8n / Make / Zapier. The response is structured JSON — no HTML parsing, no headless browser, no upstream OAuth.

Powering an AI agent (MCP)

The same endpoint is exposed as a tool in the SocialAPIs MCP server, so Claude Desktop / ChatGPT custom integrations / Cursor / any MCP-aware client can call it directly inside a chat. No glue code, no separate auth — the user's API token does both.

Scheduled monitoring & alerts

Schedule a recurring call (cron, GitHub Actions, n8n schedule), diff the latest response against the previous run, and notify Slack / email / Telegram when a meaningful change appears. The response shape is stable across calls so diffs stay reliable.

Backfilling a product feature

If you're building a feature on top of public social data (lead enrichment, brand monitoring, competitive intelligence, resale arbitrage), this endpoint usually replaces a brittle in-house scraper that broke every time Facebook tweaked its HTML. Same dataset, real-time, with an SLA.

Working code example

All SocialAPIs endpoints take your API token in the x-api-token header. Grab yours from your dashboard (or create a free account at /auth/signup — 200 free calls per month, no credit card).

curl -X GET "https://api.socialapis.io/facebook/pages/reels?link=https%3A%2F%2Fwww.facebook.com%2Fmancity" \
  -H "x-api-token: YOUR_API_TOKEN" \
  -H "Content-Type: application/json"

The response is JSON containing the requested data plus a request_id (echo it back in any support email — it lets us pull the matching row from our request log in seconds). Detailed parameter schemas and copy-paste snippets in JavaScript, Python, PHP, Java, and Go are available in the playground above.

Pagination, rate limits, and error handling

Pagination

List-style endpoints return a next_cursor in the response. Pass it back in the next request to walk the full result set. Cursors are stable across calls — safe to persist if you need to resume later.

Rate limits

10 req/min on the Free tier, 100 req/min on Pro / Ultra / Mega, higher dedicated limits on custom plans. Limit hits return HTTP 429 with a Retry-After header — respect it and you'll never see a sustained block.

Errors

4xx = your request (bad params, missing auth, hit limit). 5xx = our side (transient — retry with backoff). Every error response includes error_code, message, and a request_id for support.

Related endpoints in the Pages category

These endpoints share the same data model and auth as Facebook Page Reels. Most real-world integrations combine 2-3 of them.

Facebook Page ID

Retrieve the Facebook Page ID using the page link.

Facebook Page Details

Get detailed metadata from a Facebook Page: likes, followers, contact info, etc.

Facebook Page Posts

Fetch recent posts from a Facebook page including reactions, media, and comments.

Facebook Page Videos

Retrieve video content from a Facebook Page (up to 6 per request).

Frequently asked questions

Do I need to register a Facebook app or go through OAuth to use the Facebook Page Reels endpoint?

No. SocialAPIs handles the upstream auth and infrastructure on our side. You just send a bearer token (your SocialAPIs API token) and call the endpoint. No Facebook app review, no OAuth scope dance, no expiring user access tokens. This is the primary reason most teams move off the Graph API to us.

How much does a single call to this endpoint cost in credits?

One credit per successful response. The exact cost is shown in the dashboard under "Usage" after every call. Failed requests (4xx errors caused by bad input) do not consume credits.

Is the data real-time or cached?

Real-time. Each call fetches from the upstream source at the moment you call us — we don't cache responses between users. The exception is the Ads Library endpoints, which return Meta's own snapshots and therefore lag by 24-48 hours because Meta itself indexes them on that cadence (not us).

Can I use this endpoint inside Claude Desktop, ChatGPT, or another AI agent?

Yes. The SocialAPIs MCP server exposes every endpoint as an MCP tool, so any MCP-aware client (Claude Desktop, the ChatGPT Custom Integrations beta, Cursor, Cline) can call it directly inside a chat. The MCP server uses the same API token as direct HTTP calls, so your credit balance, rate limits, and usage history are unified across surfaces.

What happens if my call fails or returns an unexpected shape?

Every response — success or error — includes a request_id in both the body and the x-request-id header. Email it to support and we can pull the full request log (params, upstream response, timing, error trace) within minutes. We retain the log for 30 days on standard plans and indefinitely on enterprise. Don't ship a workaround for an edge case without checking with us first — it's usually a two-line server fix.

Heads up if you're migrating from the Graph API

Some fields Meta's official Graph API used to return are no longer publicly accessible (page email, exact follower counts on small pages, post audience targeting). Where we can derive them from other public signals, we do; where we can't, the field will be absent from the response (we don't fabricate values). The full list of "what's still returnable in 2026" lives in the docs — start there before assuming a field is broken on our side.

Ready to call Facebook Page Reels?

Use the playground at the top of this page to send a live request against your account — or grab the curl above and run it from your terminal. Free accounts get 200 calls per month, enough to integrate, prototype, and ship a working demo before deciding whether to upgrade.

Create a free API key · See pricing · Browse all endpoints