NTREIS RETS Server Functionality List 

 

 

 

 

Following is a list of the options from the Real Estate Transaction Specification, Version 1.5 of December 1, 2003.  The numbers reference the corresponding section in the specification.

General

·         Request and Response Message formats satisfy specification requirements

·         Data compression is not implemented

3.0 Message Format

3.5 Optional Client Request Header Fields

·         Authorization – Supported and required for authentication

·         Cookie – Supported and required for authentication

·         RETS-Request-ID –  Supported and required for authentication

·         Accept-Encoding – Unused and not supported

3.8 Optional Server Response Header Fields

·         Content-Length – Supported by server according to HTTP RFCs

·         Transfer-Encoding – Supported by server according to HTTP RFCs

·         Content-Encoding – Supported by server according to HTTP RFCs

Note: “Supported by server according to HTTP RFCs” is the RETS Vendor’s wording.  NTREIS has reason to believe ‘Content-Length’, ‘Transfer-Encoding’, and ‘Content-Encoding’ are not supported on the NTREIS RETS 1.5 server

·         RETS-Request-ID – Supported and required for authentication

4.0 Login Transaction

·         Digest Authentication is the only supported authentication mechanism

·         All communication is over port TCP 80 and does not use any other port declarations in the specification

·         HTTPS for the transport is not supported

·         SavedMetadataTimestamp is not supported

·         Balance information is not supported in the response

4.4 Optional Request Arguments

·         4.4.1 BrokerCode argument is not supported

4.5 Optional Response Header Fields

·         Set-Cookie – Supported and required for authentication

4.8 Optional Response Arguments

·         4.8.1 Balance-key – Unused and not supported

·         4.8.2 Access Control Information – Login response supports TimeoutSeconds

·         4.8.3 Office List Information – Login response supports OfficeList

 

5.0 Get Object Transaction

5.4 Optional Request Arguments

·         5.4.1 Location argument is supported

5.6 Optional Server Response Header Fields

·         5.61. Location – Supported

·         5.6.2 Description – Not Supported

 

6.0 Logout Transactions

                    ·         No optional responses are supported

 

7.0 Search Transactions

7.4 Optional Request Arguments

·         7.4.1Count argument is supported

·         7.4.2 Format argument is supported

AGENT
ACTIVEAGENT
OFFICE
RESIDENTIAL
LAND

COMMERCIAL
LEASE
MULTI-FAMILY
MEDIA
HISTORY
REMOVED

ALLPROP

·         7.4.3 Limit argument is supported

·         7.4.4 Offset argument is not supported

·         7.4.5 Select argument is supported

·         The server will return an error for any selected fields that are invalid

·         7.4.6 RestrictedIndicator is not supported

·         StandardNames support in the Query is limited to StandardNames that are advertised in the RETS Metadata. This list of names is limited to the number of fields that have been assigned Standard Names in addition to the system name.

 

12.  Get Metadata Transaction

12.3 Optional Request Arguments

·         Format argument is supported. COMPACT and SANDARD-XML formats adhere to the RETS Metadata DTD

·         The STANDARD-XML format does not support declaring the DTD version. The server only supports the 20021015 Metadata DTD format.

12.5 Optional Server Response Header Fields

·         Description – Is not supported

 

Transactions without optional features are omitted from the above list.  Please refer to the RETS 1.5 Specification for additional information.

 

 

Updated: 9/15/2010