> For the complete documentation index, see [llms.txt](https://docs.mlsgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mlsgrid.com/recent-releases/northstar-mls-upcoming-addition-of-expandable-resource-and-standalone-resource.md).

# Northstar MLS: Upcoming Addition of Expandable Resource and Standalone Resource

Hello API Data Consumer,

We want to notify you that the MLS Grid will be making the following changes to the Northstar MLS data distributed via the MLS Grid API. These changes will only affect new or modified property records following the release. These changes will not apply to older property records you have already obtained. The details of the change can be found below.\
\
**MLS Affected:** Northstar MLS

**Date of Change:** December 8, 2025\
**Resources Affected:** PROPERTY\
**Type of Change:** NEW EXPANDABLE BodyOfWater RESOURCE, NEW UnitRooms RESOURCE\
\
**NEW EXPANDED RESOURCE - BodyOfWater**<br>

The following fields will be moved from the Property resource to create a new separate expanded resource on the property record. This will function the same way as expanded Media, Rooms, and UnitTypes function currently.

The new BodyOfWater resource will be accessible by adding\
“$expand=BodyOfWater” to your existing queries.

\
The fields moving the property record to the BodyOfWater resource are:\
\
LakeAcres\
LakeChainAcres\
LakeChainName\
LakeDepth\
WaterBodyKey\
WaterBodyName\
\
Any new or modified records from the MLS will immediately receive these changes on new or modified records as the information is added in the MLS System. Any older property records will continue to contain these fields on the property record.\
\
**DO NOT re-pull old records as these changes will not be available on old records.**\
\
\
\
**NEW STANDALONE RESOURCE - UnitRooms**

A new standalone resource will be added that will provide additional information about rooms in Multi-Unit properties. This standalone resource will be titled “UnitRooms” and will be accessible by modifying your queries to access this standalone resource.\
\
A query to the UnitRooms resource will look like the following:\
\
<https://api.mlsgrid.com/v2/UnitRooms?$filter=OriginatingSystemName> eq 'northstar'

When provided by the agent this new resource will provide the following information about Rooms contained in the Multi-Unit property.\
\
The field available in UnitRooms this resource are:\
\
ModificationTimestamp\
UnitKey\
RoomDimensions\
RoomKey\
RoomLevel\
RoomType\
\
Any new or modified records from the MLS will immediately create UnitRooms records in the UnitRooms resource when provided by the MLS.<br>

**DO NOT re-pull old records as these changes will not be available on old records.**

The expanded BodyOfWater resource and the new standalone UnitRooms resource will become available on **December 8, 2025** at approximately **10:30am Central Time**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mlsgrid.com/recent-releases/northstar-mls-upcoming-addition-of-expandable-resource-and-standalone-resource.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.