Changelog

Migration Guide

Use /latest (recommended)

Use api.sylvain.sh/latest to always point to the latest version:

https://api.sylvain.sh/latest/infos
https://api.sylvain.sh/latest/evaluate

Nested paths and query strings are preserved through the redirect:

https://api.sylvain.sh/latest/chat/private?session=abc
# redirects to /v6/chat/private?session=abc

The redirect works for any HTTP method (GET, POST, PATCH, DELETE...) via a 307 Temporary Redirect, which preserves the original method and body — so POST /latest/token redirects to POST /v6/token with its body intact.

Tip

Most HTTP clients don't follow redirects by default. With curl, add the -L (--location) flag, or you'll get the 307 response without ever reaching /v6.

Manual Migration

Replace all occurrences of /v5/ with /v6/ in your API requests:

# Before
https://api.sylvain.sh/v5/infos

# After
https://api.sylvain.sh/v6/infos

Endpoint Compatibility

v6 is not a drop-in replacement for v5. Four endpoints changed method or path, the captcha changed its default mode, and the status field of error responses changed type. Read the 6.0.0 changelog before migrating.

What changed	v5	v6
Clear a private chat	DELETE /chat/:token	POST /chat/clear
Play a move	PATCH /tic-tac-toe/:game	POST /tic-tac-toe/play
Forfeit a game	DELETE /tic-tac-toe/:game	POST /tic-tac-toe/forfeit
Compare two strings	GET /levenshtein	POST /levenshtein
Captcha default mode	image	challenge
status in error responses	string ("400")	number (400)

/hyperplanning is deprecated and no longer listed in v6; it still answers, and disappears in 7.0.0.

Previous Versions

• v5 Changelog - View all v5 releases
• v4 Documentation - Legacy version