---
alias: user-guide-business-workflow-task-call-http-endpoint
render_macros: false
description: "Sends one HTTP request through the existing client factory."
---

# Call HTTP Endpoint

Sends one HTTP request through the existing client factory.

![Screenshot of a Business Workflow mapping Material records, composing JSON, and posting the payload to an HTTP endpoint.](images/business-workflow-task-call-http-endpoint.png)

## Inputs

Set `Endpoint`, `Method`, `RelativePath`, `Body`, `TimeoutMilliseconds`, `UsernameConfigPath`, `PasswordConfigPath`, `BearerTokenConfigPath` in the task details. Use the value editor to select compatible results from earlier tasks.

### Named Input Rows

Use the **+** button in **Inputs** to add one row per HTTP header. Enter its exact name, select its type, and enter a value or select an earlier result. Keep the fixed inputs. Additional names must be unique and different from the fixed input names.

See [Named Input Rows](../../../business_workflow_task.md#named-input-rows) for a worked example.

## Settings

Configure `RaiseError` in the task settings.

## Outputs

Use `IsSuccess`, `StatusCode`, `ResponseHeaders`, `ResponseBody`, `FailureKind` in subsequent tasks.

??? example "Call HTTP Endpoint"

    Enter the endpoint base address, choose POST, set `RelativePath` to `orders`, and connect Compose JSON's `Utf8` result as `Body`. Add a String input row named `X-Workflow-Test` with value `inspection`. Inspect `IsSuccess`, `StatusCode`, `ResponseBody`, and `FailureKind`; choose the error setting deliberately.

## Behavior

A String header row supplies one value. A String array from an earlier task can supply several values. Set `RaiseError` to choose whether a failed call raises an error or returns failure details. Store authentication values in configuration and select their paths.