What RESO Web API access is and why you need it

RESO Web API access is a data connection your MLS grants you, letting a program read listing data directly instead of a person reading it on a screen. MLSImport needs that connection and cannot create it for you. Your MLS issues it, to you, for your website.

This page explains what the access is, what your MLS hands over when it is approved, and how to find out what your MLS runs before you apply.

What RESO Web API means

RESO is the Real Estate Standards Organization, which defines how listing data is described and transmitted. The Web API is its modern delivery method: an OData feed your site queries over HTTPS, returning listing records in a standard shape. RESO’s own Web API page puts it as “the modern way to transport data in the real estate industry”, built on open standards, and names OData as the protocol at the core of it, while describing RETS as a deprecated transport the industry is moving off. Checked August 19, 2026.

Standard shape is the part that matters to you. It means the field holding a price is called ListPrice whether your MLS is in Florida or Alberta, so a plugin can map that field once and work across hundreds of markets.

Two older delivery methods still get offered and neither works here.

1. RETS. The previous generation of MLS data transfer. MLSImport does not read RETS. If your MLS offers both, ask for Web API.
2. A frameable IDX link or a hosted search widget. Someone else’s search running inside a frame on your page. Nothing is imported, so nothing is yours.

What you need to have

1. MLS membership. You are an agent, broker, or office with a current MLS account, or you are building for someone who is.
2. An approved data access application. Your MLS reviews and approves the request, usually naming the domain the data will be displayed on.
3. Web API chosen as the delivery method. Where an MLS portal offers a choice, pick Web API rather than RETS or IDX framing.
4. The credentials that approval produces. Either a single server token, or a client ID and a client secret. Which one you get depends on the server your MLS runs.

Finding the server your MLS runs on

Your MLS does not usually operate its own API server. It publishes through a platform, and that platform decides which credentials you receive and whether MLSImport already connects to it.

1. Open the RESO MLS list and find your MLS. Note its UOI, an identifier like M00000105.
2. Open the RESO certification directory, search the same name, and open its summary.
3. Read the Web API Server line. It names the platform: Trestle, Bridge, Spark, Paragon, Rapattoni, and so on.

The certification site is a JavaScript application, so open it in a browser. Fetching the URL with a script returns an empty page.

Which servers MLSImport connects to

MLSImport connects to CoreLogic Trestle, Bridge, Spark (the platform behind FlexMLS), Paragon, Rapattoni, ConnectMLS and Realcomp, MLS Grid, BrightMLS, RMLS, UtahRealEstate, Realtor.ca DDF, and PropTx AMPRE. Each link is the credential guide for that server; BrightMLS, RMLS and UtahRealEstate have no separate guide yet.

This list was checked on August 19, 2026 and left unchanged. The search your MLS box in the plugin’s account step is the live authority, because servers are added between checks.

If your MLS runs one of those, the work is on the MLS side: get approved, get your credentials, enter them. If it runs something else, the server can be added. That case has its own article.

What the credentials look like

Servers issue one of two credential shapes, and the plugin shows the fields matching the MLS you select.

1. A server token. One long string, used as-is. Bridge, Spark, RMLS, UtahRealEstate, and PropTx work this way.
2. A client ID and client secret. The plugin exchanges the pair for a short-lived access token on every run. Trestle, Realtor.ca, Paragon, BrightMLS, and Realcomp work this way.

Rapattoni is the exception that needs four values: a client ID, a client secret, and an API username and password. ConnectMLS needs a username and password only.

Frequently asked questions

Does having MLS membership automatically include RESO Web API access?

No. Membership makes you eligible to ask; the MLS decides whether you get it. Feed access is a separate approval on top of your account, and boards differ on who qualifies: some grant it to brokers only, some require a broker’s written authorisation before an agent can hold credentials, some charge for it, and some approve it per domain. A licence and a current MLS account are the entry requirement, not the grant.

Can MLSImport get the API access for me?

No. We are not an MLS vendor and cannot apply, sign, or hold credentials on your behalf. The application is made by you or your broker directly with the MLS, and the credentials are issued to your account. We verify them and connect the site once you have them.

My MLS offers RETS and Web API. Does it matter which I request?

Yes, request Web API. MLSImport reads the RESO Web API and does not support RETS. An approved RETS feed cannot be converted on our side, so requesting the wrong one means going back to the MLS.

Do I need one set of credentials per website?

Yes in practice, because MLS approvals name the domain the data is displayed on, and MLSImport connects one MLS per WordPress install. Two sites means two approvals and two subscriptions.

The MLS asked who my vendor is. What do I answer?

Answer according to their form. Some MLSs have a member route with no third party vendor and a separate vendor route, and members applying for their own feed usually take the member route. If the form requires a vendor to be named, ask the MLS which option fits a member using their own plugin on their own site.

Related

1. Who needs to hold the credentials
2. My MLS runs a server you do not support yet
3. Requirements before you buy
4. Connecting your MLS in the wizard

Send us your MLS name and we will tell you which server it runs on and which credentials to ask for.