Withdraw many pending LinkedIn connection requests in one run. Async and scheduled modes help you free capacity for new outreach and keep outbound lists clean. To withdraw a single invitation, use the live Withdraw LinkedIn invitation action.
/v1/actions/linkedin-withdraw-invitations/run/asyncWithdraw pending LinkedIn invitations (bulk) cancels many pending outbound connection requests in one run so you free invitation capacity and clear stale outreach before a new campaign. You get a per-row result set showing which invites were withdrawn, which were already resolved, and which failed, plus an aggregate summary.
This action runs on the LinkedIn level and is built for outbound and growth teams who need to reset the pending queue en masse rather than one row at a time.
You pass a filter (age threshold, target list, keyword) or an explicit list of invitation IDs. Edges signs each withdrawal with your authenticated LinkedIn session, walks the list with paced timing, and records a result per row. Run it async for large batches; for smaller lists a live run returns end to end.
Everything runs on Edges infrastructure, browser-less. Pacing respects LinkedIn's activity guidance so you don't trip guardrails even when you're clearing thousands of stale invites. To withdraw a single invitation, use the live Withdraw Invitation action instead.
Reach for Withdraw pending LinkedIn invitations (bulk) when you're resetting the outbound queue before a new campaign, or when a scheduled hygiene job needs to process more rows than a per-record action can handle. It slots into the LinkedIn messaging & outreach API use case as the cleanup primitive between campaign cycles.
It's also the right action when the invite list comes from a CSV import, an extraction run, or a CRM export — anywhere the input is a batch rather than a single trigger.
The action scales to thousands of rows per run in async mode. For very large batches, Edges will stretch the withdrawals over hours to keep within safe pacing — you don't need to chunk client-side.
Your own LinkedIn account. Every withdrawal is signed by the session you connected to Edges and appears in your account's activity log, just like a manual withdrawal from the LinkedIn app.
Yes. A typical chain is Extract LinkedIn Sent Invitations → filter by age → Withdraw pending LinkedIn invitations (bulk) → log outcomes to the CRM. For per-row triggers, use Withdraw Invitation instead.
Run Withdraw pending LinkedIn invitations (bulk) from the Edges library, wire it into your hygiene schedule, or call it directly from the Edges API. Browse the full Actions library to see what to chain before and after the cleanup.
curl -X POST "https://api.edges.run/v1/actions/linkedin-withdraw-invitations/run/async" \
-H "X-API-KEY: <YOUR_API_KEY>" \
-H "Content-Type: application/json" \
-d '{
"identity_ids": [
"your-identity-uuid"
],
"identity_mode": "direct",
"parameters": {
"max_results": 10,
"last_page_start": true,
"max_pages": 10
}
}'[
{
"linkedin_invitation_id": "example-123",
"linkedin_invitation_urn": "example_value"
}
]