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

Username-based contact read Request available contact fields for a selected public profile rather than a bulk contact list.
Nullable channel fields email and other fields may be unavailable; phone_numbers and websites can be empty arrays.
Professional website context Keep returned websites and other available channels distinct from inferred or guessed addresses.
Consent-managed enrichment The result does not verify a contact channel or provide permission to send messages.

Live API Demo

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

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-contact?key=<API_KEY>&username=<username>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →