Skip to content

Unknown Query Parameter

URI: https://docs.ankatech.co/errors/unknown-query-parameter
HTTP Status: 400 Bad Request

When you see this

The request carried a query parameter the meta-audit operation does not declare. Such a parameter is refused rather than ignored: a parameter that is silently dropped produces a result set the caller believes was filtered when it was not. The check runs inside the handler, after authentication and authorization, so an unauthenticated caller receives 401 and an unauthorized one 403 — only a caller entitled to the operation ever learns that a parameter was wrong.

Common Causes

  • A typo in a parameter name, or a difference in case — the match is exact.
  • A client written against a different meta-audit operation: each operation declares its own parameter set, so a name valid on one is unknown on another.
  • A client speaking an older or newer contract than the operation actually has.
  • A parameter appended by a proxy or an analytics tool rather than by the client itself.

If the offending name is not printable and bounded, the detail says only that the request carries an undeclared parameter and does not echo the name back.

Response Example

{
  "type": "https://docs.ankatech.co/errors/unknown-query-parameter",
  "title": "Unknown Query Parameter",
  "status": 400,
  "detail": "'readerUser' is not a query parameter of this operation",
  "instance": "/api/v3/audit/meta/access-logs",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

How to Resolve

  1. Read the detail: it names the offending parameter exactly as it was submitted.
  2. Check the parameter against the operation's own declared set in /v3/api-docs. The refusal deliberately does not republish the vocabulary; the OpenAPI document, published to this same scope, is where it lives.
  3. Remove or correct the parameter and re-issue the query. A request carrying more than one defect always names the same one first, so fix them one at a time.

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