Facebook profile resolver API
GET /resolve/profile · base https://api.getsocialapi.com/fb
Resolve a profile link to a numeric user_id — the id required by
contacts (About),
followers,
followings and
friends.
Request
| Parameter | In | Required | Description |
|---|---|---|---|
url | query | yes | Link to a Facebook profile (any type) |
Accepted link shapes (illustrative — the API accepts the shape, but any specific profile may be deleted or hidden):
https://www.facebook.com/nasa— username slughttps://www.facebook.com/profile.php?id=100044561550831— numeric profile URLhttps://www.facebook.com/people/Mark-Zuckerberg/4—peoplepathhttps://m.facebook.com/zuck— mobile mirrorhttps://www.facebook.com/share/p/AbCdEf123/— share link
Example
curl -G "https://api.getsocialapi.com/fb/resolve/profile" \
--data-urlencode "url=https://www.facebook.com/nasa" \
-H "X-API-Key: gsa_live_..."
Response
{
"url": "https://www.facebook.com/nasa",
"user_id": "100044561550831",
"name": "NASA - National Aeronautics and Space Administration"
}
| Field | Type | Description |
|---|---|---|
url | string | The input link |
user_id | string | Numeric user id |
cached | bool | Present when the id came from the resolver cache — omit the flag in your logic, it is informational only |
note
The example profile is verified to exist, but third-party profiles are not
stable — a deleted or hidden profile resolves to 404, which is a valid
outcome (counted as a successful lookup).
Errors
| HTTP | Body | Meaning |
|---|---|---|
401 / 403 / 429 | — | see Rate limits |
404 | {"error": "profile not found", "url": "..."} | hidden, deleted or non-existent profile |
note
404 responses are charged — like 200, they count as successful lookups (see Rate limits).