HTTP Request & Standalone Components

​

1. Node Types & Creation

• Collection-Bound Endpoints: Dragged directly from your imported OpenAPI/Swagger specifications in the left sidebar. Retains schema definitions and validation contracts.
• Standalone HTTP Request ([ ⚡ qComponent ]): Placed from the component palette. Operates independently without requiring a parent OpenAPI specification.

• GET: #61affe (Blue)
• POST: #49cc90 (Green)
• PUT: #fca130 (Orange)
• DELETE: #f93e3e (Red)
• PATCH: #50e3c2 (Teal)

​

2. Unified Request Bar

1. HTTP Method Selector: Switch between GET, POST, PUT, DELETE, PATCH, OPTIONS, and HEAD.
2. Endpoint URL Input: Supports dynamic variables and path parameter syntax (e.g. https://api.acme.com/v1/users/{userId}).
3. Save & Test Actions: Save node settings or perform immediate test execution to verify credentials.

​

3. Path Parameters & Bidirectional Auto-Sync

• Typing {petId} into the URL input automatically creates a corresponding row in the Params tab with Location = path.
• Renaming or removing the placeholder updates the URL and params table bidirectionally without manual coordination.
• The backend execution engine substitutes {petId} at runtime using mapped variables or predecessor bindings:

https://api.store.com/v2/orders/{{CreateOrder.response.body.orderId}}/status

​

4. Comprehensive Authorization Engine

​

5. Body Payloads & Dynamic Template Bindings

• JSON: Syntax-highlighted Monaco editor with dynamic variable completion.
• x-www-form-urlencoded: Form key-value editor.
• multipart/form-data: File upload attachments and binary buffers.
• Raw / Text: Plain text or XML payloads.

{
  "orderId": "{{OrderStep.response.body.id}}",
  "customerEmail": "{{env.TEST_USER_EMAIL}}",
  "timestamp": "{{$isoTimestamp}}"
}