Request Overview

What is a Request?

A request in Tigrister represents a complete HTTP transaction configuration. It includes everything needed to communicate with an API endpoint: the target URL, HTTP method, headers, authentication, request body, and validation rules.

Each request lives in its own tab. You can have multiple tabs open simultaneously, each configured independently.

Request Structure

Every request consists of three main areas:

1. Request Line

The top bar where you define the core request parameters:

  • Method — HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS)
  • URL — The target endpoint address
  • Send — Executes the request
  • Save — Saves the request to Box for later use

2. Request Panel (Left)

Configuration tabs for request data:

Body— Request payload
Params— Query parameters
Vars— Path variables
Headers— HTTP headers
Auth— Authentication
Processors— Scripts & tests

3. Response Panel (Right)

Displays the server response after sending a request:

Body— Response content
Headers— Response headers
Cookies— Set-Cookie data
Detail— Timing & connection
Contract— Schema validation

Request Lifecycle

When you click Send, the request goes through these stages:

  1. Variable ResolutionEnvironment variables and path variables are replaced with their values
  2. Request PreparationHeaders are assembled, authentication is applied, body is serialized
  3. Pre-Script ExecutionIf configured, runs JavaScript before the request is sent
  4. Network ExecutionDNS lookup, TCP connection, TLS handshake (for HTTPS), data transfer
  5. Response ProcessingResponse is received, decompressed if needed, parsed
  6. Post-Script ExecutionIf configured, runs JavaScript after the response is received
  7. AssertionsIf configured, validates the response against defined rules
  8. History RecordingThe complete request/response is saved to history

Supported Protocols

Tigrister supports multiple communication protocols. The protocol is determined by the tab type:

HTTPDefault

REST APIs, standard web requests

WebSocket

Bidirectional real-time communication

GraphQL

Query language for APIs

SSE

Server-Sent Events for streaming

This guide focuses on HTTP requests. WebSocket, GraphQL, and SSE have their own dedicated panels with protocol-specific features.

Getting StartedRequest Line