Could not connect to RESO API - CRC Reality Website

edit

Hi Andy,

I'd recommend using other applications to perform the same types of requests. For instance if you're using cURL, download Postman and follow our instructions here to verify setup. You're at the troubleshooting stage where you've narrowed it down to something with your setup.

Now, bare in mind, ValleyMLS is using RETS, which is completely different. So, if you've been treating the Web API URI as you have been with ValleyMLS, then you need to change everything up.

Joe, we are using WebAPI for ValleyMLS not RETS. We switch over to the API connection over a year ago.

Hi Andy,

Then they must be using a different provider other than our PIC or OpenMLS solutions. Regardless, my troubleshooting steps remain unchanged.

Ok, understood. What else can we test to find the issue?

Please download Postman and continue your troubleshooting following our guide here has mentioned above.

Joe, I ran the Postman job and received an error. What's your email address so I can add you to Postman account to review?

joe.brueske@bkfs.com

invite sent

Receiving this error: 504 Gateway Time-out

client id and secret added to your BK OpenMLS Test. what else do you need to test?

Hi Andy,

I import a JSON collection to the team workspace and received an authorization token, and pulled metadata:

POST https://smlsa.paragonrels.com/OData/smlsa/identity/connect/token
200
1690 ms
Network

Request Headers
Content-Type: application/x-www-form-urlencoded
Authorization: Basic c21sc2FTaG9hbHNXb3JrczpOWUc2TUlwOTJsaWg=
User-Agent: PostmanRuntime/7.32.2
Accept: */*
Cache-Control: no-cache
Postman-Token: c1b3f914-0dd0-479e-b771-327ea0dbd302
Host: smlsa.paragonrels.com
Accept-Encoding: gzip, deflate, br
Connection: keep-alive
Request Body

Response Headers
Response Body
{"access_token":"","expires_in":7200,"token_type":"Bearer"}

Please review at your leisure. I did not see any setup collections or printout in the Console for your query.

Joe, what does the above mean? Not familiar with the Postman tool. If setup collections or printout are needed to test, can you add them?

Hi Andy,

Your server is returning can't resolve host. You're troubleshooting to figure out why that's happening. Postman is just a testing tool to compare your setup with. The Collection in Postman here is just a set of HTTP Requests. The output above shows that Postman was able to resolve the host and negotiate authorization to obtain a token. That at least tells you that it's working somewhere else with a different setup. I would recommend checking the Authorization section of the Postman setup, and make sure your client is configured the same way.

Outside of that, I can really only tell you that I'm not a network/server admin, and would be little help to you in troubleshooting server configurations.

Joe, can you confirm the MLS ID for Strategic MLS Alliance?

Token URL: https://smlsa.paragonrels.com/OData/s...

DD 1.7 SystemName: https://smlsa.paragonrels.com/OData/s...

Metadata URI: https://smlsa.paragonrels.com/OData/s...

EDIT: The MLSID is smlsa and is part of the URI schema

Hi Andy,

I wanted to check in to see if this is now working for you. Also, one of our developers suggested asking you folks for the IP address(es) that you're using. We can check to see if we're blocking any of them.

Also, I forgot to ask, which API client are you folks using?

Andy,

I just noticed higher up you mentioned the error you got using Postman was 504 Gateway Timeout error. Like I said, I'm not a network admin, but maybe there's something within your setup where proxy is involved. Maybe the tracert command works because it's setup correctly, and maybe other pieces aren't? I don't know. Just a suggestion.

Joe, the server IP is 45.76.255.73. We are using Realtyna to make the API connection to Strategic MLS Alliance.

It's important to note again, we use Realtyna to connect to 2 separate MLS accounts for CRC Reality; Strategic MLS Alliance (this one is not functioning properly) and ValleyMLS (this one is functioning without issue.

Let me know what your developers say about our IP address, thanks.

Thank you, Andy.

Just to clarify, the API requests are going to come from Realtyna? Do you happen to know the IP or range of IP's they're using?

I'll keep you updated.

So are you working with a WordPress site and using the Realtyna plugin to get the API data?
Or is Realtyna actually hosting your site too?

Joe, API requests come from our website via the Realtyna plugin. This has been the exact configuration since the site was launched a few years ago.

Bruce, we host the WordPress site and use the Realtyna plugin to retrieve API data. Again, this has been the exact configuration since the site was launched a few years ago.

Thank you Andy,

Is the plugin running the requests through 45.76.255.73 or a different server? Just want to make sure I understand where that IP address is assigned.

EDIT: Infrastructure checked that IP address already, and we're seeing traffic passing through.

Joe and Bruce, do you know if the MLS query based on MlsStatus is still supported to retrieve listings?

The following

Property/$filter=MlsStatus eq 'Active'

gave me the following count:

"@odata.count": 927,

Hi Andy,

Both MlsStatus and StandardStatus are valid DD fields. The use is different. StandardStatus has RESO specified lookups, and reflects the state of the contract. MlsStatus however, is used for local or regional statuses. Our view on MlsStatus is that it's the Category vs the individual Statuses. Hope that helps.

Also, we are working on adding messaging so when requested values don't exist, client side messaging isn't just a HTTP 500 error.