Inspect an API payload
Compare large numeric IDs, duplicate keys, and JSON inside strings with the original payload.
Follow the worked guide Open JSON FormatterInspect JSON, convert timestamps, and trace website problems.
Free to use, with examples you can reproduce.
Compare large numeric IDs, duplicate keys, and JSON inside strings with the original payload.
Follow the worked guide Open JSON FormatterFollow DNS, certificate, and redirect evidence through to the final response and its next repair step.
Follow the worked guide Open Website InspectorWork through invalid syntax, large numeric IDs, duplicate keys, and nested JSON strings without changing the data you meant to keep.
Read the guideFollow a worked HTTP-to-HTTPS chain, distinguish temporary and permanent redirects, and check paths, campaign parameters, and loops.
Read the guideCompare seconds and milliseconds for one instant, verify an explicit timezone offset, and reproduce the errors caused by a wrong unit or invalid calendar date.
Read the guideAn API response can remain valid JSON while an application changes its values during parsing and export. Start with the original text and a small input you can inspect. ADEMN’s JSON Formatter preserves number tokens and duplicate object keys so you can compare the supplied payload with the formatted result before passing it to another system.
{"orderId":9007199254740993}{"orderId":9007199254740993}In the recorded Node comparison, parsing this input as a JavaScript object and serializing it again produces 9007199254740992. The formatter retains the supplied digits. This makes the comparison useful when a large identifier appears to change between a response, a log, and an exported file. Compare the receiving application’s representation as a separate step.
A repeated key requires a similar check. The sample containing two status properties keeps both properties visible in ADEMN. A receiving parser may retain a single value. Use the recorded JSON comparison to reproduce those outcomes, then choose the representation required by your own application. Syntax validity, numeric fidelity, and field-level validation are separate questions.
A timestamp copied from a database or log needs a declared unit. The value 1704067200 in seconds and 1704067200000 in milliseconds identify the same instant, 2024-01-01T00:00:00.000Z. Load those examples in Unix Timestamp Converter, select the matching unit, and compare their ISO outputs before converting an unfamiliar field.
Explicit offsets make a date comparison portable between computers. The text 2024-01-01T08:00:00+08:00 identifies that same UTC instant. A local date without an offset depends on the browser’s timezone when Local is selected. Keep the original offset in a bug report so another person can reproduce the conversion using the same assumptions.
Clock changes add two useful edge cases. A spring transition can skip a local time, and an autumn transition can repeat it with two offsets. Our daylight-saving examples compare both situations with fixed inputs and expected results. For elapsed hours, compare timestamps in the same unit. For calendar-date counting, choose the dedicated date calculator and its boundary-counting convention.
Start a website investigation with the exact public URL showing the problem. Website Inspector follows the observable request through DNS, HTTPS, redirects, and the final response. An early failure can explain why later page checks have little evidence. Read the individual results and their suggested next steps when deciding which part of the deployment to investigate.
For a redirect problem, compare each Location value and the query parameters at that hop. The downloadable local fixture includes one route that drops campaign parameters and another that preserves them. Both routes reach a successful response, so the final status alone gives an incomplete description of the behavior. The step-by-step redirect case shows the exact inputs and both traces.
After a repair, submit the original URL again and check its final path, response status, and returned page information. Record any differences you expected to see. ADEMN observes the public response available to its checking server. Browser rendering, account-specific pages, and the target’s internal logs require their own observations when they affect the issue.
Each tool page includes instructions, sample inputs, expected results, and the assumptions needed to interpret its output. The guides connect those steps to a complete task. Their review dates describe content maintenance, while the downloadable test record identifies checked inputs, outputs, and the runtime used for the developer cases.
Text, image, and calculation tools process their inputs in the browser. Website diagnostics send the public target to ADEMN’s server for the requested check. The privacy policy describes that distinction and provides optional analytics controls. A correction report can include the affected page URL, a synthetic example, the selected settings, and the expected result.
The complete tool directory groups calculators, image tools, and text utilities by their task. Fulfillment quote comparisons have a dedicated Business tools for fulfillment section with billing-unit and cost-model guidance. These supporting utilities share ADEMN’s worked-example approach, while the main developer collection focuses on data and website checks.