IP_LIST_LIMIT_REACHED
The account already holds as many IP lists as it may
A new allow or deny list was asked for when the account already holds the maximum number of lists.
- http status
- 409
- credits
- Nothing is billed for a failed request.
What it means
An account keeps a bounded number of IP lists, published as `meta.max_lists` on `GET /api/v1/ip/lists`, because every list is packed and scanned on every IP lookup the account makes. The entries themselves are the thing to grow: one list holds up to `meta.max_entries` addresses and prefixes.
Nothing is created and nothing is charged.
What to do
Add the entries to a list you already have with `PATCH /api/v1/ip/lists/{listId}`, or remove a list you no longer need with `DELETE /api/v1/ip/lists/{listId}` and create the new one.
Example response
{
"success": false,
"error": {
"code": "IP_LIST_LIMIT_REACHED",
"message": "This account already holds 20 IP lists. Remove one, or add the entries to a list you have.",
"request_id": "req_01m1kgdm4xngzmbmff68g94w0c"
}
}Every error carries the request_id also sent in the X-Request-Id header; quote it when writing to support.
Related
- RESULTS_NOT_READY · the bulk job has not finished yet
- JOB_ALREADY_FINISHED · the bulk job cannot be cancelled any more
- JOB_CANCELLED · the bulk job was cancelled before producing results
- JOB_FAILED · the bulk job failed before producing results
- JOB_NOT_RESUMABLE · the bulk job is not in a state a resume can recover
- JOB_INPUT_EXPIRED · the list the bulk job ran on is no longer stored
- JOB_NOT_FINISHED · the bulk run has not finished, so there is no completion webhook to send
- WEBHOOK_NOT_CONFIGURED · the bulk run has no webhook URL to deliver to
- IDEMPOTENCY_KEY_REUSED · the Idempotency-Key was already used for a different bulk request
- All error codes
- Verdicts and the risk score
- API reference
markdown version: /docs/errors/IP_LIST_LIMIT_REACHED.md