Profile
1 credit/v1/facebook/profileGet Facebook page profile.
url, get_business_hours
Fetch public Facebook data as structured JSON with one SocialCrawl API key. Same Post, Comment, and Author schema as every other platform. Reads are priced in credits.
23 active endpoints
23 live read endpoints for public Facebook data. Profiles, posts, reels, comments, Ad Library, groups, events, and marketplace search. Data API only.
/v1/facebook/profileGet Facebook page profile.
url, get_business_hours
/v1/facebook/profile/fullFacebook profile, recent posts, and computed analytics in one call.
url, posts, cursor, include
/v1/facebook/profile/postsList Facebook page posts.
url, pageId, cursor
/v1/facebook/postGet Facebook post details.
url, get_comments, get_transcript
/v1/facebook/post/commentsList Facebook post comments.
url, feedback_id, cursor
/v1/facebook/post/transcriptGet Facebook video transcript.
url
/v1/facebook/adlibrary/search/adsSearch Facebook Ad Library.
query, sort_by, search_type, ad_type, country
/v1/facebook/adlibrary/adGet Facebook Ad Library ad details.
id, url, trim
/v1/facebook/group/postsList Facebook group posts.
url, group_id, sort_by, cursor
/v1/facebook/marketplace/searchSearch Facebook Marketplace listings.
query, lat, lng, radius_km, min_price, max_price
Returns a Facebook page's public profile: page id, display name, profile image, bio, follower count, and page-like count.
Use it when you have a page URL and want a quick snapshot before pulling that page's posts, photos, or reels.
1 credit
url · Full URL of the Facebook page or profile
$ curl https://www.socialcrawl.dev/v1/facebook/profile?url=https%3A%2F%2Fwww.facebook.com%2FMeta \
-H "x-api-key: sc_YOUR_API_KEY"// Edit the params above and hit "Try it" to run a live request against the APIFacebook is a normal SocialCrawl social surface. You call GET /v1/facebook/… with an API key, spend credits on live misses, and get a single JSON envelope back. No second SDK.
Send your key in the x-api-key header. The same key works across the SocialCrawl catalog.
Routes are GET. Pass handles, urls, queries, and cursors as query strings. We validate formats before charging.
Live misses debit the route tier. Cache hits cost 0. Empty or hard failures refund.
Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached.
Most products resolve an account, page content, then deepen only the posts that matter.
GET /v1/facebook/profileAuthor-shaped profile
Resolve the handle or id once.
GET /v1/facebook/profile/fullPostList of recent public items
Page with cursor or after when the route supports it.
GET /v1/facebook/profile/postsFull Post for one URL or id
List rows are not enough when you need the full record.
GET /v1/facebook/postCommentList when the platform exposes it
Expand only when a thread matters.
GET /v1/facebook/profile
?url=https://www.facebook.com/Meta
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here{
"success": true,
"data": { "/* Author | Post | PostList | CommentList | … */": true },
"credits_used": 1,
"credits_remaining": 9999,
"request_id": "req_…",
"cached": false
}Field names match the rest of SocialCrawl where archetypes align.
id, username, display_name, avatar_url, bio, followers, url, ext
items[].post with id, url, content, engagement, author, published_at, ext
items[] with author, content.text, engagement, published_at when comments ship
search hits, media metadata, or transcripts depending on route
Same request lifecycle as every other /v1 platform endpoint.
Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit and concurrency.
Registry lookup finds the route. Required params run first. Invalid input returns 400 with no charge. Valid calls debit before upstream work.
A deterministic cache key is built from platform + resource + params. Hit: credits_used = 0. Miss: upstream fetch with retries and circuit breaker.
Upstream JSON is mapped to Author / Post / PostList / CommentList (or route archetype), validated, wrapped in the success envelope, and logged for billing audit.
Billing rules that matter in production
Facebook is public-read data on SocialCrawl. We normalize it into the shared schema so your code does not learn a second OAuth flow.
Public Facebook surfaces exposed by the registry. Read-only for research, monitoring, and product jobs.
Social-read upstreams behind one gateway. Prism composites combine legs when a fat route is registered.
Unified JSON envelope: success, data, credits_used, request_id, cached. Shared Author / Post / Comment leaves where archetypes align.
No write endpoints and no private inbox. Disabled routes stay out of the active count. Prefer registry docs for the live inventory.
The jobs this API is most often used for.
Page monitoring and Ad Library research
Callers concentrate on profile, content lists, search, and deepen paths on Facebook. Organic page reads and Meta Ad Library search on one key and one envelope.
Detail reads are typically a few seconds on live miss. Search and fat composites are slower paths.
The jobs Facebook data is most often used for. Each one is a full recipe with the endpoint chain and pricing.
Common ways teams put this data to work, and the stack each one tends to run.
Poll profiles and feeds on Facebook. Alert when engagement velocity jumps.
Search and expand posts for brand, product, and competitor language on Facebook.
Wire resolve to list to detail into pipelines. Cache hits keep recurring runs cheap.
Live misses spend credits by tier. Cache hits are free. Empty or hard failures refund.
curl "https://www.socialcrawl.dev/v1/facebook/profile?url=https://www.facebook.com/Meta" \
-H "x-api-key: sc_your_api_key_here"curl "https://www.socialcrawl.dev/v1/facebook/profile/full?url=https://example.com/…" \
-H "x-api-key: sc_your_api_key_here"Same key as the rest of the catalog
Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.
Same Facebook data, two very different paths. Auth, rate limits, schema, and cost, side by side.
| Feature | SocialCrawl | Meta Graph API |
|---|---|---|
| Authentication | One x-api-key header | Access tokens via Facebook Login, scoped per permission |
| Setup / approval | Sign up and call in under a minute | Meta developer app, app review, and Business verification for many permissions |
| Rate limits | Pay per request in credits, with no per-app quota | Per-app and per-user rate limits |
| Data coverage | Public pages, posts, comments, groups, reels, events, Marketplace, and the Ad Library | Strongest for pages you manage; public-content access is heavily restricted |
| Response schema | Unified JSON envelope shared across 51 platforms | Graph node-and-edge payloads |
| Pricing | From 1 credit per request, 100 free credits to start | Free within rate limits |
| Maintenance | Schema stays stable when Facebook changes its frontend | Official support, plus publishing, insights, and messaging for owned pages |
Authentication
Setup / approval
Rate limits
Data coverage
Response schema
Pricing
Maintenance
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usAsk AI about SocialCrawl