Profile enrichment
Resolve public profile-oriented fields for verification and research workflows.
Use Facebook profile methods as part of enrichment, verification, monitoring, and cross-platform identity products where you need a consistent API.
ScrapeStorm is not affiliated with Meta or Facebook. Use only data you are permitted to process.
Facebook coverage is intentionally organized around currently supported profile data surfaces.
Resolve public profile-oriented fields for verification and research workflows.
Combine Facebook coverage with other supported platforms for broader profile intelligence.
Track API method health and response stability with the shared API status tools.
Browse every supported Facebook entity below, understand what each surface is for, and open the exact docs that matches your workflow.
Profile API methods resolve public identity, account context, and the base layer for creator, brand, or people-oriented products.
What you get. Use this entity to fetch account details, contacts, summary context, and the identifiers you need before moving into content or social API methods.
Open the API method that matches the lookup, feed, summary, or discovery job you need.
Start here when you need richer public context behind profile: About by user ID and want the most complete identity view first.
Start here when you need richer public context behind profile: About by username and want the most complete identity view first.
Open these docs when you need the actual profile content surface for monitoring, archive jobs, or reporting workflows.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Choose this API method when your product needs a compact performance view around profile without opening a larger content collection.
Each platform page follows the same decision path: choose the data surface, inspect the docs, validate the response, then scale with pricing and status visibility.
Use the coverage map to identify the entity group that matches your product workflow.
Review the implementation docs for method, path, query parameters, and response shape.
Prefer V2 API methods when you need stable fields across dashboards, scoring, or enrichment jobs.
Check API method pricing and operational status before moving a workflow into production.
Start with the representative profile API method and open the docs for request and response details.
user_idstrcurl --request GET \
--url "https://www.scrapestorm.net/api/v2/facebook.com/profile/about-by-user-id" \
--header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
--get --data-urlencode 'user_id=value'
X-API-Key
user_id
Facebook API method costs are listed in the same pricing table as the rest of the platform catalog.
ScrapeStorm is not affiliated with Meta or Facebook. Use only data you are permitted to process.
API method prices are visible before integration and credits are tied to successful API responses.
Each platform page links to the API reference and implementation docs for exact request and response details.
ScrapeStorm is independent from the listed platforms; your team remains responsible for permitted data processing.
These answers cover coverage, pricing, response formats, and launch details before you commit engineering time.
The product page reflects the currently supported public API surface, so the available groups mirror live generated API methods.
Yes. Open the API reference or implementation docs from the coverage section to inspect parameters and response models.