---
title: HTTP Request
description: Call an external API or service and pass the response back into your workflow.
source: https://www.edgaze.ai/docs/builder/nodes/http-request
section: builder
---
# HTTP Request

> Call an external API or service and pass the response back into your workflow.

## Overview

HTTP Request makes a network call from inside your workflow , fetch public data, send structured payloads, or integrate with another system.

It is safe by default with host allowlists and denylists, HTTPS expectations, and optional idempotency for write-style requests.

```docsgraph
http-request
```

## Ports

- **Input , Request:** Optional upstream payload , a URL string or an object with url, headers, and body.
- **Output , Response:** The response data returned to downstream blocks.

## Inspector

- **URL:** Endpoint when nothing is connected, or as fallback alongside connected input.
- **Method:** GET, POST, PUT, PATCH, or DELETE.
- **Allowed Hosts:** Comma-separated allowlist , when set, only those domains are permitted.
- **Denied Hosts:** Comma-separated blocklist for unsafe or internal targets.
- **Require idempotency:** Enable for retry-safe POST, PUT, or PATCH writes.
- **Idempotency key:** Stable key required when idempotency is on.
- **Follow Redirects:** Whether to follow HTTP redirects.

## Tips

- Prefer HTTPS public endpoints and restrict hosts when you know the target domains.
- Treat POST, PUT, and PATCH carefully , enable idempotency when retries could duplicate writes.
- Connect a structured object upstream when headers or body vary per run.
- Test with realistic payloads before you publish.

## Related

- [Workflow Studio](/docs/builder/workflow-studio)