# Malformed query strings and overlong keys answer 400 and 401 (https://docs.predictorsdk.com/changelog/2026-10-09-request-mistakes)

2026-10-09 · Fix

A query string separated by semicolons or carrying a stray percent sign is now a 400 naming the pair at fault, an API key longer than 256 characters is a 401, and an empty player_prop_match means its default.

Three request mistakes now get the answer that says what went wrong. A query string separated with `;` (`?limit=5;provider=kalshi`) or carrying a `%` that is not followed by two hex digits used to be read as something else: the `;` pair was dropped, so a filter was silently ignored and the response looked filtered when it was not. Every route except the two webhooks now answers `400` with code `invalid_parameter`, quoting the pair at fault. An API key longer than 256 characters answered `502`, which reads as an outage and invites a retry; it is now `401` with code `invalid_api_key`, like any other key that is not valid. And `player_prop_match=` sent empty on [`GET /v1/matching-markets/sports`](https://docs.predictorsdk.com/api-reference/getSportsMatchingMarkets) now means its default, as an empty `limit` or `cursor` already did. See [error handling](https://docs.predictorsdk.com/guides/error-handling).