Four more RESO Web API servers are connected in MLSImport, and each asks for a different set of credentials. Rapattoni needs four values, Paragon and Realcomp need two, and ConnectMLS needs a username and password.
Selecting your MLS in the plugin reveals the right fields automatically. This page tells you what to request from your MLS so the values you receive match the boxes you get.
Rapattoni
Rapattoni is the only server here that combines an application credential with a user login. You need all four values, and a connection test with three of them fails silently rather than telling you which is missing.
- Client ID, entered in MLSImport Rapattoni Client id.
- Client Secret, entered in MLSImport Rapattoni Client Secret.
- API username, entered in MLSImport Rapattoni Username.
- API password, entered in MLSImport Rapattoni Client Password.
Ask your MLS for all four together, described as the client credentials and the API user for RESO Web API access. The API user is issued for the feed and is not your MLS member login.
Rapattoni feeds report property type more coarsely than most servers, so a filter split across property type and subtype behaves differently here. Import a small batch first and look at what came in before building tasks around a type filter.
Paragon
Paragon issues a Client ID and a Client Secret, entered in MLSImport Paragon Client id and MLSImport Paragon Client Secret.
Paragon installations are per MLS, so the endpoint your board uses is specific to them. You do not enter it, but mentioning your board name when you ask helps their support give you credentials for the right instance.
ConnectMLS
ConnectMLS authenticates with a username and password issued for API access, entered in Your ConnectMLS Username – provided by your MLS and the password field below it.
Ask for API credentials explicitly. A member login to the ConnectMLS front end is not the same credential and will not authenticate a feed.
Realcomp
Realcomp issues a client ID and a client secret. In the plugin, those go into the two Trestle labelled fields: Your Trestle Client ID – provided by your MLS and Your Trestle Client Secret – provided by your MLS.
The Trestle label on a Realcomp connection is expected. Both servers take the same credential shape, so they share the two fields. Enter your Realcomp values there and save.
Before you connect, confirm with Realcomp that your data access application is approved, that your account is active, and that you have the token or client credentials for it.
Credentials entered in the wrong provider’s boxes fail the connection test even when the credentials themselves are perfectly valid. If a test fails and you are sure of the values, check that the MLS selected above them is the one they were issued for.
After any of these connects
- Save the credentials, then run the connection test. Saving clears the previous test result, so a re-test is always required.
- Load the field list and choose your import fields. The list comes from your own feed, so it shows what your MLS actually returns.
- Create an import task and run a small batch before importing at scale.
Frequently asked questions
Why does my Realcomp connection say Trestle?
Because the two servers use the same credential shape and share those two fields in the plugin. It is a label, not a routing decision. Your Realcomp credentials are sent to Realcomp.
Rapattoni gave me only a client ID and secret. What now?
Go back and ask for the API username and password as well. Rapattoni authenticates with both the application credential and a user login, and the connection cannot be completed with half of the set.
Can I use my MLS member login for any of these?
No. Every one of these servers issues credentials specifically for API access, separate from the login you use to work in the MLS. Ask for RESO Web API credentials by name.
My MLS is on one of these servers but is not in the list.
Each MLS is activated individually, so being on a connected server does not automatically put your board in the search. Send us the exact MLS name, and clear the plugin cache after we confirm it is live, since the MLS list is cached for 24 hours.
Related
- CoreLogic Trestle credentials
- What RESO Web API access is and why you need it
- My MLS runs a server you do not support yet
- Verifying your MLS connection
Tell us which of these servers your MLS runs and we will confirm exactly which values to request.