Skip to content

Log Fingerprint Rate Limited

URI: https://docs.ankatech.co/errors/log-fingerprint-rate-limited
HTTP Status: 429 Too Many Requests

When you see this

The caller has already computed 10 log fingerprints in the current minute, or 200 in the current day. Nothing was computed and nothing was recorded in the audit trail. The bound is per caller and is counted in a shared store, so it holds across every Admin API instance. Retry-After states how many seconds remain until a computation is admitted again.

The operation confirms a guessed identifier for its caller, so the bound limits how many guesses one caller can check.

Common Causes

  • A script that computes the fingerprints of many identifiers in a loop.
  • An investigation that computes the same identifier repeatedly instead of keeping the values the first answer returned.

Response Example

{
  "type": "https://docs.ankatech.co/errors/log-fingerprint-rate-limited",
  "title": "Log Fingerprint Rate Limited",
  "status": 429,
  "detail": "Too many log fingerprint computations by this caller; nothing was computed. Retry after the time the Retry-After header states.",
  "instance": "/api/v3/admin/platform/log-fingerprints",
  "timestamp": 1761390000,
  "extensions": {
    "requestId": "4b2e8f1a-6c3d-4e9b-a7f0-1d5c2e8b9a63"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details. The response carries Retry-After in seconds.

How to Resolve

  1. Wait the number of seconds Retry-After states, then compute again.
  2. Keep the fingerprints an answer returned: they do not change until the log fingerprint key is rotated, and one answer already carries the value of every mounted key version.

Operations that emit it

Method Endpoint
POST /api/v3/admin/platform/log-fingerprints

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.