How will I pull photos? 

The DDF® payload will now expose the image URLs for all three photo types: 

•ThumbnailPhotoURL (low resolution); 

•PhotoURL (medium resolution); and

•LargePhotoURL (high resolution).

What does this mean for my business? You will now have two options to retrieve photos from DDF®: 

1.   Store the URLs in your system and embed them directly into your websites. The benefit of this method is not having to download and store every possible listing image for every customer’s site. This will also allow you to manage your DDF® better feeds by reducing the time needed to keep the feeds in sync and removing the need for large amounts of file storage. This is the recommended approach for most DDF® clients. 

2. You can also download images using the URL instead of streaming through the GetObject function of the Object.svc and continue storing photos within your system. 

What happens if I don’t make the change by July 6, 2020? 

If you don’t make any changes, your websites will not receive any photos from DDF®. 

1. building queries (e.g. return all properties in the $300K-$500K range, with 3+ bedrooms)
2. indicating which fields the user would like returned (e.g. return only Address, Price and BedroomCount for each listing)

By design, CREA’s DDF® service does not allow ad-hoc querying. Clients are expected to pull all listings available to them, and not choose a subset at runtime. If the registered owner of the destination wants filters applied to their data feed, they can be configured in the DDF® dashboard (http://tools.realtorlink.ca). The only value that can be directly queried is the ID field for each resource type.

CREA’s DDF® service also does not allow clients to customize the data included in the response. All DDF® clients receive the same Standard-XML data payload. The RETS Select concept that users can pick and choose which value to include is more practical when providing Compact (i.e. tabular) data, which is not supported. Since clients cannot customize the format of the results, data fields are not required in metadata calls.

A “Not Logged In” error being returned after a successful Login is likely occurring because you are not including the X-SESSIONID cookie that was set in your Login response. This X-SessionID value needs to be submitted with every request after logging in. CREA’s DDF®Data Feed validates that the X-SessionID and credentials match on every request, so if its missing, you’ll get a “Not Logged In” response.The RETS 1.7.2 specification requires clients to include any cookies set by the server:

http://www.reso.org/specifications (See section 3.3 Required Client Request Header Fields)