Skip to content

Requests

Configure HTTP request settings for t-req.

This page covers configuration options for HTTP requests. For usage documentation, see HTTP Mode.

Configure default HTTP request behavior in your treq.json config file.


Configuration

treq.json
{
"requests": {
"timeout": 30000,
"verify_ssl": true,
"cookies": {
"auto_capture": true,
"send_from_jar": true
},
"history_retention": "forever",
"history_content": {
"request_headers": true,
"request_body": true,
"response_headers": true,
"response_body": true,
"cookies": false,
"test_results": true,
"hook_results": false
},
"redaction": {
"enabled": true,
"patterns": ["password", "secret", "token", "api_key"],
"placeholder": "[REDACTED]"
}
}
}

Available Options

OptionTypeDefaultDescription
timeoutnumber30000Request timeout in milliseconds
verify_sslbooleantrueVerify SSL certificates
cookies.auto_capturebooleantrueAutomatically capture cookies from responses
cookies.send_from_jarbooleantrueSend cookies from the cookie jar with requests
history_retentionstring"forever"How long to retain request history. Options: "forever", "30days", "7days", "session"
history_contentobjectsee belowConfigure which data to save in history
redactionobjectsee belowConfigure sensitive data redaction

History Content Options

Control which parts of requests and responses are saved to history.

OptionTypeDefaultDescription
request_headersbooleantrueSave request headers
request_bodybooleantrueSave request body
response_headersbooleantrueSave response headers
response_bodybooleantrueSave response body preview
cookiesbooleanfalseSave captured cookies
test_resultsbooleantrueSave test execution results
hook_resultsbooleanfalseSave hook execution results

Redaction Options

Automatically redact sensitive data before saving to history. This helps keep secrets out of your history files while still making requests accessible to agents.

OptionTypeDefaultDescription
enabledbooleantrueEnable sensitive data redaction
patternsstring[]see belowKeywords to match for redaction (case-insensitive)
custom_patternsstring[][]Additional regex patterns for redaction
placeholderstring"[REDACTED]"Text to replace redacted values with

Default redaction patterns: password, secret, token, api_key, apikey, api-key, authorization, bearer, access_token, accessToken, refresh_token, refreshToken, private_key, privateKey, credential


Configuration Precedence

Settings are applied in this order (later overrides earlier):

  1. Hardcoded defaults - Built-in values
  2. treq.json config - Your requests settings
  3. CLI arguments - Command-line overrides (e.g., --timeout)
  4. Request-specific - Per-request settings in TUI

Examples

Disable SSL verification for development:

treq.json
{
"requests": {
"verify_ssl": false
}
}

Short timeout with session-only history:

treq.json
{
"requests": {
"timeout": 5000,
"history_retention": "session"
}
}

Disable automatic cookie handling:

treq.json
{
"requests": {
"cookies": {
"auto_capture": false,
"send_from_jar": false
}
}
}

Redact custom API keys and JWT tokens:

treq.json
{
"requests": {
"redaction": {
"enabled": true,
"patterns": ["accessCode", "secretKey", "apiToken"],
"custom_patterns": [
"sk-[a-zA-Z0-9]{48}",
"eyJ[a-zA-Z0-9_-]*\\.[a-zA-Z0-9_-]*\\.[a-zA-Z0-9_-]*"
],
"placeholder": "[REDACTED]"
}
}
}

Save minimal history (exclude headers and body):

treq.json
{
"requests": {
"history_content": {
"request_headers": false,
"request_body": false,
"response_headers": false,
"response_body": false
}
}
}

Save full history including cookies and hooks:

treq.json
{
"requests": {
"history_content": {
"cookies": true,
"hook_results": true
}
}
}