xpay✦ HTTP icon

xpay✦ HTTP

Make HTTP requests with automatic 402 payment handling and policy enforcement

xpay✦ HTTP

AI-generated

Summary

Execute an HTTP request to a specified URL using the chosen HTTP method, supporting multiple authentication methods and flexible request configuration, with automatic handling of payment-required (HTTP 402) responses through the xPay Smart Proxy.

Inputs

  • method — The HTTP method to use (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS). Defaults to GET.
  • url (required) — The target URL to which the HTTP request is sent.
  • authentication — Authentication method for the request: None, API Key, Bearer Token, or Basic Auth.
  • apiKeyName — Name of the API key header or query parameter (shown if API Key authentication selected). Defaults to 'X-API-Key'.
  • apiKeyValue — Value of the API key (shown if API Key authentication selected).
  • apiKeyLocation — Where to send the API key: header or query parameter (shown if API Key authentication selected). Defaults to header.
  • bearerToken — Bearer token for Authorization header (shown if Bearer Token authentication selected).
  • basicUsername — Username for Basic authentication (shown if Basic Auth selected).
  • basicPassword — Password for Basic authentication (shown if Basic Auth selected).
  • headers — Additional HTTP headers to include in the request, specified as name/value pairs.
  • queryParameters — Additional query parameters to include in the request URL as name/value pairs.
  • bodyContentType — Content type of the request body when using POST, PUT, or PATCH: None, JSON, Form Data, Form URL Encoded, or Raw. Defaults to JSON.
  • bodyJson — JSON body to send with the request when bodyContentType is JSON.
  • bodyRaw — Raw body text to send with the request when bodyContentType is Raw.
  • formData — Form fields to include as key/value pairs when bodyContentType is Form Data or Form URL Encoded.
  • paymentSettings — Payment handling options including auto-pay on HTTP 402 responses, maximum payment allowed per request, and whether to fail if payment limits are exceeded.
  • options — Additional request options such as timeout (seconds), retry count on failure, SSL error ignoring, redirect following, and whether to return full response including headers and status code.

Output shape

a list of items each containing the response body as JSON merged with payment and policy info, or the full HTTP response including headers and status code if requested

Request is proxied through the xPay Smart Proxy which handles payment-required (HTTP 402) responses automatically according to payment settings. If fullResponse is false, the node outputs the response body with an _xpay property holding payment and policy metadata. If fullResponse is true, the full HTTP response structure is returned. Errors can cause workflow failure or be output per item if 'continue on fail' is enabled.

Links

Discussion