> For the complete documentation index, see [llms.txt](https://docs.mapsindoors.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mapsindoors.com/sdks-and-frameworks/web/other-guides/working-with-events.md).
# Working with Events
### Overview
Let's take a look at the events that MapsIndoors offers and how to utilize them.
> Events are actions or occurrences that happen in the system you are programming, which the system tells you about so you can respond to them in some way if desired. -- [*MDN web docs*](https://developer.mozilla.org/en-US/docs/Learn/JavaScript/Building_blocks/Events)
For example, if the user clicks on a Location on the map, then you can react to that action by presenting the user with additional info about the Location.
A code example is shown in the JSFiddle below, but will be run through bit by bit in this guide.
#### Ready Event
The `ready` event will be fired when MapsIndoors is done initializing and is ready to interact.
```javascript
mapsIndoors.addListener('ready', (e) => {
log(`MapsIndoors: Ready`);
});
```
#### Building Changed Event
The `building_changed` event will be fired when the map is moved around and a new Building comes in focus.
This is also related to the Floor Selector which will update its view to show the Floors of the current Building.
The event handler is called with a [building](https://app.mapsindoors.com/mapsindoors/js/sdk/latest/docs/global.html#Building) object representing the building in focus.
```javascript
mapsIndoors.addListener('building_changed', (e) => {
log(`Building changed: ${e.buildingInfo.name}`);
});
```
#### Floor Changed Event
The `floor_changed` event will be fired when the Floor is changed; either by clicking the Floor Selector or by calling `setFloor()` on the MapsIndoors instance.
The event handler is called with the Floor Index of the current Floor.
```javascript
mapsIndoors.addListener('floor_changed', (e) => {
log(`Floor changed: ${e}`);
});
```
#### Click Event
The `click` event will fire when the user clicks on a Location on the map.
The event handler is called with a [location](https://app.mapsindoors.com/mapsindoors/js/sdk/latest/docs/global.html#Location) object representing the Location clicked.
```javascript
mapsIndoors.addListener('click', (location) => {
log(`Clicked: ${location.properties.name}`);
});
```
---
# 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.mapsindoors.com/sdks-and-frameworks/web/other-guides/working-with-events.md?ask=&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.