Accept many pending LinkedIn invitations in one automated run. Use async or scheduled execution to process your inbox at scale and grow your network faster. For a single invitation, use the live Accept LinkedIn invitation action.
/v1/actions/linkedin-accept-invitations/run/asyncAccept pending LinkedIn invitations (bulk) clears your pending-invite queue in one run, so dozens or hundreds of requests move from Pending to Accepted without you touching the LinkedIn inbox. It runs on the LinkedIn level against the account you connect to Edges, which means every accept is executed through your authenticated session and shows up in that account's activity log.
Use it when accept decisions are periodic rather than per-record — a scheduled sweep of the inbox, a post-event mop-up, or a weekly "accept everyone still pending from last month" routine.
You trigger one run and Edges paginates through your pending invitations list, accepting each one in sequence on LinkedIn infrastructure. The action ships as an async or scheduled job because volume-heavy inbox processing takes longer than a single API call and should respect LinkedIn pacing guidance. Edges handles rate limits, retries transient failures, and exposes a final status per invitation so you can reconcile which ones were accepted and which were skipped.
Because the action runs against your connected LinkedIn session, you do not need cookies, headless browsers, or proxy management on your side. You get a structured list of results back, ready to merge into your CRM or data warehouse.
Reach for this action when you want a weekly or monthly catch-up on inbox hygiene, or when you have accumulated pending requests while building audience. It is the batch counterpart to the single-record Accept Invitation, and it plugs directly into the LinkedIn messaging & outreach API workflow — accept in bulk, enrich, then queue first-touch messages.
Do not use it as your primary accept logic if decisions are event-driven per lead; pair the single-record action with a CRM trigger instead.
senderFilter or a pre-filter step.Edges does not impose a hard cap, but LinkedIn's per-account activity ceiling effectively limits throughput to low hundreds per day. Split very large backlogs across multiple scheduled runs to stay comfortably under the guardrails.
Your LinkedIn account. You connect LinkedIn to Edges once; every accept in the bulk run is executed through that authenticated session. There is no shared pool and no credential sharing.
Yes. Common chains include Extract LinkedIn Profile right after the accept to enrich new connections, followed by Message LinkedIn Profile to send a first-touch message to the freshly-accepted cohort.
Schedule Accept pending LinkedIn invitations (bulk) from the Edges library, wire the output into your CRM or warehouse, or call it from the Edges API. Browse the full Actions library to see what you can chain before and after the sweep.
curl -X POST "https://api.edges.run/v1/actions/linkedin-accept-invitations/run/async" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct"
}'[
{
"linkedin_invitation_id": "example-123",
"linkedin_invitation_urn": "example_value"
}
]