The invitations the account sent that are still pending, a page of limit. Pass cursor back for the next page; null on the last.
Your API key from the console (gw_live_…).
In: header
Query Parameters
The LinkedIn account (lg_…) to act as.
1 <= lengthInvitations per page, 1 to 100. Default 100.
1 <= value <= 100100The cursor the previous page answered, passed back unchanged, for the next page. Leave it out for the first page; a null cursor means there is no next page. Opaque: its form differs by route.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/v1/users/invite/sent?account_id=lg_3f9c2a7b1d"{ "object": "UserInvitationList", "items": [ { "object": "UserInvitation", "id": "7391827364519283746", "invited_user_id": "ACoAAB1a2b3c4d5e6f", "invited_user_public_id": "jane-doe", "invited_user": "Jane Doe", "date": "2026-10-29T10:00:00.000Z" } ], "cursor": null}Connections GET
The connections, newest first, a page of `limit` (at most 40, as LinkedIn's connections page loads). Pass `cursor` back for the next page; `null` on the last. Some accounts can page through their newest 200 connections only: past them the list ends (`cursor` is `null`).
Send an invitation POST
A write (`invite`, plus a `visit` when the profile is opened on the way). A note over 300 characters is refused (422 `too_many_characters`), never cut. LinkedIn's refusals: 422 `errors/cannot_resend_yet` (its limit, or too soon to invite again: cool the sender down) and `errors/already_invited_recently` (already pending: treat as sent).