JsonMind

JsonMind Guides

Practical developer guides

Short, evidence-based guides for the errors and decisions developers hit every week. Every guide links to a browser tool, cites the relevant specification, and states its limits.

25 in-depth guides6 topics54 linked toolsBrowse all tools

JSON & Data

5

Encoding & Text

5

Security & Authentication

3

API & Contracts

6
API & Contracts15 min read

HTTP 429 Too Many Requests: Retry-After, Backoff, and Retry Storms

Understand what 429 Too Many Requests means, parse Retry-After seconds and HTTP-dates, design jittered exponential backoff with a cap, and avoid retry storms.

Updated Nov 11, 2026Read guide
API & Contracts14 min read

Idempotency Keys for APIs: Safe Retries for Payments and State Changes

Design idempotent APIs that survive retries: key generation, header placement, storage schema, request fingerprints, replay, TTL, and payment failure semantics.

Updated Nov 11, 2026Read guide
API & Contracts10 min read

JSON Schema Validation: Common Errors and How to Fix Them

Diagnose JSON Schema validation failures, understand required, type, additionalProperties and format errors, and validate payloads before they reach production.

Updated Nov 10, 2026Read guide
API & Contracts9 min read

Convert cURL to fetch or Axios Without Breaking the Request

Map cURL flags to fetch and Axios options, avoid quoting and content-type mistakes, and verify the converted request against the original.

Updated Nov 9, 2026Read guide
API & Contracts10 min read

Fix CORS Preflight Errors: Missing Access-Control-Allow-Origin

Diagnose CORS preflight failures with the browser, curl, and server logs. Learn which headers are required and why credentials break wildcard origins.

Updated Nov 9, 2026Read guide
API & Contracts14 min read

HTTP Status Codes for APIs: 4xx vs 5xx and What to Fix First

A practical debugging guide to HTTP status codes, including 400 vs 422, 401 vs 403, 404 vs 410, 429 retries, and 502 vs 504 gateway failures.

Updated Nov 9, 2026Read guide

Images & Media

3

Documents & Conversion

3

Reviewed against primary specifications and linked sources.

JsonMind guides are written and reviewed by the engineering team. We check each guide against the relevant RFC or vendor documentation, link the primary sources, and update the guide when behavior changes.

Primary sources are linked at the end of each guide.