# Documentation for Test, Monitor, and Visualize Geospatial APIs 1.0.0

This documentation is for version 1.0.0, which is no longer actively maintained.

For up-to-date documentation, see the [latest version](/content/docs/desktop/history/index.html) (1.1.0).

## Accessing Request History

1. **Click** the ** History icon in the left sidebar
2. The history panel will display a table of all your previous requests
3. **View** requests in chronological order (newest first)

## History Table Overview

The history table contains the following columns:

### Open Action
- **Icon**: Click to load the request back into the API testing interface
- **Functionality**: Restores all request parameters, headers, and body content
- **Use case**: Quickly repeat or modify a previous request

### URL
- **Display**: Shows the full endpoint URL that was tested

### Method
- **Values**: GET, POST, PUT, PATCH, DELETE
- **Quick identification**: Easily see what type of request was made

### Date
- **Format**: MM/DD/YYYY format
- **Chronological** order (newest first)

### Time
- **Format**: HH:MM AM/PM format

### Status
- **HTTP codes**: 200, 404, 500, etc.
- **Quick assessment**: Instantly see which requests succeeded or failed

## Using History Effectively

### Rerunning Previous Requests
1. **Locate** the request you want to repeat in the history table
2. **Click** the 🔗 open icon in the first column
3. The request will be loaded into the API interface with:
   - Original URL
   - HTTP method
   - Service type
   - All query parameters
   - Headers
   - Request body (if applicable)
4. **Modify** any parameters as needed
5. **Click** Send to execute the updated request

### Analyzing Request Patterns
#### Success Rate Analysis
- **Scan** the Status column for patterns
- **Identify** frequently failing endpoints
- **Track** improvements after API fixes
- **Monitor** service stability over time

#### Performance Tracking
- **Review** response times for similar requests
- **Compare** performance across different time periods
- **Identify** performance bottlenecks
- **Track** API optimization results

#### Usage Patterns
- **See** which endpoints you test most frequently
- **Identify** common parameter combinations
- **Track** your testing workflow evolution
- **Plan** future testing strategies

## History Management

### Automatic Logging
Quetzly automatically logs:
- **All sent requests**: Every request you execute
- **Request details**: Complete parameter and header information
- **Response metadata**: Status codes, timing, and size information
- **Timestamps**: Precise timing for each request

### Data Persistence
- **Local storage**: History is stored locally on your machine
- **Session persistence**: History survives application restarts

### History Limitations
- **Storage capacity**: History has a practical limit based on available disk space