Get Available LinkedIn Contact Information
View all LinkedIn Data API endpoints →Pass a public username to read available professional contact information. The documented data object contains first_name, last_name, public_identifier, urn, email, phone_numbers, websites, twitter, address and wechat; some values are null or empty arrays. Availability varies, and a returned email is not evidence that it is verified or that its owner consented to outreach. Use only permitted fields in consent-managed workflows and provide appropriate retention and deletion controls.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/linkedin-scraper/get-user-contact API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/linkedin-scraper/get-user-contact?key=<API_KEY>&username=<username>'
Query Result
Use Cases
- Fill available contact fields in an existing consent-managed CRM record.
- Let an opted-in directory member review returned professional websites.
- Preserve empty contact channels instead of replacing them with guessed values.
- Route newly returned contact information to a permission and retention review.
Frequently asked questions
Will every profile return an email address or phone number?
No. Contact information can be missing, null or represented by empty arrays. Do not promise hidden contact details, and do not infer a channel from a name or employer.
Is a returned email verified or approved for outreach?
No such guarantee is established. A contact field is data, not consent or deliverability verification. Apply the permissions, retention and deletion rules appropriate to your workflow.