i18n and API endpoints

Mikes Notes

Ajabbi takes an API-first approach. SaaS applications and their APIs are versioned the same, and i18n applies to each API.

Given that each build is human language specific, it makes sense to go with:

• GET api.example.com/api/countries/1/en-uk/

Resources

• https://en.wikipedia.org/wiki/Interface_description_language
• https://en.wikipedia.org/wiki/OpenAPI_Specification
• http://openapis.org/
• https://github.com/api-platform/core/issues/127
• Design and Build Great Web APIs by Mike Admunson (Pragmatic)
• https://pragprog.com/titles/maapis/design-and-build-great-web-apis/
• http://alps.io/spec/alps-to-html/
• Everything Curl (free book) https://curl.haxx.se/book.html
• https://github.com/api-platform/api-platform
• http://alps.io/spec/index.html
• https://datatracker.ietf.org/doc/html/draft-amundsen-richardson-foster-alps-07

Options

• GET api.example.com/api/countries/1/en-uk/
• GET http://api.example.com/countries/1?locale=fr-FR
• GET http://api.example.com/countries/1/locales (to find locales available)