Not able to access RETS Feed

asked 2020-12-29 08:10:05 -0600

Hi,

Not able to access the RETS feed when using the URL from the Paragon RETS developer sheet. The url to fetch the metadata and search is as follows:

This URL is of login and works fine but:

RETS URL: https://gamls-rets.paragonrels.com/re...

Using this URL

http://<paragon.rets.server.url>/rets/fnisrets.aspx/mlsid/getmetadata?Type=METADATA- RESOURCE&Format=COMPACT&ID=0

http://<paragon.rets.server.url>/rets/fnisrets.aspx/mlsid/search?SearchType=Property &Class=ResidentialProperty&QueryType=DMQL2&Format=COMPACT&StandardNames=1&Select=ListingID,Lis tPrice&Query=(ListPrice=300000%2B)&Count=1&Limit=10

This doesn't work. I am using the <paragon.rets.server.url> = https://gamls-rets.paragonrels.com/</paragon.rets.server.url>

Is there something that I am doing wrong.

Please help.

Thank you.

edit retag flag offensive close merge delete

Comments

So you are using https?
Did you replace mlsid in your metadata and search urls with GAMLS?

bwolven gravatar imagebwolven ( 2020-12-29 08:40:56 -0600 )edit

Hi, with http also the same results. Where will I find mlsid?

davidhardik gravatar imagedavidhardik ( 2020-12-29 14:34:56 -0600 )edit

Same as position in your login URL, GAMLS.

bwolven gravatar imagebwolven ( 2020-12-30 08:50:08 -0600 )edit

Hi, I wasn't able to find out when I logged in... Can you please tell me how the mlsid will look like or something so I can look into it? Any examples of that sort. It would be great...

Thank you

davidhardik gravatar imagedavidhardik ( 2020-12-30 14:19:56 -0600 )edit

Update: We checked the document (paragon-rets-developer-start-guide.pdf) and tried to use the API (Basics of Using Paragon Metadata)

Below are the details

http://gamls-rets.paragonrels.com/ret...

MLS ID – GROVERAMIT And authentication which was provided by RETS

Response Received

404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.

davidhardik gravatar imagedavidhardik ( 2020-12-31 02:45:37 -0600 )edit

Not sure where you got GROVERAMIT from. In your case it should be GAMLS.

http://gamls-rets.paragonrels.com/rets/fnisrets.aspx/GAMLS/getmetadata?Type=METADATA-OBJECT&Format=COMPACT&ID=0


The URL prefix would be the same for all transactions.
"http://gamls-rets.paragonrels.com/rets/fnisrets.aspx/GAMLS/"

bwolven gravatar imagebwolven ( 2020-12-31 09:08:21 -0600 )edit

Hi,

While accessing this it gives this error: <rets replycode="20036" replytext="Miscellaneous server login error. Missing RETS-Version"> </rets>

Is there something else we are missing?

davidhardik gravatar imagedavidhardik ( 2020-12-31 11:54:56 -0600 )edit

Sorry add parameter &rets-version=rets/1.7.2 to each request you make.
It’s normally a header that is passed for each request from a RETS client.
But we also allow it as a URL query parameter as shown in your login URL.

bwolven gravatar imagebwolven ( 2021-01-01 08:51:19 -0600 )edit

So for the example above it would be something like this:

http://gamls-rets.paragonrels.com/rets/fnisrets.aspx/GAMLS/getmetadata?rets-version=rets/1.7.2&Type=METADATA-OBJECT&Format=COMPACT&ID=0
bwolven gravatar imagebwolven ( 2021-01-01 11:04:00 -0600 )edit

After hitting the URL provided, we are getting the following error

401 - Unauthorized: Access is denied due to invalid credentials. You do not have permission to view this directory or page using the credentials that you supplied.

davidhardik gravatar imagedavidhardik ( 2021-01-02 00:54:44 -0600 )edit

Hi, is there any direct number, webex or something that we can have a discussion and sort this out as I need to get it working asap. Kindly let me know.

davidhardik gravatar imagedavidhardik ( 2021-01-02 11:05:45 -0600 )edit

Hi, any update on why we are getting invalid credentials error.

davidhardik gravatar imagedavidhardik ( 2021-01-04 08:45:23 -0600 )edit

Are you calling Login first then Getmetadata?
Sequence:
1. Login
2. Getmetadata
3. Other transactions such as search ...
4. Logout

Not sure how you are testing this?
Is this in a web browser or from an application?
If an application, are you passing the RETS-Session-ID cookie returned by Login in the subsequent requests?

bwolven gravatar imagebwolven ( 2021-01-04 09:10:14 -0600 )edit