LinkedIn invitation limit check: pending invitations sent (free)
linkedin.invitations_sent
liveThe pending connection requests on your connected account, counted today (the day starts again at 00:00 UTC) and over the last 7 days against the caps (30 a day on RouterGrowth, 20 in the account's first week connected; roughly 200 a week on LinkedIn; about 5 with a note a month on a free account), with how many more to send now and the recent invitations with their notes. Free. Run it before a batch of linkedin.invite.
Unipile:
all inputs
✓ marks a combination proven with a real provider call. Others are wired and unit-tested; their first live run verifies them.
Providers
| Provider | Status |
|---|---|
| Unipile |
live |
Billing
Unit: per_call · unmatched results billed: no
Free. Counts are a floor: accepted and withdrawn invitations leave LinkedIn's pending list, and LinkedIn does not publish its caps.
The exact quote is returned by /v1/inspect before every call and held with headroom on execution. The quote is the price floor: if the provider's actual cost overruns it, the run bills the overrun at the same rate, never above the hold. The unused part of every hold is released.
Run it
curl https://api.routergrowth.com/v1/run \ -H "Authorization: Bearer $ROUTERGROWTH_API_KEY" \ -d '{ "capability": "linkedin.invitations_sent", "input": { }, "routing": {"provider": "auto"} }'
Input schema
{
"properties": {
"account_id": {
"description": "The account name (or id) from linkedin.accounts; optional when you have one account",
"type": "string"
}
},
"type": "object"
}
Normalized output fields
pending · sent_today · last_24h · last_7d · remaining_today · resets_at · remaining_this_week · invitations · next_step