# Retrieve the Historical Analysis of a TOE
source: https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/historical-analysis/index.md

## Overview {#overview}

The `GET Historical Analysis` endpoint retrieves the overall rating, security domain ratings, security criteria ratings, and trending data for historical analysis. Analyses from scans prior to the current scan is termed as historical analysis.

You must provide the `toe_id` in the API request to retrieve the historical analysis of a vendor.

A graphical representation of the overall rating trend over time can be seen in **Overview** tab of the vendor's page on the **RiskRecon web portal**. Hover your mouse pointer on the graph and be guided by a black dot, which represents a scan on a particular date, to find the overall score summary change from the scan.

Click a particular point on the graph to view the overall score summary change, and rating change of the security domains and criteria.

![](https://static.developer.mastercard.com/content/riskrecon-api/uploads/historical-analysis.png)

## Sequence Diagram {#sequence-diagram}

The following diagram shows how to retrieve the historical analysis of a TOE:
Diagram retrieve-historical-analysis

## Execution Steps {#execution-steps}

The following steps describe a sample integration flow to retrieve the historical analysis of a TOE:

1. The user sends a `GET` request to retrieve historical analysis and provides the `toe_id` as the input parameter.
2. RiskRecon provides the the historical analysis of the requested TOE.

## Sample Request and Response {#sample-request-and-response}

For a sample request and response of this API, see [Get the Historical Analysis of a TOE](https://developer.mastercard.com/riskrecon-api/documentation/testing/analysis-samples/hist-analysis-smpl/index.md).

## Use Case Examples {#use-case-examples}

The use cases in this section discuss how you can use the `GET Historical Analysis` endpoint to retrieve the historical analysis of a TOE:

* [Tracking vendor rating over time](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/historical-analysis/index.md#tracking-vendor-rating-over-time)
* [Determining the security risk posture while vetting potential vendors](https://developer.mastercard.com/riskrecon-api/documentation/use-cases/risk-assessment/analysis/historical-analysis/index.md#determining-the-security-risk-posture-while-vetting-potential-vendors)

### Tracking vendor rating over time {#tracking-vendor-rating-over-time}

A vendor has been operating with an old version of a software for more than a year. Besides, several other issues too have been detected overtime within the vendor's systems. The customer has shared an action plan with the vendor who is working to resolve the issues. The customer wants to do a quick check to understand if the ratings have improved and uses the `GET Historical Analysis` endpoint to check on the trend and ratings. Based on the ratings and trend returned by the endpoint, the customer can decide whether to continue business with the vendor.

### Determining the security risk posture while vetting potential vendors {#determining-the-security-risk-posture-while-vetting-potential-vendors}

A RiskRecon customer is vetting a vendor and needs to know the vendor's security risk posture. The customer has used the `GET TOE` and the `GET Findings` endpoint to retrieve the list of all the vendor's current risks. Further, the customer uses the `GET Current Analysis` endpoint to know the current security domain and criteria ratings, and trend. The customer also uses the `GET Historical Analysis` to find out the vendor's risk posture trend for the past one year. The customer then compares the two analyses to understand the vendor's overall risk posture and if the vendor has improved their ratings. The insights thus received helps the customer to better evaluate if they should do business with that vendor and take on the potential risks.

## Endpoint {#endpoint}


API Reference: `GET /v1/analysis/history/{toe_id}`