How do you version public web APIs?
Summary
The article discusses whether public web API versioning should be tied to URL paths (e.g., /api/v1) or kept separate from the contract versioning. It argues that coupling URL versioning with semantic versioning is an antipattern and highlights the confusion and maintenance challenges when the URL and API contract diverge. It invites readers to share API design preferences and pet peeves.