429 into a decision.
The five systems
Four of the five are ours. We set them below what LinkedIn tolerates, which is the point — an account stopped by an Edges limit is an account that did not get restricted by LinkedIn.
Plan rate limits
How many API requests your workspace may make per minute, counted separately for each family of endpoints — running actions, managing identities, reading workspace data, polling runs. This is about your integration’s traffic, not about LinkedIn.Concurrency
How many async runs Edges processes at once, and how each run is split into batches. This shapes how fast a large job finishes, not whether it is allowed. Submit as much as you like: extra runs queue and start as slots free up.Action limits
The quotas most people mean by “limits”. Each LinkedIn action type has its own allowance, tracked per identity, on rolling windows — per minute, and then longer windows up to 24 hours. Hitting one action’s limit leaves every other action on that identity untouched. A newly connected identity does not start at full allowance — see Identity Ramp-Up.Identity throughput
A ceiling on everything one identity does, whatever the mix of actions. Where action limits ask “how many connection requests today?”, this asks “how much total activity in the last minute?”. You will rarely meet it first; when you do, the answer is more identities rather than more patience.LinkedIn’s own limits
Everything above is ours. LinkedIn also enforces its own caps and protections on the account, and those are not published, not stable, and not something we can raise. We detect them and hand them back with a distinct label so you can tell them apart from ours — see Which limit was hit.Which of these you have to plan around
This is the practical question, and the answer depends on how you supply accounts.Bring your own accounts
You own the identities, so action limits are your ceiling. Capacity grows by adding identities, not by pushing one harder. Plan rate limits are unlikely to be what stops you.
Managed
You don’t own the identities, so your plan’s rate limits are your ceiling. Keeping enough capacity available is our job — you are not planning against per-account caps at all.
The quotas themselves are identical in both cases. What changes is who absorbs them.
Credits are not a limit
Credits are what a run costs; limits are what a run is allowed to do. Exhausting credits and hitting a limit are different failures with different fixes. See Credit costs for pricing.When a call is refused
Every limit rejection names the window it came from, so you can wait the right amount of time instead of backing off blindly.Which limit was hit
Every label, what it means, and how long to wait.
Recover a blocked run
Resuming work that stopped part-way.
Related
Action limits
Every quota, by account level, and which actions consume it.
Plan rate limits
What your API key may do per minute.
Identity Ramp-Up
Why a new identity stops earlier than the table says.