Backend HTTP Request Node
| Description | The Backend - HTTP Request node allows sending HTTP requests directly from the backend, instead of the frontend. This ensures that integrations with external services are handled securely and are not exposed to the client side. |
| Available in | Authentication, Admin, Self Service, API, Consent, Library, Custom, User Defined |
| Node Name | Backend - HTTP Request |
API Configurations
This section defines the parameters for the HTTP request sent by the node.
API Method / URL
#### API Method Specifies the **HTTP method** used for the request (GET, POST, PUT, PATCH, DELETE). #### Follow Redirects When enabled, the request will automatically **follow HTTP redirects** returned by the server. #### API URL Defines the **endpoint URL** of the internal or external service that will be called.API Headers
Allows you to define custom **HTTP headers** to include in the request. These headers are sent together with the HTTP request.API Data
The API Data section defines the **body of the HTTP request**, providing the data that will be sent to the external service as part of the request body. It is used when the selected HTTP method supports a request payload (POST, PUT, PATCH).CA Certificate
The CA Certificate field allows specifying a **trusted Certificate Authority (CA) certificate** to validate the SSL/TLS connection when making HTTPS requests. This ensures that the remote server's certificate is trusted and the connection is secure. #### Skip Certificate Validation This option allows skipping the SSL/TLS certificate validation. When enabled, the system will accept any certificate presented by the server, even if it is self-signed or invalid.Save in the Flow store
Attributes from the HTTP response can be saved **into a variable** for reuse by other nodes. See [Common Configurations]({filename}/pages/io/io-nodes/io-node-types/common-configurations.md#save-in-the-flow-store) for details.Default Output Node
- Success
- Failure
