Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.testbrick.com/llms.txt

Use this file to discover all available pages before exploring further.

API Request Blocks

API request blocks make HTTP requests to your API endpoints. Each block can be configured with a method, URL, headers, body, and authentication.

Adding a block

Click API in the toolbar to add a new request block. It automatically connects to the last block in your flow. Click the block on the canvas to open the side panel where you configure everything. Request block with side panel

Method & URL

Select the HTTP method and enter the URL:
  • GET — fetch data
  • POST — create data
  • PUT — replace data
  • PATCH — update data
  • DELETE — remove data
URLs support environment variables: {{baseUrl}}/users Method and URL bar

Headers

Add request headers as key-value pairs. Click + Add Header to add more. Common headers are auto-detected:
  • Content-Type: application/json is set automatically when you have a JSON body
Header values support variables: Bearer {{token}} Headers configuration

Body

For POST, PUT, and PATCH requests, enter the request body. JSON is the default format.
{
  "email": "{{testEmail}}",
  "name": "John Doe",
  "role": "admin"
}
The body field supports variable autocomplete — type {{ to see available data. Body editor with autocomplete

Authentication

The Auth tab supports three types:
TypeFieldsExample
Bearer TokenToken value{{authToken}}
API KeyHeader name + valueX-API-Key: {{apiKey}}
Basic AuthUsername + passwordStandard HTTP basic auth
Auth values support variables — reference tokens from previous blocks. Auth tab

Block title

Give your block a descriptive name (optional). It shows on the canvas above the method and URL, making complex flows easier to read. Block with title
Good block names: “Create User”, “Login”, “Verify OTP”, “Get Profile”. These make the flow self-documenting.

Running a single block

Click Send in the side panel to run just that block. The response appears in the Response tab immediately. This is useful for testing individual requests before running the full flow. Response tab