Strategic MLS Alliance Missing Listings [closed]

edit

Any hint on why this feed is behaving much differently from other Paragon Web API feeds? Even with a select on ListingKeyNumeric / ModificationTimestamp, it seems we are not pulling all of them.

Basically, there is no @odata.nextLink, so we need to skip "manually"?

Correct. We don't currently support nextLink.

When using the $Count we get "@odata.count":1021, but the original RETS feed had 2116

bwolven can you confirm how many active listings are in the Strategic_17 feed?

It looks like the StandardStatus doesn't have a value in all Property Types
Try this: $filter=(MlsStatus ne '(20) Sold - Sold')
I show 2073 when I use that filter.

I get a 500 error when trying to use that filter

Just tried that, getting a 50x. Also tried with 20, '20' and 'Sold', same result.

Are you sending more than one $filter parameter?

I did it with modificationtimestamp and by itself. https://smlsa.paragonrels.com/OData/S... ne '(20) Sold - Sold'). Copied it from here to there.

There are two spaces after the (20)
I think the site is stripping extra spaces.

Yeah adding the space worked. Question on top & skip. . . when going over the sets of data, does top count from the skip, meaning do both have to increment or just top?

This works, thanks. Any chance this different format will be documented anywhere? The usual paragon api feeds are way easier to work with.

Skip is similar to RETS offset but $skip is zero based.
Top is similar to RETS limit, the number of rows to return.
So you would set your batch size with $top and increment $skip by the batch size.
So:
$skip=0&$top=10
$skip=10&$top=10
$skip=20&$top=10
etc.

I think RETS is easier to work with too.
But I'm a little biased since I have worked with RETS it for many years.
But I guess it is the wave of the future whether we like it or not.

SMLSA does not match the documentation, so it would be nice if there was some that matched up to it, given it seems to be nonstandard.