LV2 · Toolooo Standard
API Chaos Payload Builder
Generate bounded JSON edge-case packs with typed mutations, nested paths and local copy/export.
Load a sample or paste JSON, select categories and generate a pack. Payloads stay in memory until reset or the page closes; copy and export are explicit local actions.
What this tool does and why
Before you start
What
Generate bounded JSON edge-case packs with typed mutations, nested paths and local copy/export.
Why
Missing, null, coercible and unexpected values expose different validation assumptions; isolated mutations make those assumptions easier to test against the real API contract.
Your Result and Action update in the tool as you change its inputs.
Model note
This browser-side model explains the inputs you choose. Check an important decision against the real system, brief, or production constraints.
Next
How this tool stays honest
How it works
Start from a JSON object or array and create independent cases for missing fields, nulls, number ranges, text encoding, boolean coercion, array cardinality and object shape. Inspect each path and purpose, copy a payload or export a local test pack without assuming API status codes.
Assumptions
The tool runs in your browser and models the information you provide. It does not know facts outside that model.
Limitations
Generated JSON is syntactically valid and the API contract is unknown. Cases probe types, cardinality and encoding without predicting HTTP status or proving rejection. Input, nesting, case count and output size are capped; generation is not exhaustive.
Understand API Chaos Payload Builder
What this tool helps you understand
Start from a JSON object or array and create independent cases for missing fields, nulls, number ranges, text encoding, boolean coercion, array cardinality and object shape. Inspect each path and purpose, copy a payload or export a local test pack without assuming API status codes.
When to use it
When designing negative cases for a JSON API contract.
Try a scenario
Start with a field that is required by your actual contract, then compare missing, null and wrong-type mutations against the real validator.
How to read the result
Inspect each case path, mutation and concern, then compare observed behavior against your own API contract in a test environment. No HTTP result is predicted.
Assumptions and limits
Generated JSON is syntactically valid and the API contract is unknown. Cases probe types, cardinality and encoding without predicting HTTP status or proving rejection. Input, nesting, case count and output size are capped; generation is not exhaustive.
Toolooo is part of Khizooology, created byKhizar Imtiaz (khizooo).