Toronto Regional Real Estate Board delivers its RESO Web API through PropTx, whose API is known as AMPRE. MLSImport connects to it, and the credential is a single bearer token you paste into the server token field.
PropTx boards were added as their own provider rather than being treated as a generic feed, because AMPRE is stricter than most servers about how requests are formed.
What PropTx issues
PropTx issues one long bearer token for your approved data feed. There is no client ID and secret pair to exchange, and there is nothing that expires on a rotation schedule the way a Trestle secret does.
That makes the plugin side short. The whole connection is the MLS selection plus that token.
Getting the token
- Apply through your board for RESO Web API data access for your website. TRREB members go through the board’s data services route, not through PropTx directly.
- State the domain the listings will be displayed on. Approvals name the site.
- Ask for the AMPRE bearer token for your approved feed, and ask which feed type you were granted, for example IDX or broker.
- Ask for the API documentation link if they offer one. It tells you which fields your feed carries.
Expected result: a bearer token tied to your account, your feed type, and your domain.
Ask which feed type you were approved for before you build filters. An IDX feed and a broker feed return different sets of listings, and a filter that returns nothing is often a feed scope question rather than a filter mistake.
Entering the token
- Open MLS Import Settings and find your board in the Your MLS search.
- Paste the token into Your API Server token – provided by your MLS. PropTx boards use the same server token field as Bridge and Spark markets.
- Save, then run the connection test.
What the plugin does differently for PropTx
Two provider specific behaviours are handled for you, and both are worth knowing because they explain symptoms you might otherwise misread.
- Timestamps are sent in full OData form. AMPRE rejects a shortened timestamp on the modification filter that other servers accept. The plugin expands it before sending, which is what keeps hourly sync returning changed listings instead of zero.
- Media is requested with the listing. Photos come back in the same response rather than through a second call.
Photo selection on AMPRE feeds does not always mark a preferred image the way other feeds do. The plugin falls back to a sensible order rather than leaving a listing without a main photo.
If hourly sync reports no changed listings on a PropTx feed while listings are clearly changing in the board, check that the plugin is current before anything else. That symptom is exactly what an unexpanded timestamp produces, and it was fixed on the plugin side.
Frequently asked questions
Is AMPRE the same as PropTx?
PropTx is the provider and AMPRE is the RESO Web API it serves. When your board says PropTx and the documentation says AMPRE, they are describing the same feed.
Do I need a separate Realtor.ca DDF connection as well?
No, and you could not use both on one site. MLSImport connects one MLS per install. Choose the feed with the coverage and fields you need, and if you want both you need two sites and two subscriptions.
My token works but some listings are missing.
Check your feed type and your import task filters in that order. A broker feed only carries listings tied to your brokerage, which looks like missing data if you expected board wide coverage.
Does PropTx access cost extra?
Whatever your board charges for data access is separate from your MLSImport subscription and is billed by them. Ask your board for their current data services fees.
Related
- REALTOR.ca DDF credentials
- What RESO Web API access is and why you need it
- Verifying your MLS connection
- Who needs to hold the credentials
Send us your board name and token and we will confirm the connection and the feed scope with you.