Facebook API - Pages, Posts, Reels, Groups, Events

Facebook via Scavio

Pull a Facebook page's profile, posts, reels and photos, one post with its comments, a single reel or video with downloadable URLs, a public group and its posts, an event, and the top posts for a hashtag. All endpoints return structured JSON.

When to trigger

Use this skill when the user asks to:

• Read a Facebook page or public profile: name, category, verified flag, likes, followers, and (where published) website, phone, email, address, hours, rating, profile and cover photos
• Read a page's recent top posts, its reels (with downloadable video URLs), or its photo grid
• Read one post in full with its reaction breakdown and top comments
• Resolve a reel / video / watch item to its downloadable HD and SD video URLs
• Read a public group's profile and its top posts
• Read a public event (time, location, host, going/interested counts)
• Read the top public posts for a hashtag
• Do brand monitoring, competitor page analysis or content research on Facebook

Setup

Get a free API key at scavio.dev (50 free credits to get started, no card required):

export SCAVIO_API_KEY=sk_live_your_key

Every request is a POST with a JSON body and:

Authorization: Bearer $SCAVIO_API_KEY

Endpoints

Base URL: https://api.scavio.dev. Every Facebook endpoint costs 1 credit.

Parameters

Every endpoint except hashtag takes a single url:

hashtag takes:

Scope notes

• The post and group-post endpoints return the current top posts, not the full historical feed.
• post/comments returns the top visible comments, not the full thread or nested replies.
• Private groups and locked profiles are reported as unavailable (a 404), and cost nothing.
• Reel and video URLs are directly downloadable but signed with a short expiry - use them promptly.

Examples

import requests

BASE = "https://api.scavio.dev"
# Your key from https://scavio.dev. Load it from your environment or secret
# store in real code - keep it out of source control.
API_KEY = "sk_your_key_here"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}

# 1. A page's profile, then its recent posts
profile = requests.post(f"{BASE}/api/v1/facebook/profile", headers=HEADERS,
    json={"url": "https://www.facebook.com/nike"}).json()
posts = requests.post(f"{BASE}/api/v1/facebook/profile/posts", headers=HEADERS,
    json={"url": "https://www.facebook.com/nike"}).json()

# 2. One post in full, plus its top comments
post = requests.post(f"{BASE}/api/v1/facebook/post", headers=HEADERS,
    json={"url": "https://www.facebook.com/nike/posts/pfbid0..."}).json()

# 3. A reel resolved to downloadable HD/SD URLs
reel = requests.post(f"{BASE}/api/v1/facebook/reel", headers=HEADERS,
    json={"url": "https://www.facebook.com/reel/1234567890"}).json()

# 4. Top posts for a hashtag
tag = requests.post(f"{BASE}/api/v1/facebook/hashtag", headers=HEADERS,
    json={"tag": "photography"}).json()

curl:

curl -s https://api.scavio.dev/api/v1/facebook/profile \
  -H "Authorization: Bearer $SCAVIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.facebook.com/nike"}'

Response shape

Every response uses the envelope { data, response_time, credits_used, credits_remaining }. data carries the profile / posts / reel / group / event payload, with a count on the list endpoints.

Guardrails

• Every Facebook call is 1 credit. A 404 for a private group, locked profile or dead id is billed as false - the customer is not charged for data that was genuinely unavailable.
• Posts and group posts are the current top posts, not the full feed; comments are the top visible ones, not the full thread.
• Reel/video URLs expire quickly - download promptly rather than storing the URL.
• Never fabricate follower counts, post text, comment text or contact details. Only return what the API returned.
• Profiles, posts and comments involve real people. Summarise; do not build profiles of individuals, and respect that contact fields are only returned when the page itself published them.

Failure handling

• 400 means an invalid or missing parameter. Fix and retry.
• 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
• 404 means the surface is not found or unavailable (e.g. a private group or locked profile).
• 429 means rate or usage limit exceeded. Wait before retrying. See rate limits.
• 502 / 503 mean the source is temporarily unavailable - wait a few seconds and retry.
• If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.