First time here? Check out the FAQ!

Regarding Paragon API Set Up

  • retag add tags

We are having trouble connecting to the Paragon API odata feed. Our initial connection through Postman is failing, and a 'resource not found' error message displays.

I have authorization set to bearer token, and am using the Server Token as Bearer Token in the set-up. This is being passed through in the header.

We get the following message: { "error": { "code": 404, "message": "Resource could not be found" } }

I have also attempted to set up OAuth 2.0 authorization using my client id/secret, and '' as the access token URL. I get an 'Authentication Complete' message from Postman when I click 'Get New access Token', but no token is generated.

The credentials we have been provided are:

Client ID: fOUx3dNHlhcYWNLAZfZB

Server Token: 6c27097499f5a85151ebc9f4856964a0

Browser Token : 75181183c9207aa22f0e2889f2b7b538

Thank you for your assistance, Dan Neiman ZapLabs

djn1990's avatar
asked 2022-07-19 10:45:58 -0500, updated 2022-07-19 10:52:15 -0500
edit flag offensive 0 remove flag close merge delete


What MLS are you trying to connect to?

bwolven's avatar bwolven (2022-07-19 13:24:39 -0500) edit
add a comment see more comments

1 Answer


This was to access Tuolumne County Association of Realtors. I have since figured out the missing component to our URL request (dataset ID). This issue has been resolved. Thank you for your response.

djn1990's avatar
answered 2022-07-19 16:45:18 -0500
edit flag offensive 0 remove flag delete link



bwolven's avatar bwolven (2022-07-19 16:47:16 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer