Doors open Saturday at the new store. Come say hi.
1,204 86
juicer.io/facebook/api
Facebook Page posts, as JSON.
One key returns a Page's posts and Page profiles as the same normalized JSON as 14 other networks. No Meta developer app of your own, no permissions review, no token refresh.
curl "https://api.juicer.io/v1/data/posts?platforms=Facebook&term=yourpage" -H "Authorization: Bearer $JUICER_API_KEY"AI agents ready
Copy this prompt into the agent of your choice and get going right away.
I want to pull Facebook Page data through the Juicer API. Work from the official docs, not from memory.
1. Read https://developers.juicer.io first (or connect its docs MCP server, https://developers.juicer.io/mcp, no auth needed). The Quickstart and Authentication pages explain how to get going without a human signing up: POST /v1/authorize with an email returns a temporary API key, and a free Sandbox plan is available for a permanent one.
2. Then use the Juicer MCP server at https://api.juicer.io/mcp if you can, or the REST API at https://api.juicer.io/v1 with the key as a bearer token.
3. For Facebook: look up a Page's posts with platforms=Facebook and the Page username, and resolve a Page's profile with the profiles lookup. Follow the docs for term types and cursor pagination.
Task: resolve the Page <yourpage>, fetch its 10 latest posts and summarize the engagement.- Free Sandbox tier
- No Meta app review
- Cursor pagination
- MCP server included
Two ways in
Data API for any public Page. Integrations API for yours.
Both live behind the same key and return the same post shape. Pick by whether you manage the Page.
Data API Connection-free
Look up a public Page's posts or profile on demand with GET /data/posts and /data/profiles. Nothing to connect, fresh results per request, cursor pagination. 6 credits per Facebook sync when you import a Page this way as a source.
See the lookupsIntegrations API Connected Pages
Connect the Pages you administer through Juicer's OAuth, once. Juicer syncs them on your schedule for 1 credit per sync, applies your moderation rules, stores the history you read for free, and calls your webhook when a new post lands.
See syncs and webhooks01 / posts
Pull a Page's posts.
Pass the Page's username and get its recent posts: message, attached media, reactions and comment counts, posting time and the canonical URL. The same fields Instagram, TikTok and LinkedIn return, so one parser covers every network.
GET /data/posts in the docs →{
"data": [{
"platform": "Facebook",
"message": "Doors open Saturday at the new store. Come say hi.",
"poster": { "display_name": "Your Page" },
"media": [{ "type": "image", "url": "https://..." }],
"like_count": 1204,
"comment_count": 86,
"url": "https://www.facebook.com/yourpage/posts/..."
}],
"meta": {
"platforms": [{ "platform": "Facebook", "success": true, "has_more": true, "next_cursor": "..." }]
}
}
GET /v1/data/posts 200
02 / profiles
Resolve a Page to its profile.
Up to five handles per request. An exact handle match returns that Page with follower and post counts; otherwise you get candidates to disambiguate. Every profile carries every field, null where Facebook exposes nothing.
GET /data/profiles in the docs →{
"data": [{
"platform": "Facebook", "term": "yourpage", "exact_match": true,
"profiles": [{
"handle": "yourpage",
"display_name": "Your Page",
"url": "https://www.facebook.com/yourpage",
"verified": true,
"metrics": { "follower_count": 48210, "post_count": 1320, "total_view_count": null }
}]
}]
}
GET /v1/data/profiles 200
Your Page
facebook.com/yourpage
- Followers
- 48,210
- Posts
- 1,320
03 / your own pages
Sync the Pages you manage. Get a webhook.
Connect a Page you administer as a feed source and Juicer syncs it on a schedule for 1 credit per sync, applies your moderation rules, keeps the history readable for free and calls your webhook when new posts land. Connection-free lookups on Pages you don't manage cost 6 credits per sync.
Webhooks in the docs →{ "platform": "Facebook", "term": "yourpage", "term_type": "username" }
// later, on your endpoint
{
"event": "post.created",
"feed_id": 458351,
"post": { "platform": "Facebook", "message": "New this week ...", "url": "https://..." }
}
POST /v1/feeds/458351/sources 201
post.created https://yourapp.com/hooks/juicer delivered 200
Use cases
What teams build on the Facebook API
The same normalized posts serve product features, marketing sites and AI workflows.
Page posts inside your product
Show a customer's Facebook activity in your CRM, agency dashboard or community app without owning the OAuth flow. Connect their Page once and read it forever.
Curated walls for events and campaigns
Pull the Pages behind an event, a partner program or a campaign into one moderated stream and push the keepers to a site, a screen or a print pipeline.
Social proof for stores
Pull a brand's Page posts and reviews into product pages and checkout flows. Connected sources keep the proof current without a redeploy.
Monitoring and analytics
Archive posts and engagement counts for the Pages you track, yours and competitors', and chart follower growth, reactions and posting cadence over time.
Facebook data for AI agents
Give an agent get_data_posts and get_data_profiles through the MCP server and it can research a Page, summarize a campaign or draft replies with live context.
Retiring a hand-built Graph API integration
Replace Meta app review, expiring Page tokens and version deprecations with one endpoint that Juicer keeps working. Most teams migrate in a day.
Why use Juicer instead of the Graph API directly?
Reading Facebook yourself means a Meta developer app, an app review for every permission, Page tokens that expire, media URLs that expire faster, rate limits and a Graph API version that retires every two years. Juicer carries all of it through its own reviewed Meta app.
Build it yourself
A Meta app, a review, and a pager.
- Meta app review
- Page tokens expiring
- Media URLs expiring
- Graph API versions retiring
- Rate limits
- Moderation
- Webhook plumbing
- Engagement fields per version
Weeks to first post. Forever to maintain.
Juicer handles the heavy lifting.
With the Juicer API
One key. Same JSON as 14 other networks.
- No Meta developer app
- Page profiles with follower counts
- Cached media that keeps working
- Moderation applied before you read
- Webhooks on new posts
- Cursor pagination per platform
- MCP server for agents
- Free Sandbox to start
The developer surface
API, MCP, webhooks, docs.
Everything on this page is one key. Reads are free; only syncs of connected sources spend credits. Sandbox is free, Builder is $99 a month, Scale $499, Platform Partner from $2,500.
REST API
GET /data/posts and /data/profiles for connection-free lookups; feeds, sources, posts, moderation and analytics for the Pages you connect.
Read the referenceMCP server
33 tools for AI agents, including get_data_posts and get_data_profiles, on every API plan including the free Sandbox.
Connect an agentWebhooks
post.created and friends, delivered to your endpoint when a connected Page publishes. Test deliveries from the dashboard.
See the payloadsCredits and plans
Facebook connected source: 1 credit per sync. Premium source: 6. Reads of synced posts: free. The calculator sizes a plan for your sources and refresh rate.
Compare API plansQuestions
Frequently asked questions
What developers ask before pulling Facebook data through Juicer.
-
Do I need a Facebook developer app or Graph API access?
No. API lookups run against Juicer's own infrastructure: you pass a Page name and get JSON back. The only Meta login involved is optional: connecting a Page you manage as a feed source, through Juicer's OAuth, unlocks cheaper syncs and webhooks for that Page. -
Which Facebook lookups are supported?
On GET /data/posts, Facebook accepts term_type=username (a Page's posts). GET /data/profiles resolves Page handles to profiles with metrics. Reviews, visitor posts and mentions are feed source types: connect the Page in a feed and read them through GET /feeds/{id}/posts. -
Can I read personal profiles or Groups?
No. Facebook does not expose personal profile content or Group content to third parties, so neither the API nor a connected source returns them. Public Pages only. -
How does pagination work?
Each call returns one upstream page of results. meta.platforms[] carries has_more and an opaque next_cursor per platform; repeat the same request with cursor=<value> to continue. Cursors are per platform, so a multi-platform request paginates each network independently. -
How current is the data?
API lookups fetch fresh results at request time. Connected sources sync on the schedule you choose, from daily to every few minutes; more frequent syncs spend credits proportionally faster, and reads of what has already been synced are free. -
What does Facebook cost in credits?
Reads of already-synced posts are free. A connected Facebook Page source costs 1 credit per sync; a premium (connection-free) Facebook source costs 6 credits per sync, the highest of any network because Facebook data is the most expensive to collect. Sandbox is free; Builder is $99 a month for 750 credits, Scale $499 for 4,500, Platform Partner from $2,500. The API pricing page has the calculator. -
Is there an MCP server?
Yes. Juicer's MCP server exposes the Facebook lookups as get_data_posts and get_data_profiles, next to feed, source, moderation, analytics and webhook tools, so an AI agent can pull Facebook content without custom scrapers or OAuth flows. It is available on every API plan, including the free Sandbox. The full reference lives at developers.juicer.io. -
Can I display the posts instead of building a UI?
Yes. The same account gives you the Facebook feed widget: connect the Page, pick a layout and paste one embed code. Many teams use both, the widget for the marketing site and the API for the product.
