30 chars · 1 line
48 chars · 3 lines
1 parameter1 unique keys
30 chars · 1 line
48 chars · 3 lines
Nested query value error
There is no universal standard for mapping nested JSON objects into flat query strings. VetaTool rejects nested objects so it does not silently choose bracket, dot, deepObject, or JSON-in-string semantics for you. This tool is free to use. No account or payment is required.
Last updated
One API may expect filter.status=active, another filter[status]=active, another a JSON string, and another repeated keys. Automatically choosing one can create a syntactically valid but semantically wrong URL.
The generic builder therefore accepts only strings, numbers, booleans, null, and arrays of those primitives.
The nested object is ambiguous; the corrected example uses one explicit primitive value.
{"filter":{"status":"active"}}{"filter":"active"}Common questions
No. The builder avoids assuming one framework-specific nested-query convention.
Yes, if you explicitly stringify it first and pass that JSON text as a string value.
Yes. Arrays of primitive values become repeated parameters.
Debugging a specific Query String issue? Browse Query String troubleshooting.