facebook

Get Facebook page profile

Returns a unified Facebook Author profile with page ID, display name, profile URL, profile image, bio (the page intro), follower count, page-like count, and creation date. Two things to know before grading on the numbers: author.followers is Facebook's ROUNDED public display figure (106,000,000 on the Meta page, where the exact page-like count alongside it reads 106,588,412), and author.joined_at is an ISO DATE (YYYY-MM-DD), not an instant, because Facebook publishes page creation to the day. A business page carries considerably more than a personal profile, and all of it rides in author.ext: business_category, website, links[], public_phone, public_email, address, price_range, rating (Facebook's recommendation string, e.g. "74% recommend (9,493 reviews)") with rating_count (that review count as a number), talking_about_count, cover_url, page_active, and ad_library_page_id / ad_library_status: the Ad Library page id is a different id from author.id and is the one /v1/facebook/adlibrary/company/ads takes, so you can chain profile → ads off a single lookup. A personal profile returns null for the listing fields it has no equivalent for rather than omitting them. links[] and business_hours[] are also mapped, the latter only when you pass get_business_hours=true, but Facebook returned both empty on every page measured on 2026-08-11, so treat them as best effort rather than data you can depend on. author.following and author.posts_count remain null because the upstream profile response does not provide those totals.

get/facebook/profile

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/facebook/profile
  • Auth: API key in header x-api-key

Query parameters

urlstring required

Full URL of the Facebook page or profile. A profile share link (https://www.facebook.com/share/…) is accepted.

get_business_hoursstring

Get the business's hours

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "facebook",
  "endpoint": "/v1/facebook/profile",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.