Request Logs

The request logs page provides a detailed history of all your API requests, essential for debugging and monitoring your integration.

Accessing Logs

Navigate to /dashboard/logs in your dashboard.

Filtering

Filter your requests by:

Request Cards

Each request is displayed as an expandable card showing:

• Status - Success or error indicator
• Timestamp - When the request was made
• Response time - How long the request took
• URL - The target URL that was captured
• Format - PNG, JPEG, or WebP
• Viewport - Dimensions used for capture
• API Key - Which key was used (masked for security)

Click any card to expand and see full details.

Expanded Details

The expanded view shows:

Request Information

Request Options

• Viewport - Width, height, and scale factor
• Wait - Wait conditions (load, networkidle, delay)
• Block - Content blocking settings (ads, trackers, cookie banners)
• Full page - Whether full page capture was enabled
• Cached - Whether the response was served from cache

Response Details

For successful requests:

• Format - Output image format
• Dimensions - Actual image width and height
• Size - File size in human-readable format
• Response time - Total processing time
• Credits used - Credits consumed

For failed requests, the error message is displayed.

Screenshot Preview

Successful requests show a thumbnail preview of the captured screenshot with options to:

• Open Full Size - View the full screenshot in a new tab
• Copy URL - Copy the CDN URL to clipboard

Raw Request/Response JSON

The collapsible "Raw Request/Response" section shows the exact JSON data for debugging. This is invaluable for:

• Verifying your request parameters are correct
• Understanding what the API actually received
• Debugging unexpected results
• Sharing details with support

Request JSON

Shows the exact parameters sent to the API:

{
  "url": "https://example.com",
  "viewport": {
    "width": 1200,
    "height": 630
  },
  "output": {
    "format": "png"
  },
  "cache": {
    "ttl": 86400
  }
}

Note: Sensitive content like raw HTML or Markdown is not stored for security reasons.

Response JSON

Shows the API response in the same format returned by the API:

{
  "id": "req_abc123def456",
  "status": "completed",
  "image": {
    "url": "https://cdn.renderscreenshot.com/screenshots/abc123.png",
    "width": 1200,
    "height": 630,
    "size": 34567,
    "format": "png"
  },
  "cache": {
    "hit": false,
    "key": "screenshots/abc123.png",
    "url": "https://cdn.renderscreenshot.com/screenshots/abc123.png",
    "expires_at": "2026-01-26T15:30:00Z"
  }
}

Understanding Cache Expiration

The cache.expires_at field shows when the cached screenshot will expire:

• Calculated from request time + cache TTL
• Default TTL is 24 hours (86,400 seconds)
• Custom TTL can be set via cache.ttl parameter (1 hour to 30 days)

This helps you understand:

• When a cached screenshot will be refreshed
• Why you might be seeing stale content
• When to use cache.refresh: true to force a new capture

Error Response JSON

For failed requests, the response shows error details:

{
  "error": {
    "type": "target_error",
    "code": "screenshot_failed",
    "message": "Page load timeout after 30000ms",
    "retryable": true
  },
  "request_id": "req_abc123def456"
}

Copy Buttons

Each JSON block has a Copy button to quickly copy the full JSON to your clipboard. Use this for:

• Pasting into support tickets
• Comparing with your application logs
• Debugging in your development environment

Tips for Debugging

1. Check the Request JSON - Verify your parameters match what you intended to send
2. Compare timestamps - Correlate with your application logs
3. Look at cache.expires_at - Understand if you're seeing cached content
4. Check error.retryable - Know if you should retry failed requests
5. Use Request ID - Reference the req_ ID when contacting support