Nestoria API - version 1.18 - response status handling
Hello, Nestovelopers,We have some good news - the version 1.18 of Nestoria API is out! I grant you that a release version number reaching the age of majority might not provoke universal excitement, but we believe we have added a few handy features in the 1.18 release (for the full history, check Nestoria API - Version History).The notable additions in the 1.18 version of Nestoria API are two response fields that return API response status:
- "application_status_code"; and
- "application_status_text".
You can find more details about response field implementation in the Nestoria API - Return Codes page.
As a result, the requests made through Nestoria API can get similar level of status feedback as provided by our native code. The improved response status reporting should help developers handle request exceptions, making it easier to develop cool applications that use API to access Nestoria property listings and average house prices.
For example, applications using Nestoria API to request listings by location will now receive notification of misspelled, ambiguous or unknown locations. This will allow applications using our API to present meaningful status updates to their user and carry out appropriate compensating actions. Moreover, if the location search via Nestoria API does return listings, developers could persist unique listing IDs locally, and then use the response codes added in 1.18 iteration to check if the given unique listing IDs are still available for retrieval.Of course, the work on APIs is never done. We’ll make sure to let you know when we release the next iteration and we'd love to hear any feedback you have.
