Look up a LinkedIn person

This route only reads. It never invites, messages or withdraws, and it keeps working when Settings → Agent → LinkedIn Sending is set to read-only, so you can watch LinkedIn relationships while Revnu sends nothing. Each call spends one of your LinkedIn account's 50 profile lookups a day. How Revnu paces LinkedIn to keep accounts safe is in LinkedIn Limits.

curl -G -H "Authorization: Bearer $REVNU_API_TOKEN" https://revnu.com/api/v1/linkedin/person \
  --data-urlencode "profile=https://www.linkedin.com/in/tom-park/"

Query

Response

{ "person": { providerId, publicIdentifier, name, headline } | null, "accounts": [account, …] }, one entry per connected LinkedIn account.

An account read in full is { account, connectedAs, state: "ok", connected, invite, revnuInvite, messages, messagesTruncated, lastReplyAt }:

• connected is true when this account and the person are first-degree connections.

• invite is the request LinkedIn reports between them, or null: { direction: "sent" | "received" | null, status: "pending" | "ignored" | "withdrawn", at }, where at is when it was sent (epoch milliseconds) if LinkedIn says.

• revnuInvite is Revnu's own record when Revnu sent the invite from this account: { sentAt, acceptedAt, withdrawnAt }. acceptedAt is when Revnu first saw the person connected, not LinkedIn's exact time.

• messages are the newest 50 in the conversation, oldest first: { at, from: "you" | "them", sentBy, kind, text }. sentBy is "agent" when Revnu sent it, "person" when someone replied from Revnu's inbox, and null when it was typed in LinkedIn. messagesTruncated says older messages exist.

• lastReplyAt is the time of their newest message, or null.

An account that could not be read has a state instead: not_connected, needs_reauth (reconnect it in the dashboard), paced with message and retryAt (the account's daily profile-lookup budget is spent), or error with message, including when no profile matches.

With LinkedIn sending set to read-only

This route keeps working when Settings → Agent → LinkedIn Sending is switched to read-only. Read-only stops every invite, message and InMail across the workspace, but profile lookups and conversations are reads, so connection state and the last 50 messages still come back. That makes read-only plus this route a safe way to watch LinkedIn relationships without Revnu sending anything.

Watching for changes

For people in one of your Revnu sequences, read linkedin on GET /leads instead. It carries when each invite was sent and accepted and when they replied, from Revnu's own records, and costs no lookups. This route is for people Revnu did not contact.

There is no route that lists all your connections, pending invites or conversations. Every lookup needs a profile, one person at a time. There are no LinkedIn events or webhooks either. To notice an accepted invite or a new reply, call this route for the people you care about on a schedule, such as once a day each, and compare connected, invite and lastReplyAt with what you stored last time. Every call spends lookups, so watch a short list, not your whole pipeline. For counts across the account, GET /results has linkedin.data.replies and invites for any window.