Skip to Content
PredictorSDK

Unknown query parameters are now rejected instead of ignored

BreakingFix

Every endpoint now returns 400 for a query parameter it does not read, instead of accepting the request and dropping the parameter.

The parameter this was really about is ?platform= on GET /v1/markets. That is the spelling GET /v1/matching-markets/sports uses for the same concept, so it is the natural guess — and it used to return the entire catalogue with a 200 on it. Measured against production before this shipped, ?platform=sxbet, ?providers=kalshi and ?nonsense=1 each returned the identical total of 1,935,451 and the same first row as an unfiltered page. A caller who tried any of them had no way to tell the filter had been discarded. A misspelled filter that silently returns everything is harder to diagnose than an error, and the fix for the provider filter shipped a 400 for an unrecognized value already, so a misspelled name was the only way left to be silently ignored.

The rejection is uniform. It applies to every route on the API, including GET /v1/health and the ones that read no parameters at all, because a guarantee that holds on some endpoints is not one a caller can build against. Provider webhook callbacks are the single exception — their caller is a third party that would retry rather than read the error, and no API consumer can reach them.

GET /v1/markets?platform=sxbet
400 {"error": "unknown query parameter",
     "message": "This endpoint does not read the query parameter \"platform\". It accepts: category, cursor, limit, provider.",
     "status_code": 400}

The response names the key it rejected and lists the ones that endpoint accepts, so the fix is visible in the error rather than requiring a trip to the reference. On /v1/markets the parameter you want is provider — see Filtering.

Who this affects. Only hand-built requests. The generated TypeScript, Python and Go clients expose exactly the parameters each endpoint declares and physically cannot send anything else, so no SDK call changes and the generated clients are byte-identical. If you build requests yourself, drop any parameter that is not listed under the endpoint in the reference. Like the router's 404 and 405, this answer comes from the router before the API key is read.