Skip to main content
ComponentsEngine
Availability2014.1 or later
GermainUX can execute HTTP or HTTPS requests manually, on a schedule, or through an automated trigger.

Configure an HTTP Action

Single request to an endpoint

Configure an HTTP Scenario

Multi-step API request workflows

Configure Execution Notifications

Status alerts for requests

Validate the Configuration

Test before recurring runs

​
Requests can be configured as:

​
Configure an HTTP Action

Use an HTTP Action when GermainUX needs to execute one request against an endpoint.

​
Go to:

GermainUX Workspace -> Left Menu → Settings → Wizards -> HTTP Action
Configure the action, including:
  • Action name
  • URL and protocol
  • HTTP method
  • Headers
  • Query parameters
  • Request body, when applicable
  • Authentication or credential reference
  • Timeout
  • Expected response or success criteria
  • Monitoring Node and Engine
  • Manual, scheduled, or event-driven execution
Save and deploy the action when the configuration is complete.

​
Configure an HTTP Scenario

Use an HTTP Scenario when the workflow requires multiple requests—for example, authentication followed by one or more API transactions.

​
Go to:

GermainUX Workspace -> Left Menu → Settings -> Wizards -> HTTP Scenario Configure:
  • The scenario name and target application.
  • The Monitoring Node and Engine.
  • Each HTTP or HTTPS request in its execution order.
  • Authentication and credential references.
  • Values that must be passed between requests.
  • Response validations and failure conditions.
  • Optional SLA thresholds.
  • The execution schedule.
Save and deploy the scenario after testing its requests and dependencies.

​
Schedule Execution

An HTTP Action or Scenario can run:
  • Manually
  • At a specific time
  • At a recurring interval
  • In response to an SLA, rule, insight, or automation condition
See Configure a Time Interval. Select an Engine that can reach the target endpoint from the network location you want to test.

​
Configure Execution Notifications

Use the following options to receive status notifications: Enable both options during initial testing. In production, enable the notifications required by your operational policies.

​
Validate the Configuration

Before enabling recurring execution:

​
Get Help

Contact GermainUX Support

The Germain Team can help you set this up.

Can't find what you need?

Search all GermainUX docs with Ctrl + K, or use the feedback buttons at the bottom of this page to tell us what is missing.

The content of this document is proprietary to GERMAIN SOFTWARE LLC.