Skip to main content

History

Keep track of all your API requests with Quetzly Validator's history feature. The history system automatically logs every request you make, providing valuable insights into your testing patterns and making it easy to repeat or modify previous tests.

Accessing Request History​

  1. Click the history 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 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)
  • Navigation: Quickly find requests from specific time periods

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
  • Service types: What type of service was tested

Data Persistence​

  • Local storage: History is stored locally on your machine
  • Session persistence: History survives application restarts
  • Privacy: No request data is sent to external servers
  • Security: Sensitive data remains on your local system

History Limitations​

  • Storage capacity: History has a practical limit based on available disk space
  • Performance: Very large histories may affect application performance