API errors and rate limits
What each error code means, how to fix it, and how many calls a key can make per minute.
Every error has the same shape and a matching HTTP status. The requestId (also sent as the X-Request-Id header) is what support needs to look at your call.
{ "error": { "code": "invalid", "message": "Give the campaign a name.", "requestId": "…", "fieldErrors": { "name": "Give the campaign a name." } } }| Status | Code | What it means | What to do |
|---|---|---|---|
| 400 | invalid_json | The body isn't valid JSON | Check the JSON |
| 401 | unauthenticated | The key is missing, mistyped, revoked or expired | The header must read Bearer, a space, then the key. Make a new key if needed |
| 402 | billing_paused, limit_reached | The subscription is paused or past due, or a plan limit was reached | Check Settings, Billing. Pausing and stopping always work |
| 403 | forbidden | The key's access level is too low for this call | Use a higher level, such as Admin to launch |
| 404 | not_found | No such thing in this workspace | Check the ID. Something in another workspace looks the same as nothing |
| 413 | payload_too_large | The body is over 5 MB | Send fewer rows per call |
| 415 | unsupported_media_type | No JSON content type | Add Content-Type: application/json |
| 422 | invalid | Valid JSON, but not valid input | Read fieldErrors: it names the field and says what's wrong |
| 429 | rate_limited | Too many calls this minute | Wait the seconds in Retry-After, then retry |
| 503 | unavailable | Temporarily unavailable | Retry after a few seconds |
| 500 | unknown | Our fault | Send us the requestId |
#Rate limits
Limits are per key, per minute, by the kind of call:
| Kind | Per minute | For |
|---|---|---|
| Read | 60 | Reading data |
| Write | 20 | Changes that never touch LinkedIn: create or edit campaigns, set do-not-contact, pause |
| Bulk | 10 | Adding up to 500 people to a list in one call |
| Enqueue | 5 | Anything that starts LinkedIn activity: launch, resume, add leads to a campaign |
Responses include X-RateLimit-Limit and X-RateLimit-Remaining. A 429 includes Retry-After. Rejected 429s don't count against you, so waiting out Retry-After is always enough. Sending more rows per call (up to 5,000 for a list import) is better than sending more calls.
Was this article helpful?