Conflicting keys

HTTP 400 · token-conflict — ← all Webpath errors

A header key and a query key were both sent and disagree.

How to recover. Send the key exactly one way — header or query, not both.

Example response

{
  "type": "https://muse.as/a/webpath/errors/token-conflict",
  "title": "Conflicting keys",
  "status": 400,
  "detail": "Send the key exactly one way \u2014 header or query, not both."
}

This page documents the token-conflict error type returned in Webpath RFC 7807 application/problem+json responses. The machine-readable detail field carries a recovery hint you can show a user verbatim — see the Spec §12 and API Reference.