Step 1: Format the API response
Suppose your endpoint returns: {"code":0,"data":{"userId":1001,"token":"eyJ..."}}. Paste the entire string into WoDeTool's JSON Formatter to expand the tree instantly with syntax highlighting.
If parsing fails, the error points to a line number — often a trailing comma or an HTML error page disguised as JSON. Confirm Content-Type is application/json before blaming application logic.
Step 2: Decode JWT and verify exp
Copy the token (without the Bearer prefix) into JWT Decoder to inspect payload fields like exp, iss, and custom claims.
Example: "exp": 1718123456. Use the Timestamp Converter in seconds mode to get a human-readable expiry. If the token is expired, a 401 response is expected — no guesswork required.
Step 3: Diff API contract changes
Before release, paste old and new JSON responses into JSON Diff. Added keys, removed fields, and type changes (e.g. userId number → string) are highlighted — lightweight contract review for mobile and web clients sharing one API.
WoDeTool extras: pipelines and extension
Save a pipeline: JSON Formatter → JWT Decoder → Timestamp Converter for repeat debugging. The Chrome extension opens the right tool from selected text with ?input= prefilled.
Standard dev utilities run locally in your browser — suitable for staging responses (avoid pasting production secrets).