# Cities

Cities in the Musement API can refer to different types of *destinations*. This includes islands, natural landmarks, beaches, actual cities and more.

An activity's city appears in both the `/activities` and `/activities/{activityUuid}` endpoints. In the example response below, the activity takes place in Paris:


```json
{
	[...]
	"city": {
		"id": 40,
		"name": "Paris",
		"country": {
			"id": 60,
			"name": "France",
			"iso_code": "FR"
		},
		[...]
		"time_zone": "Europe/Paris"
	},
	[...]
}
```

For more information about cities in the catalog, check out the [dedicated section](/api/catalog/cities).

## Activities with multiple cities

Every activity is connected to at least one *default* city. An activity may be connected to multiple cities. This is a common situation when an attraction is located near multiple destinations or transportation is involved.

Activities connected to multiple cities will appear in results when [filtering by any of the cities](/api/catalog/activities/searching#cities). However, only the *default* city will appear in the activity's `city` property. To see all the cities for a single activity, make the following request:


```bash
curl -X GET '{baseUrl}/activities/{activityUuid}/destinations' \
-H 'X-Musement-Application: {applicationValue}' \
-H 'X-Musement-Version: 3.4.0' \
-H 'Authorization: Bearer {accessToken}'
```

The response will contain an array of cities. In the example response below, the activity is connected to both Paris (the default) and Versailles:


```json
[
	{
		"id": 40,
		"name": "Paris",
		[...]
		"country": {
			"id": 60,
			"name": "France",
			"iso_code": "FR"
		},
		"time_zone": "Europe/Paris",
		"default": true
	},
	{
		"id": 41,
		"name": "Versailles",
		[...]
		"country": {
			"id": 60,
			"name": "France",
			"iso_code": "FR"
		},
		"time_zone": "Europe/Paris",
		"default": false
	}
]
```