Skip to main content
LiteClient provides a comprehensive interface for building HTTP requests with full control over methods, URLs, parameters, headers, and body content.

​
Request Methods

LiteClient supports all standard HTTP methods:
  • GET - Retrieve resources
  • POST - Create new resources
  • PUT - Replace existing resources
  • PATCH - Partially update resources
  • DELETE - Remove resources
  • HEAD - Retrieve headers only
  • OPTIONS - Query supported methods
Select your method from the dropdown next to the URL bar.

​
URL & Query Parameters

​
URL Input

Enter your full URL in the URL bar. The URL supports variable substitution using the {{variableName}} syntax: 
{{baseUrl}}/api/v1/users/{{userId}}
Type {{ to trigger autocomplete and see all available variables from your global, collection, and environment scopes.

​
Query Parameters Editor

Manage query parameters with a dedicated key-value editor:
1

Add Parameter

Click Add Parameter to create a new query parameter row.
2

Enter Key and Value

Type the parameter name and value. Both support variable substitution.
3

Toggle Individual Parameters

Use the checkbox to enable or disable individual parameters without deleting them.
Example: 
Key: page    Value: 1
Key: limit   Value: {{pageSize}}
Key: sort    Value: created_at
This generates: ?page=1&limit=50&sort=created_at

​
Headers

Customize request headers with full control over keys and values.

​
Adding Headers

  1. Navigate to the Headers tab
  2. Click Add Header
  3. Enter the header key and value
  4. Both key and value support variable substitution

​
Common Headers Example

Content-Type: application/json
Accept: application/json
X-API-Key: {{apiKey}}
User-Agent: LiteClient/1.0
Authentication headers (like Authorization) can be set automatically using the Auth tab. See the Authentication page for details.

​
Request Body

Configure request bodies with multiple content types:

​
No Body

Select No Body for GET and HEAD requests that don’t send a request body.

​
Raw Body

The raw body editor supports multiple content types with syntax highlighting: 
{
  "name": "{{userName}}",
  "email": "[email protected]",
  "role": "admin"
}
Includes automatic syntax highlighting and validation.

​
Form Data

Upload files and send multipart form data:
1

Select Form Data

Choose Form Data from the body type dropdown.
2

Add Fields

Add key-value pairs for text fields and file uploads.
3

Upload Files

Click the file icon next to a field to select a file for upload (25MB limit).
Example use case: 
Key: title       Value: Profile Picture
Key: image       Value: [Select File: avatar.jpg]
Key: category    Value: {{imageCategory}}
Form-data file uploads have a 25MB size limit. For larger files, consider using a dedicated file upload API.

​
URL-Encoded Form Data

Send form data as application/x-www-form-urlencoded: 
Key: username    Value: {{userName}}
Key: password    Value: {{userPassword}}
Key: remember    Value: true
This sends: username=john&password=secret&remember=true

​
Variable Substitution

Variables work in all body types:
  • Raw JSON/XML/HTML - Use {{variableName}} anywhere in the content
  • Form Data - Both keys and values support variables
  • URL-Encoded - Keys and values support variables
Variable resolution follows the layered precedence: Environment → Collection → Global. Only enabled variables are resolved.

​
Sending Requests

Once you’ve configured your request:
1

Click Send

Click the Send button in the URL bar to execute the request.
2

View Response

The response appears in the bottom panel with status, headers, body, and cookies.
3

Cancel If Needed

Click Cancel during long-running operations to abort the request.

​
Request Execution Flow

When you send a request, LiteClient:
  1. Runs pre-request scripts (if configured)
  2. Resolves all variables (globals → collection → environment)
  3. Substitutes variables in URL, headers, body, and auth
  4. Sends relevant cookies based on domain
  5. Executes the HTTP request
  6. Captures the response
  7. Runs post-response scripts (if configured)
  8. Records the request in history
Pre-request and post-response scripts can modify variables and perform assertions. See the Scripting page for details.

​
Multi-Tab Editing

Work on multiple requests simultaneously:
  • Open multiple request panels at once
  • Drag tabs to reorder
  • Unsaved changes indicator (dot) shows when modifications haven’t been saved
  • Each tab maintains independent state
Save frequently used requests to collections so you can quickly open them later from the sidebar.

​
Best Practices

Replace hardcoded values like API keys, user IDs, and base URLs with variables. This makes requests reusable across environments.
Use the enable/disable toggle for headers and parameters instead of deleting them. This preserves your configuration for future testing.
When saving requests to collections, use clear names that describe what the request does: “Create User”, “Get Order by ID”, “Delete Product”.
Some APIs accept multiple content types. Save separate requests for JSON and XML variants to test both formats.