Getting Floor Plans, Unit & Expense Data

Joining and synchronizing Property Units and Expense Tables

Overview:

  • Base URL: https://api.sightmap.com/v1
  • Auth: Pass your API key in the header as “API-Key: [your_key]”
  • All endpoints below are scoped to a single asset. Replace {asset_id} with the Engrain asset ID.

Data Model:

  • An asset has floor plans and units. Every unit belongs to exactly one floor plan via its floor_plan_id field.
  • Expenses exist at three levels: asset, floor-plan, unit.
  • Floor plan and unit expenses are split into two pieces — the fee metadata, and fee entries (the actual dollar values keyed to each floor plan or unit).

To provide a transparent experience for end-users, you need more than just a list of room numbers; you need a comprehensive view of a property’s availability and the total cost of residency. This section guides you through the process of fetching core asset structures and layering in complex fee data to build a complete "Unit Profile."


What’s Inside:

  • Building the Foundation: Units & Floor Plans - Before you can assign a price, you need a place. We start by showing you how to pull the "containers" of an asset—Units and Floor Plans—and how to identify the critical join keys that link them together.

  • The Expense Hierarchy: Property, Floor Plan, & Unit Fees - Expenses in our ecosystem are highly granular. You will learn how to navigate the three levels of financial data: Asset-level fees (standard property-wide costs), Floor Plan-level entries (fees specific to a layout), and Unit-level expenses (unique costs assigned to a specific front door).

  • Data Orchestration: Putting it All Together - The real magic happens during the join. We provide a step-by-step logic guide on how to stitch data from over eight API calls into a single, unified object. This ensures that when a user looks at a specific unit, they see every relevant cost—from the application fee down to the specific pet deposit for that unit.
📘

Pro Tip: If you are integrating with a third-party PMS (Property Management System), pay close attention to the Unit Reference Groups section to ensure your internal IDs match ours perfectly.


💡

Explore Our New Expense Data Integration

We’ve launched three new example properties in the SightMap REST API featuring realistic expense data models. Use these assets to test and visualize expenses across the asset, floor plan, and unit levels.

  • Demo Asset IDs: 7778 • 7779 • 7780

Ready to get started?

  • Request a Technical Demo Discover how our advanced APIs deliver granular expense data across every asset level. Contact Partnerships
  • Become an Engrain Partner Not currently integrated? Let’s get you up and running with our expense-enabled APIs. Start Your Integration
  • Existing Partner Support Need access to these assets or help with permissions? Contact API Support

What’s Next

Pulling Unit & Floor Plan Data