Skip to main content
Smart limits budget how many actions of each kind a LinkedIn account may perform per day. They are on by default for every connected account and every outbound call checks them server-side before dispatch: work that would exceed a budget is parked, not lost.

​
How budgets work

Every action type (connection requests, messages, profile visits, endorsements, and so on) has its own daily bucket. When a bucket is spent, further actions of that kind wait until the budget refreshes. Parked work resumes automatically as soon as the limit releases; nothing needs re-queuing.
Smart Limits tab showing the warmup percentage, six health signals and per-action daily caps

The Smart Limits tab of the account drawer: the warmup score with its six signals, incident logs, and the per-action caps below.

​
Warmup

A freshly connected account starts with reduced budgets that ramp up gradually. The ramp is driven by six live signals about the account, shown in the drawer: recent activity, concurrent sessions and IPs, blocks, limit hits, account age, and profile completeness. They multiply into the day’s allowance.
Warmup counts real sends: activity the account actually performed matters, not just time passed. A dormant account ramps slower than one that is actively and successfully working.

​
Limit statuses

​
Raise a limit, release a hold

Limits are editable per account in the drawer. Raising a limit offers reset hold, which atomically raises the budget and resumes everything parked on it in one step. Without reset hold, the raised budget takes effect on the next refresh cycle.
Hitting a budget over the API answers limit_exceeded. The action can resume the next day or after the limit is raised; the account is not penalized for your retry logic.