Lusha · Rate Limits

Lusha Rate Limits

Lusha enforces per-plan rate limits across three simultaneous windows — per minute, per hour and per day — and returns the full remaining/used/allowed triple for each window on every response. The numeric ceilings vary by plan and are not published (the docs point you at the help centre or your account manager), with two exceptions the docs do state outright: the Webhooks family is capped at 100 requests/minute per account, and bulk subscription create and delete take at most 25 items per request. On exhaustion the API returns 429.

Lusha Rate Limits is the machine-readable rate-limit profile for Lusha on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 13 rate-limit definitions, measuring requests, items, contacts-or-companies, companies, and entities.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and quota_exceeded.

Tagged areas include Sales Intelligence, B2B, Enrichment, Contact Data, and Prospecting.

13 Limits Throttle: 429
Sales IntelligenceB2BEnrichmentContact DataProspectingIntentRate LimitingQuotasThrottling

Limits

Webhooks API requests per-account
requests
100
Stated outright in the Webhooks section of the API reference.
Create Subscriptions batch size per-request
items
25
Delete Subscriptions batch size per-request
items
25
Standard endpoint limits (per minute) per-plan
requests
Published as a header pair (x-rate-limit-minute / x-minute-requests-left); the numeric ceiling depends on plan and is not published.
Standard endpoint limits (per hour) per-plan
requests
numeric ceiling not published; read x-rate-limit-hourly at runtime.
Standard endpoint limits (per day) per-plan
requests
numeric ceiling not published; read x-rate-limit-daily at runtime.
Credit Usage API per-account
requests
Docs state the Credit Usage API carries different limits from standard endpoints, without giving the figures.
Bulk request size per-request
contacts-or-companies
100
Maximum 100 contacts or companies per request; minimum 1 credit per request.
Buying Group companies per request per-request
companies
25
Signal Score entities per request per-request
entities
100
Tables entity IDs per add/remove call per-request
entity-ids
500
Entities per table per-table
entities
50000
Tables per account per-account
tables
500

Policies

Backoff Strategy
Exponential backoff on 429/5xx per the docs (1s, doubling, 60s cap). No Retry-After header is documented, so the client owns the schedule.
Read the window headers
All three windows are reported on every response; an agent should gate on x-minute-requests-left / x-hourly-requests-left / x-daily-requests-left rather than on a published number.
Bulk over single
Bulk requests (up to 100 entities) cost 1 credit per 1-25 results, so batching lowers both request count and credit burn.

Sources