Skip to main content
WidgetExamples Logo
Tools / API Inspector

API Response Inspector

Path-based comparison for Flutter API payloads. Distinguishes missing from null, preserves large numeric lexemes, and inspects structural contract changes.

Response A — Baseline100 KiB limit
0%
Waiting for input…1 lines · 0 chars
Response B — Incoming100 KiB limit
0%
Waiting for input…1 lines · 0 chars
🔒 Local Sandbox (0 network requests)
User Guide: Comparing Stable vs Changed Responses in Flutter
Read Full Tutorial & Dart Code →
Limit 1: Observed Difference ≠ Server Contract Proof

An absent key in an observed response is an observed difference in that specific sample. It does not prove the field is optional or nullable in the backend contract. Always verify schema rules against your backend OpenAPI/Swagger specification.

Limit 2: Index-Based Array Alignment

JSON arrays are strictly ordered sequences. Unless arrays provide unique identity keys, array differences are inspected by index order. Reordering array items appears as index-level replacements rather than silent key matching.

Limit 3: 64-bit Lexical Numeric Precision

Standard JavaScript JSON.parse coerces numbers to 64-bit float doubles, losing precision for values > 253-1 (e.g. Snowflake IDs like 9007199254740993). API Inspector preserves numbers as exact lexical strings.

Limit 4: Local Sandbox Privacy Guarantee

0 network requests are made. All parsing, diffing, draft autosaving, and snapshot storage remain 100% inside your local browser. By default, raw payload values are excluded from exported reports to prevent leaking tokens or PII.