First time here? Check out the FAQ!

Missing fields - depending on RETS client used

We have a custom RETS library that we've used for years to query RETS data. Recently, we upgraded the code to authenticate correctly with RETS version 1.7.2 (not sure if this is related to the problem, or just coincidence).

Now, the library is no longer able to retrieve Lat/Lng geo points for listing data. They just come back blank.

To troubleshoot, we used the RETS Connector tool using all the same server URL and credentials for our RETS account. The RETS Connector tool did return lat/lng geo data.

We use the same server and credentials in our custom library, and while we get other listing data without problem, the lat/lng data are missing.

Using WireShark, we were able to determine that the two HTTP requests very similar with two notable differences:

  1. The RETS Connector uses a GET request with a query string while our custom library uses a POST with form data.
  2. The user agent string is different (obviously)

Aside from that, we could identify no notable differences. The RETS select fields were the same. The actual query was the same, etc.

We've been assured that our profile and permissions haven't changed, and it doesn't make sense that this would be the problem anyway since one tool can get the data while the other can't.

Any idea how this could be happening?

integrinet's avatar
asked 2015-09-09 13:28:02 -0500
edit flag offensive 0 remove flag close merge delete


Can you provide a little more information: RETS login URL and the user agent you normally send? Also, are the lat/long columns there and just empty or are they missing completely?

bwolven's avatar bwolven (2015-09-09 18:22:56 -0500) edit

The RETS Login server: The full login URL: User agent: IntegriNet/1.1

The lat/lng columns are there, but they are just missing actual data. We work for the MLS. The permissions are wide open.

integrinet's avatar integrinet (2015-09-10 11:24:15 -0500) edit
add a comment see more comments

2 Answers


Latitude/Longitude retrieval was not enabled for User Agent: IntegriNet. We have enabled it so should be working now. If you haven't done so already, make sure to logout and do a fresh login to make sure the setting is applied. Please let us know the results. Thanks.

bwolven's avatar
answered 2015-09-11 08:13:51 -0500
edit flag offensive 0 remove flag delete link


Thanks for fixing that configuration. Everything is working well now.

integrinet's avatar integrinet (2015-09-11 09:53:27 -0500) edit
add a comment see more comments

For the most part, latitude and longitude values are not available via RETS, unless you have a specific agreement with the MLS to get that information. I'm not sure that's the issue in this case, but that is a possibility. As Bruce mentioned, we'll need more details to properly troubleshoot the problem.

vendorsupport's avatar
answered 2015-09-10 09:05:27 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments

Your Answer

Login/Signup to Answer