RESO Common Format (RCF)

The RESO Common Format (RCF) is a new endpoint format provided by the Trestle API that enhances the standard RESO WebAPI experience by providing more developer-friendly data structures.

Key Differences

Multi-Enum Fields

The primary difference between the standard RESO WebAPI and RCF is how multi-enum fields are handled:

Standard RESO WebAPI (/odata): - Multi-enum fields are returned as comma-separated string values - Values use enum identifiers rather than standard names - Requires client-side parsing and enum lookup

RESO Common Format (/rcf): - Multi-enum fields are returned as arrays - Values use standard RESO names instead of enum identifiers - No client-side parsing required

Example Comparison

Standard WebAPI Response

Check Icon{
  "PropertyType": "Residential,Commercial",
  "Heating": "CentralAir,ForcedAir"
}

RCF Response

Check Icon{
  "PropertyType": ["Residential", "Commercial"], 
  "Heating": ["Central Air", "Forced Air"]
}

Authentication

RCF endpoints use the same authentication mechanisms as standard RESO WebAPI endpoints:

• Bearer token authentication
• Same scopes and permissions
• Identical rate limiting