Skip to main content
HTTP commands enable you to make HTTP/HTTPS requests to APIs and web services. These commands are essential for fetching data from REST APIs, web services, and other HTTP-based endpoints. HTTP commands run in HTTP steps.

Available Commands

HTTP Request

Single request with Cloudflare handling (ID 1001)

HTTP Parallel Request

Parallel requests with Cloudflare handling (ID 1002)

HTTP Request - Got

Single request with HTTP/2, proxy and TLS options (ID 1003)

HTTP Parallel Request - Got

Parallel requests with the Got client (ID 1004)

HTTP Request - Got Scraping

Single request with browser-like headers and TLS (ID 100)

Common Use Cases

  • API Integration: Fetch data from REST APIs
  • Web Scraping: Retrieve HTML content from web pages
  • Data Synchronization: Pull data from external services
  • Authentication: Call login or token endpoints and reuse the result in later steps

Common Parameters

Every HTTP command requires these parameters:
Use verb, not method. Projects with HTTP commands missing url, verb, contentType or timeout are rejected on save.

Placeholders

HTTP commands resolve ${name} placeholders from item state and local variables in URLs, headers and bodies:
See Placeholders for where values come from.

Best Practices

  • Keep credentials out of logs: Fetch tokens in an earlier step or command and reference them with placeholders instead of hard-coding them
  • Set Appropriate Timeouts: Configure timeouts based on expected response times, within the step interval
  • Validate Responses: Add a Validation command before parsing