i18n and API endpoints

Mike's Notes

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

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
• https://pragprog.com/titles/maapis/design-and-build-great-web-apis/
• http://alps.io/spec/alps-to-html/
• 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

References

• Design and Build Great Web APIs by Mike Admunson (Pragmatic)
• Everything Curl (free book) 

Repository

• Home > Ajabbi Research > Library >
• Home > Handbook > 

Last Updated

18/05/2025

Article

By: Mike Peters

On a Sandy Beach: 20/04/2025

Mike is the inventor and architect of Pipi and the founder of Ajabbi.

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

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

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)