LinkedIn Profile API - Username to Professional JSON

Pass the public username from a LinkedIn /in/ profile URL, not the entire URL or display name. A successful live lookup returned data.id, urn, public_identifier, full_name, headline, location, avatar, cover, profile flags, website and locale fields. Optional include_* booleans request additional sections and can increase request consumption. An inaccessible or nonexistent profile was observed with HTTP 200, success:false, data:null and status_code:403; early HTTP 202 responses also carried business failures. Check success and message before using data.

API Features

Public-handle input Supply the username segment of the profile URL, such as the observed public handle williamhgates.

Professional identity object The observed data object includes full_name, headline, location and public_identifier.

Section-by-section expansion Choose include_experiences, include_educations and other flags only when those sections are needed.

Explicit access-failure contract Business success is separate from HTTP status; an inaccessible profile can return data:null with status_code:403.

Live API Demo

GET /api/project/linkedin-scraper/get-user-profile

Username *

Include bio (optional)

Include certifications (optional)

Include educations (optional)

Include experiences (optional)

Include follower and connection (optional)

Include honors (optional)

Include interests (optional)

Include publications (optional)

Include skills (optional)

Include spoken languages (optional)

Include volunteers (optional)

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-user-profile?key=<API_KEY>&username=williamhgates'

curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-user-profile?key=<API_KEY>&username=williamhgates'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Refresh the headline and location of a consent-managed professional record.
Resolve a supplied profile URL to its username in application code and retrieve structured identity.
Retain a selected profile's returned urn for later experience or skill requests.
Build an editable opt-in directory card using available public profile fields.

Frequently asked questions

Why can HTTP 200 still return no profile?

HTTP success does not guarantee business success. The observed inaccessible-profile response contained success:false, the message This profile can't be accessed or not exist, data:null and status_code:403. Inspect those fields rather than treating null as a usable profile.

Should I enable every include_* option?

No. Request only the sections your application needs. These flags can increase request consumption, sections may remain unavailable, and media URLs have expiration metadata rather than permanent availability.

Related operations

Guides

View Subscription Plans →

Get LinkedIn Profile by Username