RESO Endpoints Error Reponses

Owned by Natan Y.
Last updated: Sept 01, 2023
1 min read

As the RESO standard adheres to the OData protocol, all error responses should follow the corresponding standard. Here is the response body format based on this standard: http://docs.oasis-open.org/odata/odata-json-format/v4.0/errata03/os/odata-json-format-v4.0-errata03-os-complete.html#_Toc453766668

  • Response Codes:

Error Code

Error Name

Description

Sample Request

Error Code

Error Name

Description

Sample Request

400

Bad Request

Authorization and Authentication are OK but the request cannot be handled by server.

reso/odata/Property?$filt= ListingId eq 'FHR20231663'
- error message: $filt is not supported.

401

Unauthorized

Access to the endpoint without a valid access token

 

403

Forbidden

api-key is wrong or no access to the feed

 

404

Not Found

access to a resource that does not exist or is not available

reso/odata/Prop?$filter=field eq value
- error message: Prop is not valid

429

Quota Exceeded

Indicates too many attempts in the past minute or hour

 

500

Server Error

Indicates an error in Server

 

504

Gateway Timeout

Indicates that the query took too long to process