Facebook URL to ID Converter - Page Identifier Lookup

Resolve Facebook Page usernames and supported Page URLs into numeric identifiers and a compact identity record. Facebook URL to ID Scraper returns the available profile ID, Page ID, name, public link, picture and verification flag, with one row per processed target.

Use this focused lookup to match Page references across databases or prepare inputs for other tools. Its single table and JSON export contain the same nine scalar fields.

At a glance	Details
📥 Input	Page usernames, numeric identifiers or supported Page URLs
📤 Output	Profile ID, Page ID, requested identifier and public identity fields
📄 Collection	One lookup per distinct queued target
🔐 Facebook login	Not required
💾 Delivery	Nine scalar columns, matching JSON and dataset exports

What the Facebook URL to ID scraper returns 🔢

The Actor resolves the public identity behind a Page reference. It returns id and the separate page_id when available, plus a name, public profile URL, picture and verification flag.

IDs remain strings so long numbers are not rounded in your application. The username field contains the normalized requested identifier; it can be a number when the input resolves from a numeric or legacy Page URL. It does not promise to discover the current vanity name.

How to resolve a Facebook URL to an ID 🚀

1. Add Page usernames or supported Page links to inputList.
2. Keep every input as a string, including numeric identifiers.
3. Start the Actor and inspect the ID and status columns.
4. Export the mappings or join them to your existing records.

{"inputList":["Meta","https://www.facebook.com/NASA/"]}

For a numeric Page reference, https://www.facebook.com/profile.php?id=20531316728 is an accepted URL form. Use your own public targets when preparing a production run.

Facebook ID data fields and output 📦

Field group	Included data
Request context	Original input and success or failed status
Identifiers	Profile ID, available Page ID and normalized requested identifier
Public identity	Display name, profile URL, picture URL and verification flag

Complete illustrative success row; the sample Page and its identifiers are not a live lookup claim:

{
  "input": "harborartscollective",
  "status": "success",
  "id": "100200300400500",
  "page_id": "100200300400500",
  "username": "harborartscollective",
  "name": "Harbor Arts Collective",
  "profile_url": "https://www.facebook.com/harborartscollective/",
  "profile_picture_url": "https://images.example.com/harbor-arts.jpg",
  "is_verified": false
}

Every field is a scalar in the same table and JSON object, so no nested-record handling is needed. Successful optional fields may be empty strings or false when the public source omits them. A failed row retains input, uses status: failed and sets the seven identity fields to null.

Input requirements and Page coverage ⚙️

Parameter	Type	Required	Default and limits
inputList	Array of strings	Yes	At least one item; no default target or configured item-count maximum

Accepted forms include a plain Page username, a numeric string, a direct Page URL, profile.php?id=NUMERIC_ID, and a legacy /pages/NAME/NUMERIC_ID URL. Standard, mobile and web Facebook hosts are supported. Bare identifiers may contain letters, digits, dots, underscores or hyphens and be up to 100 characters long.

Do not supply a leading @, group or event link, or a post, Reel, photo or video URL. This is a Page identity lookup rather than a general converter for every Facebook content type. There is no pagination setting.

Repeated inputs that normalize to the same queued target are normally handled once. Different aliases may require separate lookups, so use the returned IDs when matching records.

Facebook identifier use cases 🎯

Page record matching

Connect Page links from different datasets to numeric identifiers while retaining the original input for traceability.

Data preparation

Resolve known public references before using a downstream service that expects a numeric Page ID.

Directory maintenance

Keep a compact mapping of Page names, URLs and IDs without collecting a full Page detail record.

Link validation

Separate successful identity lookups from malformed or unavailable references before starting a larger enrichment job.

Pricing and billable ID lookup rows 💰

Check the Actor's Pricing tab for the current model and rate. Under dataset-item pricing, each saved success or failed lookup row can count as a billable result.

Automatic retry attempts do not independently create rows. Duplicate normalized targets are normally queued once, but distinct aliases are not guaranteed to collapse into one record before lookup.

Facebook URL to ID API and integrations 🔌

Replace $ACTOR_ID with the ID from the Actor API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["Meta","https://www.facebook.com/NASA/"]}'

Use the dataset as a lookup table in a spreadsheet, CRM or database. Scheduled runs, webhooks and Apify integrations can connect this mapping step to a broader workflow.

Reliability and identifier limits ⚠️

The Actor retries temporary request failures and returns a failed row when a lookup remains unavailable. Bad references are handled independently of valid inputs; startup or dataset storage failures can still interrupt the run.

Facebook can rename, restrict or remove Pages and omit optional fields. Profile IDs and Page IDs can represent different identifiers; keep both rather than assuming they are interchangeable. No identifier is guaranteed permanent by this tool.

Frequently asked questions ❓

Can I submit Page URLs as well as usernames?

Yes. Direct Page links and supported numeric or legacy Page URL forms are accepted alongside plain usernames.

Does it resolve post, event or group IDs?

No. Use the corresponding Facebook actor for those entities. This Actor focuses on public Page identity references.

Why is username a number in my result?

That field retains the normalized requested identifier. Numeric Page references can therefore produce a numeric string there.

Are id and page_id always the same?

No. They are separate source fields. Either may differ, and the Page-specific value may be absent.

Do I need Facebook credentials?

No Facebook login or cookies are requested. Restricted identities can still be unavailable to the Actor.

Support, responsible use, and related actors 🛟

Share the run ID and a safe public Page reference that reproduces the issue. Do not include credentials or API tokens.

Use public identity data in accordance with applicable privacy and platform requirements.