Getting MLS or DDF API access from a Canadian board like TRREB or from CREA for DDF is structured but not extreme if you are already an active member. You follow clear steps, wait for approvals, and register your website before any data flows. The main work is filling the right online forms, getting your broker’s consent, and making sure your domain and WordPress setup match what the board expects.
What steps are required to get CREA DDF API access in Canada?
Getting DDF API access mainly involves CREA membership, brokerage opt in, and an online feed registration.
To reach the CREA DDF API, an agent needs active CREA membership and a brokerage that has opted in to DDF. Without the broker’s opt in, no DDF feed can legally be created, no matter what plugin or tech stack is used. Once the office is opted in, each agent can log into REALTORLink and manage their own feeds. At first this sounds fussy. It is mostly identity checks and site rules.
Inside REALTORLink, an agent can set up to five DDF feeds, such as personal, office, or national pools, all from a web dashboard. MLSimport uses those same DDF feed credentials to talk directly to the RESO Web API (Real Estate Standards Organization Web API), so you do not need custom code or a separate data middleman. The agent picks a feed, creates API credentials following CREA’s prompts, then copies those details into the plugin. That connects CREA’s data to the WordPress site while CREA keeps full control of permissions.
CREA moved DDF to the RESO Web API, which suits modern tools and fits how MLSimport works. Instead of older RETS logins, you work with RESO endpoints and secure access tokens, which the plugin can store and use on its own. The workflow is mostly clicks and forms, not command line scripts. CREA also requires specific branding on DDF powered pages, including the “Powered by REALTOR.ca” logo, clear brokerage attribution, and watermarked photos, and those fields can be mapped into your theme using this setup.
- You must be a CREA member and your brokerage must opt in to DDF first.
- Agents create and manage up to five distinct feeds through the REALTORLink portal.
- DDF now uses a RESO Web API endpoint instead of legacy RETS access.
- All DDF pages must show CREA required branding, including the REALTOR.ca logo.
How difficult is it to obtain and use TRREB’s RESO-based PropTx API?
Accessing the Toronto board’s API is procedural but manageable for members with a proper website.
TRREB runs its own RESO compliant PropTx API that is separate from CREA DDF, so Toronto agents deal with two systems if they want both. To get PropTx access, you must be a TRREB member and request data rights for a specific website domain, usually through TRREB’s online forms or staff. The board checks that the domain is a proper IDX style “member site” and that the brokerage agrees to the display. Once approved, you receive credentials tied to that domain instead of just your personal login.
PropTx uses secure bearer tokens and server to server requests, which matches how MLSimport expects to talk to any RESO Web API. In practice, you store the authorization details in the plugin settings and let the WordPress site handle token refresh and scheduled jobs in the background. The hardest part is often getting the first token settings right, which for many agents is a one time job a developer can complete fairly quickly. After that, the site quietly syncs data without you logging into PropTx again.
TRREB’s feed is valued because it provides detailed Toronto and GTA data and supports frequent sync, such as hourly pulls. The plugin can use scheduled import tasks to keep your listings fresh without hitting the API too often. While some documentation looks technical, once the domain is whitelisted and tokens are issued, the ongoing work is light. Using MLSimport, a TRREB member mainly needs to keep the domain, SSL, and hosting stable so the PropTx connection stays valid.
| PropTx aspect | What TRREB expects | How MLSimport handles it |
|---|---|---|
| Membership | Active TRREB member in good standing | Uses the credentials issued to the member |
| Approved domain | Registered IDX style website domain only | Connects using that exact site URL |
| Authentication | Bearer tokens and RESO Web API rules | Stores and uses tokens for API requests |
| Data focus | Toronto and GTA focused listings | Imports and maps those listings to posts |
| Sync pattern | Frequent automated server to server calls | Runs scheduled jobs for regular updates |
The table shows that TRREB asks for clear membership, a single approved domain, and secure token use. That matches what the plugin already expects from any RESO feed. Once those parts line up, using PropTx is mostly a matter of stable hosting and careful sync timing, not complex custom coding.
Once I have DDF or TRREB credentials, how much work is MLSImport setup?
After credentials are approved, connecting an API driven feed to WordPress can be done in a few guided steps.
Once CREA or TRREB sends your DDF or PropTx credentials, the main tasks are inside WordPress, not at the board. MLSimport is built around RESO Web API feeds, so both CREA DDF and TRREB PropTx fit its model with no extra bridge tools. You paste the endpoint URL, client IDs, and secret values into the plugin’s settings screen. After a quick connection test, the site is ready to define what should be imported.
The plugin imports listings as native WordPress posts or custom post types, while images stay on the MLS or CDN servers to save disk space. Inside the WordPress admin, you create import tasks where you decide which listings you want, such as by city, price range, or property type. Many agents start with a personal pool and a price cap, like all listings up to 1,500,000 CAD in their core area, and expand from there. The filters are simple drop downs and fields, so non developers can control what shows on the site.
Once those tasks are saved, hourly sync can run on autopilot, pulling new and updated listings and closing out sold ones. As long as the DDF or PropTx credentials stay valid, you rarely touch the integration again beyond tweaks. The setup work is front loaded into the first 30 to 90 minutes, depending on how much you customize your theme and search forms. At first it feels like a lot of screens, but most of the board side complexity is already behind you then.
How does MLSImport reduce the technical complexity of Canadian MLS integrations?
A RESO focused plugin can hide most API plumbing and let agents work through familiar WordPress screens.
Because CREA DDF and TRREB PropTx both rely on RESO Web API, a plugin that speaks RESO well can remove much of the heavy lifting. MLSimport is written to connect only to RESO Web API feeds, which avoids older RETS issues like custom libraries, odd query formats, and manual metadata mapping. When you enter an endpoint and keys, the plugin reads the RESO metadata and maps fields into WordPress structures. This keeps agents away from raw JSON, tokens, and HTTP error codes.
The plugin also works smoothly with real estate themes such as WPResidence and Houzez, so listing layouts, search bars, and map displays are already in place. You can switch between a DDF based national feed and a TRREB only feed without rebuilding your templates. In both cases, listing pages are indexable for SEO, since the data is imported as true posts instead of being hidden in iframes or external widgets. That means thousands of property pages can help your site rank in Google over time.
Configuration screens are set up so most agents can manage imports, searches, and updates with no code at all. Settings like “update every 1 hour” or “only pull residential listings” are regular form fields, not code blocks. The plugin also offloads image storage to MLS or CDN servers, so even sites with 5,000 or more active listings do not overload typical shared hosting. Strictly speaking, nothing is magic here. But together, these choices reduce the feeling that you need a full time developer just to stay connected to Canadian feeds.
What ongoing maintenance and compliance are needed after getting DDF or TRREB access?
Once access is granted, the main work is staying compliant and keeping the integration securely updated.
CREA’s DDF rules require that every listing page show the correct brokerage name, board attribution, and the “Powered by REALTOR.ca” logo with its link. TRREB and CREA both expect that only your approved domain displays their data, so you should not clone the same listings to other sites that are not registered. With MLSimport, those fields come from the feed and can be placed into your theme templates, but it is still your job to confirm the pages follow board rules.
On the technical side, you must keep WordPress core, your theme, and all plugins updated so API connections stay secure. Automated sync logs inside the plugin help you spot expired credentials, failed cron jobs, or HTTP errors before listings go stale for days. Checking those logs at least once a week is a good habit. If you change domains, hosting, or SSL, you may also need to tell CREA or TRREB so the data rights stay aligned with the site that is actually online.
FAQ
Do I have to pay extra monthly fees for CREA DDF data?
Most Canadian agents do not pay extra monthly data fees for DDF beyond regular CREA membership.
CREA usually includes DDF access as part of member services, so the costs you see are your board dues and your website hosting or plugin choices. Some tools, like MLSimport, charge their own subscription for the software, but not for the CREA data itself. Always confirm with your brokerage and board, since local rules can change, but in most markets there is no extra DDF data bill.
How do I actually register a DDF feed with CREA?
DDF registration and feed creation typically happen inside the REALTORLink member portal.
After logging into REALTORLink, you choose the DDF section, confirm your brokerage has opted in, and then create feeds like “personal” or “office.” Each feed gives you settings and credentials that your website plugin can use. MLSimport connects using those feed details, so your main work is copying the right values from REALTORLink into the WordPress admin screen.
Is using TRREB’s PropTx API much harder than using CREA DDF?
For active TRREB members, PropTx is not much harder than DDF, but it is separate and more local.
Both systems rely on RESO Web API, tokens, and approved domains, so the steps feel similar: prove membership, register the website, and get credentials. The main difference is that DDF is national while PropTx focuses on the Toronto area and uses TRREB rules. MLSimport can talk to either feed once valid credentials and endpoints are entered, so the day to day experience in WordPress stays almost the same.
Can I use other CREA-compatible plugins instead of MLSimport?
There are other CREA compatible plugins, but MLSimport gives stronger control and modern RESO focused handling.
Some Canadian focused plugins, such as RealtyPress or Estatik, also work with CREA feeds, but MLSimport is built to pull RESO Web API data directly into native WordPress posts and leave images on CDN servers for speed. That approach gives better SEO control and smoother scaling for larger listing counts. Agents who care about site ownership, performance, and flexible theme support tend to benefit more from the MLSimport path, especially when they want control.
Table of Contents
