LOCKBOX SYSTEM IMPORT SPECIFICATION
Real Estate Standards Organization (RESO) provides the foundation for streamlined real estate technology through the creation and certification of standards. It serves more than one million real estate professionals. It promotes to create same experiences: Interoperability between MLS, broker, agent, and consumer technology tools in this case for Sentrilock.
What type of RESO access are we requesting and what we will do with it
SentriLock is requesting MLS Partner Vendor access to RESO listing and membership data.
- Replication of membership data for the purpose of authenticating, credentialing, and authorizing access to electronic lockboxes.
- Replication of listing data to secure and facilitate showings and provide visibility and traceability to secured listings.
Import Method
SentriLock can offer options for import methods with a third-party vendor, but they must meet our minimum required performance expectations for use with our SentriLock product(s). It is also required that the customer understands what those performance expectations are and acknowledge this as part of their on-boarding process with their SentriLock Project Manager.
The SentriLock standard for imports is the use of the RESO Web API for all membership and listing information. These are the industry standards intended to ensure the highest level of accuracy when sharing disparate data sources amongst vendors in the real estate industry.
Note that whether we receive all the data from one or multiple systems, the ability to tie the data together is the main requirement. For instance, if you want to send us office/agent data from your Membership system and listings from your MLS system, then there must be a field in both systems that can tie listing to the agent.
To ensure the accuracy and integrity of your data SentriLock may occasionally request a full dataset to conduct software testing. You are responsible for providing this data and for any costs associated with obtaining data from your data vendors.
A Board Identifier is required if more than one Board is included in the datafeed. (Standard)
For a single Board feed, we can move forward without a Board Identifier, but it is not recommended. However, if a change is made to add this Board with another, that request will be denied until a Board Identifier has been established.
How to Contact the SentriLock Data Team
During the conversion process, you may be in contact with several members of the SentriLock Data team. When you send e-mail or reply to an e-mail message from the SentriLock Data Team, please direct your e-mail to integrations@sentrilock.com to ensure all members of the Data team will see your message. This helps to ensure a smooth conversion.
COMPANY/ OFFICE
For each office (or company) in your Association please specify the following information:
RESO FIELDS | SENTRILOCK FIELD NAME | ||
OFFICEMLSID | Unique ID | ||
OFFICENAME | OFFICE Name | ||
OFFICEPHONE | OFFICE PHONE Number | ||
- | Area code (3-digit number) | ||
- | Subscriber number (7-digit number) | ||
OFFICEADDRESS1, OFFICEADDRESS2 | Street Address | ||
OFFICECITY | City | ||
OFFICESTATEORPROVINCE | State/Province | ||
OFFICEPOSTALCODE | Zip/Postal Code | ||
- | Country (if other than US) | ||
OFFICESTATUS | Status |
Company / Office – Sentrilock Specific Definition
- Area code and Subscriber numbers are put together to form the phone number
- Status (Company should be active or terminated)
USER (RESO calls it "Member")
For each person in your Association who will have access to the system please specify the following:
RESO FIELDS | FIELD NAME | ||
MEMBERMLSID | Unique ID | ||
MEMBERNATIONALASSOCIATIONID | NRDS / NAF Number | ||
MEMBERSTATELICENCE | Real Estate License Number | ||
MEMBERTYPE | Type | ||
MEMBERFIRSTNAME | First Name | ||
MEMBERLASTNAME | Last Name | ||
MEMBEROFFICEPHONE | Office Phone Number | ||
MEMBERMOBILEPHONE | Cell Number | ||
MEMBEREMAIL | Email Address | ||
OFFICEMLSID | Office unique ID | ||
SKSS Status | |||
Lockbox Service Status | |||
MEMBERSTATUSFIELD | Account Status
|
User – Sentrilock Specific Definition
- Account Fields
- Lockbox Service Status - Controls access to the lockbox website
- SKSS Status - Controls access to showing service
- Account Status - Controls the account status (active/inactive)
- Member – user type, permission level someone should have within the system
IMPORTANT INFORMATION: SentriLock requires a unique User Name for each user. If the User Name you provide us with is not unique within our system, we will append a value to it. For example, if you provide us with the User Name “MSmith” and our system already has an “MSmith” User Name, we will add your region code to the User Name. In this case, the User Name “MSmith” becomes “MSmith-999”. This does not apply when using an email address. Email addresses must be unique in all circumstances for individual accounts.
User Types (Reso does not have this) Will need to be removed.
The Type field indicates which kind of access this person should receive. Possible types are:
Administrator: Administrators have access to all data in the Association. They can also authorize new Agents for a SentriKey® account.
Broker: A Broker has access to all agents and listings within the office they are associated with. They can have listings, own lockboxes, and be issued a SentriKey® account.
Office Staff: Office staff have access to all Agents and listings within the office they are associated with.
Agent: An Agent can see their own data. They can have listings, own lockboxes, and be issued a SentriKey® account.
Affiliate: An Affiliate can be issued a limited access SentriKey® account which does not allow them to own lockboxes.
Assistant: An Assistant can see their team’s data. They can be issued a limited access SentriKey® account which only allows them operation of their team member’s lockboxes.
If your User file contains types other than these, please provide us with a text file or e-mail that explains how each type should be processed. If you have data types 1, 2, 3, and 4, you need to tell us which of these types is an Administrator and which is a Broker. For example, your e-mail or text file could include something like:
- 1=Administrator
- 2=Broker
- 3=Office Staff
- 4=Agent
RESO FIELDS | USER PEM LEVEL | ||
Administrator | |||
Broker | |||
office staff | |||
agent | |||
affiliate | |||
assistant |
LISTING (Reso calls it Property)
For each listing in your Association please specify the following:
RESO FIELDS | FIELD NAME | ||
LISTINGID | MLS number | ||
LISTAGENTMLSID
CoListAgentMlsId |
user id (needs to match unique id from user file)
Co-Listing Agent |
||
STREETDIRPREFIX STREETNUMBER STREETNAME STREETSUFFIX UNITNUMBER |
Street Address
Street Direction Street Number Street Name Street Suffix Street unit number |
||
Street address line 2 | |||
CITY | city | ||
STATEORPROVINCE | state/province | ||
POSTALCODE | zip/postal code | ||
COUNTRY | country (if other than us) | ||
COUNTYORPAISH | county | ||
TOWNSHIP | Township | ||
SUBDIVISION | Neighborhood | ||
LISTPRICE
MLSSTATUS |
list price
Listing Status |
||
CLOSEPRICE | sale price | ||
BEDROOMSTOTAL | bedrooms | ||
BATHROOMSFULL | full bath | ||
BATHROOMSHALF | half bath | ||
LIVINGAREA | square footage | ||
HIGHSCHOOLDISTRICT | school district | ||
SHOWINGINSTRUCTIONS | showing instructions | ||
MODIFICATIONTIMESTAMP
ONMARKETDATE
OFFMARKETDATE
PRICECHANGETIMESTAMP YEARBUILT |
last modified date
On Market Date (For coming soon listings) Off market date (no longer showing) Price Change timestamp year built |
||
LONGITUDE | longitude | ||
LATITUDE
DAYSONMARKET CUMULATIVEDAYSONMARKET |
latitude
Days on market Cumulative Days on Market |
||
LISTINGKEYNUMERIC | UNIQUE ID THAT IDENTIFIES PHOTO | ||
PHOTOCOUNT | PHOTO FIELD COUNT | ||
PHOTOSCHANGETIMESTAMP | PHOTO LAST MODIFIED TIMESTAMP FIELD | ||
Photo pull method (get object search) |
Listing – Sentrilock Specific Definition
User Photos
We provide a means for uploading an individual’s photo to their profile. If you wish to provide us user photos, then they must be named using the Unique ID from the User data. For instance, if a user’s Unique ID is ’1234′, then their photo must be named’1234.jpg’ or’1234.gif’ etc. In addition, we HIGHLY recommend that user photos adhere to the following criteria:
- Medium size anywhere from 200KB to 500KB, ideal hi-res, 150 pixels resolution or higher
- Portrait format with a width-to-height ratio of .75 (in pixels should be 75/100 or correspondent multiple of each, e.g., 150/200, 300/400, etc.)
- HEADSHOT ONLY, no body shots. Also, no team photos, group shots, family members, pets, etc. are allowed
- Users also can upload their own photo