> For the complete documentation index, see [llms.txt](https://docs.multiset.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multiset.ai/fundamentals/rest-api-docs/map-details.md).

# Map details

Fetch a single map by map code, or list every VPS map on the account, with status, location and spatial metadata.

This API endpoint retrieves comprehensive details of a VPS map by providing its unique map code in the URL path along with a bearer token for authentication, returning complete information including the map's status, geographic location, spatial metrics (floor areas, elevations, capture points), storage usage, etc.

{% hint style="info" %}
**`hasPano`** tells you whether the map has a 360° virtual tour. When it is `true`, you can load the tour with the [360° Virtual Tour (Pano)](/fundamentals/rest-api-docs/pano-360-virtual-tour.md) APIs. If the map belongs to a Map Version, the response also carries `versionCode` and `activeMapCode`. See [Map Versioning](/fundamentals/map-versioning.md) for how to apply them at runtime.
{% endhint %}

{% openapi src="/files/crAGFko3hVqHLa65gdiY" path="/vps/map/{mapCode}" method="get" %}
[get-map.yaml](https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-f171b3389d2ef800eedcdd8ad221975d2ae776e6%2Fget-map.yaml?alt=media)
{% endopenapi %}

### GET All VPS maps for an account

{% hint style="warning" %}
`limit` and `page` are both required on this endpoint. A request without them, such as `GET /vps/map`, returns `500` with `{"error": "Something went wrong!"}`. Use `GET /vps/map?limit=10&page=1` to fetch the first page.
{% endhint %}

{% openapi src="/files/WjX5DJ8IiGWIu7l50anH" path="/vps/map" method="get" %}
[openapi-maplist.yaml](https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fgit-blob-6e904ae42be69edb7ec5074c9a00d1fb822c5637%2Fopenapi-maplist.yaml?alt=media)
{% endopenapi %}

{% openapi src="/files/REo9Pu8Yu4xpabhcwiue" path="/vps/map-set" method="get" %}
[mapset-api-openapi.yaml](https://3163433004-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FokTDI7QVY04Zvb1pQ8Ry%2Fuploads%2Fh5JvlrsX78bpolBaI0ec%2Fmapset-api-openapi.yaml?alt=media\&token=25af37b3-58e0-4ef8-b053-5d362183c412)
{% endopenapi %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.multiset.ai/fundamentals/rest-api-docs/map-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.