Rate limits
Limits are counted per key in a window of 60 seconds, so a script that goes wrong cannot flood a workspace.
| Kind of call | Calls per minute, per key |
|---|---|
| Reads | 120 |
| Writes | 30 |
| Operations that contact people | 30 |
A person may also set a daily limit on contact operations for one key or connection (at most 500 a day). Without it there is none beyond the account's own, and if the workspace requires approval for what agents send, a default of 20 requests a day keeps the queue small. See Contacting people.
Above the key there are two more counters, so that many keys or many rotations do not multiply a limit. One person in one workspace or organization may make 600 calls a minute across all their keys and connections there, and one organization may make 1,200 a minute across everyone.
When you hit a limit
The answer is 429 with the code rate_limited and a Retry-After header holding the number of seconds to wait. Wait that long, then retry. A steady retry loop with a short pause and a growing delay is the right shape.
curl -si "https://app.konekt.so/api/v1/workspaces/$WS/leads" -H "Authorization: Bearer $KEY" | head -n 5Staying inside the limits
- Ask for the largest page you need (
limit=200) instead of many small ones. - Poll the events feed with a cursor instead of re-reading lists. See Events and webhooks.
- Use a webhook if you have an address that is always up, so you need no loop at all.
Separately from these limits, every account has its own daily and weekly limits for what it does on LinkedIn. Those protect the account and are not changed by the API.