Resolve a LinkedIn profile by its public identifier (the username in linkedin.com/in/<identifier>) from this sender account. A silent read — no profile view is registered.
Authorization
bearerAuth An API key created under Settings → API & Webhooks.
In: header
Path Parameters
The profile's public identifier (username), e.g. "john-doe".
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/accounts/string/profiles/string"{ "data": { "profileUrl": "string", "publicIdentifier": "string", "firstName": "string", "lastName": "string", "fullName": "string", "headline": "string", "picture": "string", "relationship": { "status": "not_connected", "degree": 1, "openProfile": true, "canMessage": true, "canInvite": true } }}List direct actions GET
The direct actions (connection requests, messages, InMails, profile views) taken from this sender account, newest first.
Send a connection request POST
Send a LinkedIn connection request from this sender account to a profile, with an optional note. Notes are a premium feature capped at 300 characters; free sender accounts can't include one, so their invites are sent without the note. The profile is tracked as a lead and a connection.accepted webhook fires when it is accepted. Returns 409 when an invitation to the profile is already pending, or 429 when the sender hit its daily cap or its weekly connection-request limit (tier-based: about 130 invites per week for free accounts, 150 for paid; admin-configurable), unless the workspace has the limit bypass enabled.