Rate Limit

Usage is governed by four separate per-account daily allowances. They are configured per plan rather than fixed by the API, so the exact numbers for your account come from your plan — what follows is how each counter is consumed.

• Search
  Consumed by POST /v1/contact/search — 1 per call.
• API
  Consumed by /details, /enrich and /bulk — 1 per profile submitted, so a batch of 10 consumes 10.
• Email
  Consumed by email delivery inside a request — 1 per address delivered.
• Mobile
  Consumed by mobile delivery inside a request — 1 per number delivered.

• The profiles array on /bulk must be non-empty and hold at most 10 entries. Larger arrays are rejected with 422 rather than truncated.
• Because the API counter is per profile, a 10-entry batch draws 10 from the daily API allowance — the same as ten single calls.

Exceeding an allowance returns 402 with a message naming the counter. Note that “out of credits” and “daily limit reached” share status 402 but carry different messages, and the remedies differ — buy credits, versus wait for the daily reset. Branch on the message, not the status.

• Insufficient Credits
  Your balance does not cover the maximum the request could cost. Remedy: buy credits.
• Search daily limit have been exhausted
  The daily search allowance is used up. Remedy: wait for the daily reset.
• Api daily limit have been exhausted
  The daily request allowance is used up, or the batch size would exceed it. Remedy: wait for the daily reset.

Expect completion typically within minutes, and always poll GET /v1/contact/enrich?id= or use a webhookUrl rather than assuming a fixed latency.

If you're a technology partner requiring higher daily allowances or increased queue capacity for parallel processing, contact us to discuss custom options.