> ## Documentation Index
> Fetch the complete documentation index at: https://docs.driv.ly/llms.txt
> Use this file to discover all available pages before exploring further.

# Retrieve Historical Photo

> Retrieving a Specific Photo

**Description**:\
Retrieves a single historical photo by its index. The `index` is typically a numeric identifier (e.g., `1`, `2`) corresponding to the order in which images were returned for that VIN.

**Example Request**:

```http theme={null}
GET https://historical.photos.vin/1HGCM82633A004352-1.jpg
```

**Successful Response**:

* Returns the requested image file (e.g., JPEG).
* Response includes `Content-Type: image/jpeg`.
* May include caching headers such as `Cache-Control` to improve performance.

**Error Case**:\
If the requested image doesn’t exist, a `404 Not Found` response is returned. Ensure your integration handles such cases gracefully.

***

## Workflow Summary

1. **List Available Images**: Fetch the VIN endpoint to get a list of image URLs.
2. **Fetch a Specific Image**: Use one of the returned URLs to retrieve the actual image file.

***

## Getting Started

* **Integration**: To integrate with your frontend, fetch and cache images from a server-side service using your Drivly credentials.
* **Authentication**: If you do not have Drivly credentials, please [reach out](https://drivly.typeform.com/applyforaccess?typeform-source=docs.driv.ly) to our team.
* **Caching**: Leverage caching headers to reduce load times and bandwidth usage.
* **Error Handling**: Implement robust error handling for non-existent VINs or indices.