Ramp-up is not per-action. It applies across the per-action quotas tied to that identity — connection requests, profile visits, messages, searches, enrichments — rather than to one action or one category. If you are hitting a limit sooner than the quota table suggests on a recently connected identity, ramp-up is the first thing to check.It does not change the identity-wide throughput caps (per second, per minute, per 15 minutes, and so on) listed in Smart Limits — those apply in full from the start.
How capacity is calculated
Full capacity is reached after 5 days. Each day, an additional fifth is unlocked:
The ramped value is rounded up, and it is never lower than 1 — so even on day 1, every limit allows at least one call.
The ramp is measured from the identity’s first sync, not from your first API call. An identity connected and left idle still finishes its ramp-up on schedule.
Ramp-up scales the window quota — the 24-hour allowance. The shorter caps on the same limit (per minute, per 15 minutes, per 4 hours) apply at full strength from day one, so a ramping identity can still be stopped by a burst.
Checking where an identity currently sits
Ramp-up is already reflected in the Get Identity Limits endpoint. That endpoint is the only place that returns the effective limit for a specific identity right now — the quota tables in the documentation show full capacity, which a ramping identity has not reached yet.Overriding ramp-up
Limits are resolved in a fixed order of precedence:1
Custom limits on the integration
If a custom limit is configured for the identity’s integration, it is used as-is.
2
Ramp-up limits
Otherwise, if the integration account is still inside its ramp-up window, the ramped value applies.
3
Default limits
Otherwise, the standard quota for the account level applies.
Related
LinkedIn Smart Limits
The full capacity an identity ramps toward.
Get Identity Limits
Effective limits for one identity, ramp-up included.
How Limits Work
The five systems, and which ones apply to you.

