Overview

error logs api the error logs api allows you to programmatically view failed api requests to understand what is causing them to fail inspecting error logs can be useful to determine whether the cause of an api request failure relates to the api request itself or the host website being down or experiencing technical difficulties you can use the error logs api in combination with the rainforest api status page https //rainforestapi statuspage io/ to inspect any open platform issues you may also use the account api https //docs trajectdata com/rainforestapi/account api to view live updates on any open api issues that may be causing requests to fail which requests are shown in the error logs api? real time requests to the main api that result in an http 500 response code https //docs trajectdata com/rainforestapi/response codes are shown in the error logs api requests run via collections, or requests that result in any other http response code https //docs trajectdata com/rainforestapi/response codes are not for example, an http 400 that indicates an error in your request parameters, would not be shown in the error logs api error log retention error logs are retained, and available via the error logs api and rainforest api dashboard https //app rainforestapi com/errorlogs , for 3 days from the time that they last occurred if the same request is retried and results in another error then the error log entry will increment its' count property to show the number of occurrances of that same error and the 3 day timer will reset in addition to programmatic access to error logs via the error logs api you can also view error logs visually, in the rainforest api dashboard https //app rainforestapi com/errorlogs you can also request email updates when new error logs occur via the rainforest api dashboard https //app rainforestapi com/errorlogs next steps list error logs https //docs trajectdata com/rainforestapi/errorlogs api/list