Request Line
The request line is the top bar of the workspace. It contains the essential elements for defining and executing a request: the HTTP method, the target URL, and action buttons.
HTTP Method
The method dropdown on the left side of the URL input defines the type of HTTP operation. Select the method that matches your API's expected action.
| Method | Purpose | Has Body |
|---|---|---|
| GET | Retrieve data from the server. Should not modify server state. | Optional* |
| POST | Create a new resource or submit data for processing. | Yes |
| PUT | Replace an existing resource entirely with new data. | Yes |
| PATCH | Partially update an existing resource. | Yes |
| DELETE | Remove a resource from the server. | Optional* |
| HEAD | Same as GET but returns only headers, no body. Used to check if a resource exists. | Optional* |
| OPTIONS | Returns the HTTP methods supported by the server for a URL. Used for CORS preflight. | Optional* |
URL Input
The URL input accepts the full endpoint address. You can type, paste, or use environment variables.
Basic URL Format
https://api.example.com/users/123URL with Query Parameters
https://api.example.com/users?page=1&limit=10Query parameters added in the URL are automatically synced to the Params tab.
URL with Path Variables
https://api.example.com/users/:userId/posts/:postIdPath variables use colon prefix (:variableName). Values are defined in the Vars tab and replaced before sending.
URL with Environment Variables
{{baseUrl}}/users/{{userId}}Environment variables use double curly braces ({{variableName}}). Values are resolved from the active environment when sending.
Enter while the URL input is focused to send the request.Send Button
The Send button executes the request with the current configuration.
Before Sending
The following checks are performed before a request is sent:
- Path variables must have values (if URL contains
:paramsyntax) - If path variables are empty, you are redirected to the Vars tab with a warning
Save Button
The Save button (disk icon) stores the request configuration for later use. Saved requests appear in the Box section of the sidebar.
New Request
For requests not yet saved, clicking Save creates a new Box item. You will be prompted to enter a name.
Existing Request
For requests opened from Box, clicking Save updates the existing item with your changes. The button shows "Update" when there are unsaved modifications.
Project Endpoint
For requests opened from a Project, Save updates the endpoint definition in the project file.
More Actions
The three-dot menu on the right provides additional actions:
Import from cURL
Converts a cURL command into a Tigrister request. Useful when copying commands from documentation or browser DevTools.
Example cURL command:
curl -X POST https://api.example.com/users \
-H "Content-Type: application/json" \
-H "Authorization: Bearer token123" \
-d '{"name": "John"}'The following cURL options are supported:
-X, --request— HTTP method-H, --header— HTTP headers-d, --data— Request body-u, --user— Basic authentication-F, --form— Form data
Export as cURL
Generates a cURL command from the current request configuration. Useful for sharing requests or running them from a terminal.
The exported command includes the method, URL, headers, body, and authentication (excluding sensitive tokens that would need manual input).
Automatic cURL Detection
When you paste text starting with curl into the URL input, Tigrister automatically detects it and opens the Import modal. This allows quick import without using the menu.
Toggle Sidebar
The menu icon on the far left toggles the sidebar visibility. Hiding the sidebar gives more horizontal space for the request and response panels, which is useful on smaller screens or when you need to see more of the request/response content.