The Facebook Profile Scraper API lets you retrieve public information from a Facebook page or profile by its handle, together with the posts on the page. It returns name, category, bio, exact likes and talking-about counts, followers and following, website, phone, the page owner, profile and cover photos, the photo tiles, and the posts with their text, media, reaction breakdown, comment and share counts.
HasData is an independent service and is not affiliated with, endorsed by, or sponsored by Facebook. Facebook is a trademark of its respective owner. This API works with publicly available data only.
Get Your API Key
Sign in at hasdata.com, go to your account settings, and copy your API key.
All requests must include your key in the x-api-key header.
Request Cost and API Credits
Each request to the Facebook Profile Scraper API consumes API Credits from your account balance.
Cost per request: 10 API Credits
Credits are deducted only for successful requests.
Your total available credits depend on your active plan.
You can use your credits across all HasData APIs. The same credit balance is shared platform-wide.
Unused credits do not roll over. Any remaining credits expire at the end of the current billing period.
To monitor your credit usage and remaining balance, sign in to your account dashboard at app.hasdata.com.
The Facebook username of the page or profile you want to scrape, with or without the @ symbol, or its numeric profile id (the id of a profile.php?id=… URL), e.g. nike or 61550916779928. Groups and private personal accounts are not supported.
language
-
No
Language the page is rendered in. Facebook serves a page in the language of the request, so this changes the localised strings (followersCount, followingCount, category) while the exact figures (likesCount, talkingAboutCount) stay numeric in every language.
nextPageToken
-
No
Token from the pagination.nextPageToken field of a previous response; the page it leads to is reported as pagination.nextPage. Each paginated request returns the next three posts of the feed and a fresh token; the token is absent once the feed ends. Every request is billed separately.