> ## Documentation Index
> Fetch the complete documentation index at: https://docs.edges.run/llms.txt
> Use this file to discover all available pages before exploring further.

# Identity Ramp-Up

> How a newly connected identity's capacity grows over its first days, what it applies to, and how to override it.

When an identity's integration is newly connected, Edges does **not** give it full capacity immediately. Capacity ramps up gradually over the first few days, then settles at the quotas listed in [LinkedIn Smart Limits](/v1/linkedin/limits).

<Info>
  **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](/v1/linkedin/limits) — those apply in full from the start.
</Info>

## How capacity is calculated

Full capacity is reached after **5 days**. Each day, an additional fifth is unlocked:

| Day since connection | Share of full capacity | Example: connection requests (full = 25 / 24 h) |
| -------------------- | ---------------------- | ----------------------------------------------- |
| Day 1                | 1/5 (20%)              | **5**                                           |
| Day 2                | 2/5 (40%)              | **10**                                          |
| Day 3                | 3/5 (60%)              | **15**                                          |
| Day 4                | 4/5 (80%)              | **20**                                          |
| Day 5+               | 5/5 (100%)             | **25**                                          |

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.

<Note>
  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.
</Note>

<Info>
  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.
</Info>

## Checking where an identity currently sits

Ramp-up is already reflected in the [Get Identity Limits](/v1/api/identities/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.

```bash theme={null}
GET /v1/identities/{identity_uid}/actions/{action_slug}/limits
```

<Tip>
  If a limit you hit doesn't match the quota table, check this endpoint before anything else — it accounts for ramp-up and for any custom limit configured on the integration, so it will tell you the number that actually applied.
</Tip>

## Overriding ramp-up

Limits are resolved in a fixed order of precedence:

<Steps>
  <Step title="Custom limits on the integration">
    If a custom limit is configured for the identity's integration, it is used as-is.
  </Step>

  <Step title="Ramp-up limits">
    Otherwise, if the integration account is still inside its ramp-up window, the ramped value applies.
  </Step>

  <Step title="Default limits">
    Otherwise, the standard quota for the account level applies.
  </Step>
</Steps>

Because custom limits are evaluated **before** ramp-up, **setting a custom limit on an integration effectively skips the ramp-up period** for that identity. This is the supported way to bring a known-warm account up to full capacity immediately.

Ramp-up is on by default for every identity, as a protective measure. If it doesn't fit your use case, [contact us](mailto:support@edges.run) and we can lift it for your workspace.

<Warning>
  Skipping ramp-up on an account that genuinely has little recent LinkedIn activity is the single riskiest thing you can do to it. Ramp-up exists because sudden jumps from near-zero to full volume are the pattern LinkedIn's automated protections weight most heavily. Only override it for accounts with an established history of normal use — see [Live Mode: Safe Practices](/v1/runs/live-mode-safe-practices#cold-account).
</Warning>

## Related

<CardGroup cols={3}>
  <Card title="LinkedIn Smart Limits" icon="shield" href="/v1/linkedin/limits">
    The full capacity an identity ramps toward.
  </Card>

  <Card title="Get Identity Limits" icon="gauge-high" href="/v1/api/identities/limits">
    Effective limits for one identity, ramp-up included.
  </Card>

  <Card title="How Limits Work" icon="layer-group" href="/v1/limits/how-limits-work">
    The five systems, and which ones apply to you.
  </Card>
</CardGroup>