On this page

Credits & rate limits

Credits

ActionCredits
POST /campaigns/:campaignId/leads (successful insert)1
POST /campaigns/:campaignId/leads/batch (per successful create)1 each
Duplicate / excluded / invalid (no insert)0
POST /campaigns/lookalikeLookalike allowance (reserved at launch; unused refunded)
Control writes (start, pause, create/rename/delete campaign, assign template, tags write, templates write, account connect/reconnect/disconnect/delete, patch limits)0
GETs, search, lookup, send, preview, patch lead, batch-update, batch-delete0

Insufficient normal credits → 403 insufficient_credits. Insufficient Lookalike → 403 insufficient_lookalike_credits.

Global ceiling

All /public/v1/* requests share 120 requests / minute per API key.

Per-route limits (per API key)

Route / classLimit
Add lead (POST …/leads)60 / min
Add leads batch (POST …/leads/batch)10 / min (max 100 items)
Batch update (POST …/leads/batch-update)6 / min (max 100 items)
Batch delete (POST …/leads/batch-delete) and single delete (DELETE …/leads/:leadId)10 / min shared (batch max 100 items)
Patch lead (PATCH …/leads/:leadId)60 / min
Control writes (start, pause, create/rename/delete campaign, assign template, tags write, templates write, account connect/reconnect/disconnect/delete, patch limits)30 / min shared
Send message (POST /inbox/messages)10 / min
Profile lookup (POST /linkedin/profiles/lookup)5 / min per key; 1 / 20s per LinkedIn account; 80 / day classic or 150 / day Sales Navigator / Premium
Search (POST /linkedin/search)6 / min per key; 1 page / 15s per LinkedIn account; daily people-retrieval quota (same as in-app search)
Lookalike (POST /campaigns/lookalike)6 / min
Lead preview (POST …/leads/:leadId/preview)Global ceiling only
Other GETsGlobal ceiling only

Search page size: max 50 (classic) / 100 (Sales Navigator). Cursor pagination: each page counts as one rate-limit unit. Daily people-retrieval quota counts each person returned (not just “per call”). MCP search_linkedin_until paces the same route (~16s between pages, targetCount max 50) — still 0 ScaliQ lead credits.

On 429, wait for Retry-After (or details.retryAfterSeconds) before retrying.

Idempotency

Supported on these 10 POST routes only:

  1. POST /campaigns/:campaignId/leads
  2. POST /campaigns/:campaignId/leads/batch
  3. POST /campaigns/:campaignId/leads/batch-update
  4. POST /campaigns/:campaignId/leads/batch-delete
  5. POST /campaigns
  6. POST /campaigns/lookalike
  7. POST /tags
  8. POST /templates
  9. POST /campaigns/:campaignId/template
  10. POST /inbox/messages
Idempotency-Key: <uuid>

Max 128 characters; longer or malformed → 400 validation_error.

SituationResult
Same key + same body within 24 hours after a 2xxReplays the stored response; no second side effect
Same key, different body409 conflict
Same key while the first request is still in flight409 conflict (may include retryAfterSeconds)
Key cannot be recorded503 — nothing was performed; safe to retry the same key
Retry after a non-2xxReservation released — request runs again

Requests without Idempotency-Key are unaffected. Only successful (2xx) responses are stored for replay.

Request body size

Bodies are capped at 128 KiB. Over the cap → 413 validation_error (details.maxBytes).