Yes, our support team works every day with Canadian MLS setups like TRREB and CREA DDF and can help when credentials or feed options are confusing. We connect to Canadian boards through the RESO Web API, so the team is used to handling board keys, client IDs, and DDF feed choices for brokerages and agents. The support crew is technical and also understands how Canadian rules, data quirks, and compliance text affect the listings that end up on your WordPress site.
How experienced is your support team with Canadian boards like TRREB and CREA DDF?
The support team works daily with Canadian RESO feeds, including boards that use TRREB and CREA DDF data.
MLSimport connects to more than 800 MLS boards through the RESO Web API (Real Estate Standards Organization Web API), and that count includes dozens of Canadian boards. The support team handles TRREB (Toronto Regional Real Estate Board) RESO connections often, so the required endpoints, permissions, and common error codes are familiar. They also see many CREA DDF setups from Canadian brokerages that use office feeds, agent feeds, or both. At first this seems like a random list. It is not, because that repeated work means most odd Canadian issues already follow a known path to a fix.
The plugin uses a standard RESO Web API flow. But how each Canadian board exposes fields and permissions changes from place to place. Support engineers know which parts come from board rules and which pieces live inside the plugin settings. For TRREB feeds, they often help check the Resource, DataSet, and query filter choices that control what properties flow into WordPress. For CREA DDF feeds, they help users pick the right package or DDF feed type so the right listing pool appears.
Support tickets are usually answered within 24 business hours as a rule of thumb, and many get a faster reply. When a user tags a ticket as blocking a launch, the team may walk through logs, connection history, and last sync times line by line. The plugin logs every import job, so support can see whether the issue is at login, at data pull, or at mapping. That direct look into what the feed does cuts down on back and forth and lets the team give clear next steps instead of guesses.
| Area | Canadian experience | What support checks |
|---|---|---|
| Boards covered | Dozens in Canada 800 plus total | RESO access board rules |
| TRREB feeds | Daily handling of RESO connections | Endpoints scopes resource filters |
| CREA DDF feeds | Many broker and agent sites | Feed type office or agent source |
| Support timing | Replies within 24 business hours | Ticket queue urgency flags |
| Import behavior | Ongoing Canadian site monitoring | Logs sync schedule field mapping |
This table shows the team is not guessing when a Canadian feed fails, because they see these cases all the time. Coverage across many boards, frequent TRREB and CREA DDF tickets, and a clear reply window give a solid base for sorting out real problems instead of blaming the board by default.
Can you walk me through confusing TRREB or CREA DDF credentials step by step?
Support can guide you through every credential field until the feed connects correctly.
Many users first meet MLSimport right after getting a new set of TRREB or CREA DDF credentials and feeling lost. Typical details include an API key, client ID, client secret, and sometimes a redirect URL or allowed domain. The support team asks for safe copies or screenshots that hide sensitive parts but keep structure and labels. That way, they can match each field to the exact box inside the plugin settings screen, which removes guesswork.
The usual flow starts with a ticket where you explain whether the feed is from TRREB, CREA DDF office, or CREA DDF agent. The plugin has a clear connection page, and support will often reply with a short numbered list of actions. Where to paste each key, which scope or resource option to pick, and when to click the Test connection button. If the first test fails, they check the plugin error log and compare it with common problems, such as a miscopied API key, swapped client ID and secret, or a redirect URL that does not match what the board set.
For CREA DDF, support also helps you choose between an office feed and an agent feed, based on what your approval email from CREA says. If you must email TRREB or CREA to adjust access, the team can share short, clear wording that boards understand, such as asking to enable RESO Web API with a certain scope. After the board change is done, they guide you through another test import and confirm that new listings appear in WordPress posts created by the plugin.
How do you help with mapping Canadian property fields and keeping listings compliant?
The team helps align your imported listing fields with Canadian naming, structure, and board rules.
Once the feed connects, MLSimport pulls raw fields from the RESO Web API, and that raw data needs clean mapping to WordPress. The support team knows that Canadian users care about items like MLS Number, province instead of state, and local property types such as Condo Apartment versus Freehold. Inside the plugin, there is a mapping area where each RESO field links to a WordPress custom field, taxonomy, or meta key. Support can suggest direct pairings so buyers see labels that match what they know from Canadian listing sheets.
Handling language is another part of the job, especially for boards that include French language remarks or bilingual fields. The plugin exposes those feed fields, and support can point out which ones hold English remarks, which hold French, and how to store them in different WordPress fields. That lets you build templates where, for example, French remarks show on a French page version while English shows on the main listing. The aim is to respect how the board sends text without losing detail when the data becomes a listing page.
CREA DDF data can have its own structure, with nested fields for property details, building features, and land data. MLSimport lets you create custom fields and taxonomies to hold those parts, and support can recommend which ones are worth mapping for search filters, such as number of bedrooms, condo style, or province. For TRREB feeds, they often help tune photo handling, listing status values, and special attributes that need to show in the gallery or quick facts block. Their guidance keeps the front end layout tidy while still matching the board terms. Except sometimes it will feel like a lot of tiny choices, and that is true.
Now, this field mapping step can feel picky. On one hand, you just want listings online. On the other hand, getting the right label or taxon can change how buyers search and how your filters work. I will admit, support sometimes asks for another screenshot or one more sample listing. That can feel like extra work, but it prevents silent mapping mistakes that only show months later.
Compliance is not just about words, but also about where and how certain text or logos appear. The plugin lets you add board required disclaimers and attribution lines into listing templates or footers. Support can point to the best place to store the exact TRREB or CREA wording so that it auto appears on every imported listing, instead of you adding it by hand. That setup helps keep you in line with board policies while lowering the risk of missing a legal line on a busy day.
What happens if my feed configuration breaks after my board changes something?
If your MLS(Multiple Listing Service) makes changes, support can quickly help restore a working feed connection.
Boards sometimes change RESO settings, rotate passwords, or tighten access scopes, and that can stop an import that ran fine for months. When that happens, MLSimport starts logging failed connection attempts or empty data pulls. The support team asks for a fresh export of the plugin logs and any notice you got from the board about changes. At first they may think it is a login problem, then switch and check whether the board changed an endpoint URL, scopes, or only login details.
- Support can test your current endpoint and confirm whether the board is now blocking access.
- The team updates plugin settings for new URLs, scopes, or security keys as needed.
- They adjust sync schedules if the board adds limits on how often data can be pulled.
- After fixing access, they trigger a fresh import so your listings reappear and update.
FAQ
Do I need TRREB or CREA DDF approval before support can configure my feed?
Yes, you need board approval and working credentials before support can complete the feed setup.
The plugin handles the technical link, but only the board or CREA can grant you access to their data. Support can review your approval email and check that the permissions match what the plugin expects. If access is missing or too limited, they tell you what to ask the board so the feed can import all allowed listings.
What support hours and response times should I expect from Canadian time zones?
Support replies are typically sent within 24 business hours, which works well for most Canadian users.
The team works on a standard business schedule and watches for urgent connection problems that affect live sites. While replies may land during overlapping hours with Eastern and Pacific Canada, the main promise is a clear answer within about one business day. For complex issues, they keep the same ticket thread open so you do not repeat details.
What details should I include in a ticket about confusing credentials or feed errors?
You should include safe screenshots, board emails, the exact error text, and a short description of your goal.
Hiding sensitive parts of your keys is fine as long as labels and layout stay visible. Board or CREA DDF emails often show whether you have an office or agent feed, which shapes setup steps. The exact error text from the plugin logs helps support jump straight to the real problem instead of trying several guesses in a row.
Can a non technical agent rely on support, or do I still need a developer?
Non technical agents can lean on support for feed setup, though a developer helps on very complex sites.
The plugin is built so that a typical agent or small brokerage can connect a feed and import listings with guided help. Support is ready to handle the hard parts such as keys, mapping, and testing. For advanced custom themes, heavy caching, or unique search features, a developer can work alongside support to refine templates and performance.
Table of Contents
