Sudoku API changelog
Changes to the API contract, puzzle engine and developer tooling. The REST API remains at /api/v1.
On this page
1.2.0 · 6 October 2026
- Raised the account allowance from 60 to 6,000 API/MCP requests per minute. PDF downloads have a separate 6,000-request allowance with either grant or Bearer authentication. Added X-RateLimit-Scope. Daily JavaScript/iframe widgets do not consume these allowances.
- MCP tools declare structured output schemas and accurate read-only and idempotency annotations. Publishing and exports create hosted records; export calls create fresh grants.
- Hints accept optional
strategy: logicalto explain locked-candidate and naked-pair eliminations before a placement. Existing calls default to singles. Responses add adeductionsarray. - Operation responses include request IDs and account quota headers when the quota is evaluated.
- A versioned, downloadable developer kit includes an MCP adapter, typed JavaScript client, Python client and persistent backend example.
- API terms explicitly permit attributed commercial outputs and clarify precedence over general website terms.
- Added private personal and team puzzle libraries with revision-safe updates, in-app team invitations and scoped API keys.
- Generation accepts seed and generatorVersion: seed-v1. Custom PDFs support a title and one, two or four puzzles per page while retaining site branding.
- Added production guidance, component status checks and this changelog.
1.1.0 · 6 October 2026
- Fresh verified generation replaces a small transformed puzzle bank. Batches exclude Sudoku-symmetry equivalents; global cross-request uniqueness is not promised.
- Requested difficulty matches the measured technique ladder. Expert means the supported ladder stalls, not that a specific advanced technique is required.
- Normalized duplicates and completed grids are rejected for playable publications. Invalid grids report conflicting cells.
- Public puzzle pages omit full solutions. Collections use short persistent URLs; PDF download grants expire after 24 hours.
These changes tightened validation and difficulty behavior. Clients should handle documented error codes and treat puzzles as generated content rather than reproducible fixtures.