Use the HTTP header Accept-Language to specify the language and the region .


Here a list of supported locales:

  • en-US
  • en-GB
  • es-ES
  • de-DE
  • fr-FR
  • ru-RU
  • it-IT

The language part impacts the language in which the content is returned.
If the content is not available in the requested language, the default one for the activity is returned (usually English).

The region part impacts the country in which activities are returned.
An activity has a region visibility, so depending on the region in the locale it may or may be returned.
The region impacts the visibility of the activity but also the visibility of the taxonomies related to the activity.

For example, if a city has only activities visible to the region FR it will not be returned in the response of a request bearing the region ES.


Let's take for example the French city of Nanterre.

When you ask for the activities for Nanterre using Accept-Language: fr-FR header, the system will return 10 activities and the content in French.

curl -X GET \
  '{{api_base_url}}/cities/731/activities' \
  -H 'Accept-Language: fr-FR'

If you send the very same request using the Accept-Language: es-ES you will get an empty response. This happens because the activities for Nanterre are only active for the region FR

This also affects the endpoint returning all cities for a given country (in this case France).
The endpoint response returns only cities with at least one activity for the given locale/region.

Thus, this request will return Nanterre as one of the elements.

curl -X GET \
  -H 'Accept-Language: fr-FR'

While the very same request with Accept-Language: es-ES will not return it.


Data of the example above

Please note that Musement's catalog changes very often, so the response you'll experience might have different results from the ones above.