API JSON Envelope to Lookup Map

Select an object-record array inside a saved API response and build a complete lookup object by an exact string field.

Input/output processing stays local. Original and checkpoint downloads can retain omitted/replaced values. No all-secrets-removed, anonymization, heap-erasure or security certification.

This flow needs JavaScript. If it does not load, refresh the page and try again.

About this flow

Select an object-record array inside a saved API response and build a complete lookup object by an exact string field. Existing JSON formatting workflows do not select inside API envelopes or create a keyed complete-record lookup. The earlier JSON review pilot assumes a flat root export and ends in TSV; this ends in a strict JSON map and rejects key collisions rather than losing records.

Limitations

Each downstream CSV/JSON input remains limited to 5 MiB; a larger completed intermediate stays a checkpoint and final success is refused. Originals/checkpoints retain omitted or replaced values. Strict JSON:200,000 values/40 levels/10,000-unit number tokens; pointer at most4096units/40segments. At most50,000 object records, exact own field up to1000units and string keys up to10,000units. Missing/nonstring/duplicate keys fail without overwriting. Empty/prototype-like keys remain data. Numeric spellings remain exact. No API request, schema inference, merge or database import.
No native other-browser/physical-device/heap-erasure acceptance is established.