Localization is part of Content-Negotiation in Restful API.
So my preferred way I would do it through headers. HTTP offers standard way of defining wanted language. Have a look at Accept-Language header.
More Related Contents:
- How to get Url Hash (#) from server side
- URL encoding the space character: + or %20?
- REST API Best practices: Where to put parameters? [closed]
- Does a `+` in a URL scheme/host/path represent a space?
- Is there a way to change the browser’s address bar without refreshing the page?
- When should I use a trailing slash in my URL?
- URL matrix parameters vs. query parameters
- slashes in url variables
- Should URL be case sensitive?
- What are the safe characters for making URLs?
- What does a dot mean in a URL path?
- Passing parameter via url to sql server reporting service
- url with multiple forward slashes, does it break anything?
- What’s the best way to get the current URL in Spring MVC?
- Is a colon `:` safe for friendly-URL use?
- Encoding of XHTML and & (ampersand)
- delete version number in url
- Encode / decode URLs
- COMPLETE list of HTML tag attributes which have a URL value?
- What is %2C in a URL?
- Browser support for URLs beginning with double slash
- Add parameters to the URL (redirect) via a Greasemonkey/Tampermonkey/Userscript
- Weird characters in URL
- How do I choose the URL for my Spring Boot webapp?
- IIS URL Rewrite not working with query string
- Tomcat session management – url rewrite and switching from http to https
- Call a Server-side Method on a Resource in a RESTful Way
- Place API key in Headers or URL
- URLs: Dash vs. Underscore [closed]
- IIS7 URL Redirection from root to sub directory [closed]