bryce's profile - activity

I found these by using Postman with $top=10 then used MlsStatus ne '{status}' and MlsStatus ne ({other status}' ... As

I'm seeing the same. Here are the status values I found. Since this was an unannounced change they may change it back so

I found these by using Postman with $top=10 then used MlsStatus ne '{status}' and MlsStatus ne ({other status}' ... As

I'm seeing the same. Here are the status values I found. Since this was an unannounced change they may change it back so

I'm seeing the same. Here are the status values I found. Since this was an unannounced change they may change it back so

I'm seeing the same. Here are the status values I found. Since this was an unannounced change they may change it back so

Using the following URL I am getting the following 400 response using Postman. This query stopped working on the 6th.

https://smlsa.paragonrels.com/OData/SMLSA/Strategic_17/Property?$filter=MlsStatus eq '_10__Active___Active'&$top=10

{
"error": {
    "code": 400,
    "target": null,
    "message": "Keys with secondary physical numbers cannot specify destination field: '[47.23]@Selling Office 1 PHONENUMBE R 1 DESC'",
    "details": null,
    "innerError": null
}

}

Oddly, using not equals does work. The following query works as expected.

https://smlsa.paragonrels.com/OData/SMLSA/Strategic_17/Property?$filter=MlsStatus ne '_20__Sold___Sold' and MlsStatus ne '_40__Expired___Expired' and MlsStatus ne '_50__Withdrawn___Withdrawn_Or_Cancelled' and MlsStatus ne '_51__Withdrawn___Temporary_Off_Market' and MlsStatus ne '_60__Leased___Leased'&$top=5000

This issue appears to be resolved now.

Web API - Use of oData standard field @odata.nextLink for paging Hello, Are there any plans on using oData standard @od

Strategic Alliance gives Bad Response on simple Actives Query Using the following URL I am getting the following 400 res

MauiMLS, Thanks for the update. I am able to get photos now as well. Bruce, Thanks for the response.

MauiMLS, Thanks for the update. I am able to get photos now as well.

MauiMLS, Thanks for the update. I able to get photos now as well.

The curl command outputs: <title>ERROR: The request could not be satisfied</title> </head><body&

You can see the IP address I get for that domain. If you use curl to get image and have the domain resolve to the same

You can see the IP address I get for that domain. If you use curl to get image and have the domain resolve to the same

You can see the IP address I get for that domain. If you use curl to get image and have the domain resolve to the same

You can see the IP address I get for that domain. If you use curl to get image and have the domain resolve to the same

Bruce, this might be useful for reproducing the issue. If I take this example image: https://cdnparap50.paragonrels.

Bruce, this might be useful for reproducing the issue. If I take this example image: https://cdnparap50.paragonrels.c

"I have been grabbing data for 5 years.. never had this problem... until last week..." Same here. Bruce, I think you're

Are there any rules on image pulling that blocks IP addresses on repeated requests to access the same resource?

I'm in Arizona, my office is in California. Our image server is in a colocation separate from the office. A quick googl

Since it's CDN it should resolve to different servers based on location.

We dug more into the issue. It's an issue when the image domain resolves to IPs in the 13.0.0.0 subnet. https://cdnpara

CDN for image urls giving 504 error Images are failing to load on our feed processing server. CloudFront, the CDN Parago