First time here? Check out the FAQ!

PACMLS 403 response

Hello Paragon support team, we recently started receiving a 403 response from the RETS server at: Username: none Password: **

RETS Connector response attached for reference. Let me know if this is expected, thank youC:\fakepath\image_2023_02_27T12_31_23_865Z.png

Ylopo IDX Support's avatar
Ylopo IDX Support
asked 2023-02-27 09:14:17 -0500
bwolven's avatar
updated 2023-02-27 18:20:13 -0500
edit flag offensive 0 remove flag close merge delete


Hi Ylopo IDX Support,

In your screenshot it looks like you're sending a RETS Digest, but are using an HTTPS URL. This should be dropped, as Basic Authentication is used with HTTPS. Let us know if this doesn't fix it.

Additionally, we recommend switching from using RETS 1.5 to 1.8 to leverage the benefits in that version. You can find the specifications in a ZIP file located here from RESO.

Joe_Brueske's avatar Joe_Brueske (2023-02-27 11:21:25 -0500) edit

Please try this again.
I looks like you hit the max logins per day limit which is 20,000 for PACMLS.

bwolven's avatar bwolven (2023-02-27 17:01:08 -0500) edit

Thank you @Joe Brueske, we are now able to access the feed however no listing data is returned for a broad query on the "1. RE" (Residential) resource, example request below:

Search query: (L_UpdateDate=2023-02-20T00:00:00)

Do you know why there would be no listings returned for this request? Thank you for the assistance so far!

Ylopo IDX Support's avatar Ylopo IDX Support (2023-02-27 18:08:50 -0500) edit

You need to add the plus: (L_UpdateDate=2023-02-20T00:00:00+) to say from that date forward.
Also, L_UpdateDate is in UTC, so make sure to factor that into your queries.

bwolven's avatar bwolven (2023-02-27 18:12:15 -0500) edit
add a comment see more comments

1 Answer


Thank you very much @bwolven, super helpful as always and apologies for the misformatted L_UpdateDate query. It looks like we are all set:

Server: User name: none Full pull Local time: 2/27/2023 6:39:20 PM Server time: Tue, 28 Feb 2023 02:39:20 GMT

Running step "1. RE"

Search query: (L_UpdateDate=2023-02-20T00:00:00+) 606 records downloaded RETS Status code = 0: Operation Successful Step finished at 2/27/2023 6:39:28 PM

Ylopo IDX Support's avatar
Ylopo IDX Support
answered 2023-02-27 20:40:07 -0500
edit flag offensive 0 remove flag delete link



bwolven's avatar bwolven (2023-02-28 04:15:28 -0500) edit

Hi @bwolven, we are once again receiving that 403 forbidden response when attempting to connect to the server, is this expected and did we overrun our 20k requests limit? Apologies if so, I have restated this limit to our engineering team.

Also if there is documentation on the data usage limits for Paragon IDX feeds please let me know!

Ylopo IDX Support's avatar Ylopo IDX Support (2023-02-28 09:06:49 -0500) edit

Looks like you hit 48003 login attempts in a 24 hour period and the limit is 20000.
It resets at midnight CST
Not sure how you are pulling stuff but you will need to reduce your number of logins.
I did reset it for you so you can continue working on it.

bwolven's avatar bwolven (2023-02-28 11:57:52 -0500) edit

Understood Bwolven, apologies on overrunning those limits. We will reduce the number of logins going forward!

Ylopo IDX Support's avatar Ylopo IDX Support (2023-02-28 13:47:59 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer