# HTTP Request (API)
## Description **What it does:** This node enhances your workflows by allowing you to connect to external APIs (Application Programming Interfaces). Think of APIs as bridges connecting different software systems. **When to use it?** If your workflow needs to connect with other web services, like retrieving info from a website, the HTTP Request node helps integrate it seamlessly. ## Component settings | Parameter Name | Description | | -------------- | -------------------------------------------------------------------------------------------------------------------------- | | Method |

Choose the method


Options:

| | URL | Input the URL (Endpoint Link) | | Header |

Input the header of API, including:

| | Parameters |

Input the Parameter of API, including:

| | Payload (Body) |

Input the Payload of API, including:

| ## Advanced configurations **Failure handling strategy** lets you decide what happens if your HTTP Request runs into a problem.
You’ve got a few options: * **Stop flow** – If something goes wrong, the workflow stops right here. * **Skip** – If this request fails, just move on and keep the workflow going. * **Retry** – Give it another shot! You can set how many times to retry and how long to wait between each try. * Max retry attempts: * Min: 1 * Max: 3 * Delay between retries (seconds): * Min: 1 * Max: 5 If all retries fail, the flow will stop at this HTTP Request node. ## Example **Input**
**Output**