References API
Experimental Feature
The References API is currently an experimental feature. Therefore, the API and this documentation is subject to change. If you have any questions, please email Engrain Support.
Overview
The References API provides mappings from third-party data providers, such as property management systems (PMS), to Engrain's stable asset and unit IDs. Engrain calls these mappings references. Each reference group links a distinct provider’s asset or unit ID to the corresponding Engrain ID.
For more detail on using the Unit Map® REST API, see the REST API documentation and OpenAPI spec.
Learn how to implement the References API with our helpful quick start guide, here.
Data Providers
For each data provider, we define what the reference values represent and how the values are retrieved.
PMS Vendors
Entrata
MRI
RealPage OneSite
ResMan
Yardi RentCafe
Yardi Voyager
CRM
Funnel
Custom Solutions
Greystar
Venterra Realty
Partner Solutions
AppWork
Data Sources and References Key:Value Mapping
Property Management System
*Multiple unit reference keys exist. Multiple keys create flexibility for reference data consumers to ensure there is a value that can be related to as many datasets as possible. Consumers can identify the key that contains the value that relates to their dataset accordingly.
Property Management System: Rentable Items
| Vendor | Key | Asset Reference | Unit Reference |
|---|---|---|---|
| Yardi Voyager | yardi-rentable-items-v1 | VoyagerPropertyCode | VoyagerPropertyCode:RentableItemCode |
| Entrata | entrata-rentable-items | PropertyId | Coming Soon |
| RealPage Onesite | realpage-onesite-rentable-items-v1 | PmcID:SiteID | SiteID:UnitID |
null Values
Engrain's interactive maps and datasets represent the physical space of each property which will result in units appearing in the references API with a null value as the units exist on the physical map, but not in the property management system at the time the map and dataset were created. This is expected behavior and the null value units will either obtain a provider reference id or be removed from the dataset.
CRM
| Data Feed | Key | Asset Reference | Unit Reference |
|---|---|---|---|
| Funnel | funnel | CommunityID | CommunityID-UnitID |
Custom Solutions
| Data Feed | Key | Asset Reference | Unit Reference |
|---|---|---|---|
| Greystar Master ID | greystar-master-id | master_id | |
| Greystar Yardi Code | greystar-yardi-code | Yardi Code | |
| Venterra | venterra-realty | id | unitID |
Partner Solutions
| Data Feed | Key | Asset Reference | Unit Reference |
|---|---|---|---|
| AppWork | appwork | InternalID |
Floor Plan and Unit Type Mapping
Overview
The Floor Plans and Units endpoints provide mappings from third-party data providers’ floor plan and unit type IDs to Engrain’s floor plan and unit IDs. Unlike asset and unit references, floor plan and unit type mappings are not part of the References API and will be returned from the applicable resource.
| Data Feed | Engrain Resource | Data Feed Datapoint | Engrain Datapoint |
|---|---|---|---|
| Yardi RentCafe | Floor Plans | floorPlanID | provider_id |
| Yardi RentCafe | Units | voyagerUnitTypeName | provider_group_id |
| RealPage OneSite | Floor Plans | FloorPlanID | provider_id |
| RealPage OneSite | Units | FloorPlanCode | provider_group_id |
| Entrata | Floor Plans | IDValue | provider_id |
| Entrata | Units | UnitTypeName | provider_group_id |
Updated 5 days ago

