Define the Receiving System Request

We can start defining the receiving systems request using the Receiving System API specification.

The Receiving System API specification will define details like the Context Name, Method, and Content Type to be used for the request. This definition can be different depending on the connector protocol. For more information, go to APIs and Connectors for more details.

When variables are included in the context name, refer to the section on URL Path Variables 

Remove namespace

The “remove namespace” checkbox will remove namespace references from an outbound orchestration XML request. For instance, the payload will undergo transformation as illustrated below: 

<ns:root xmlns:ns=””> 

Transformed to:


In the original payload, the elements (root, element1, element2, element3) are prefixed with the namespace ns defined in the XML namespace declaration xmlns:ns="". This namespace declaration associates the ns prefix with the namespace URI "".

In the transformed payload, the namespace prefix ns has been removed from all the element names. This transformation effectively removes the namespace from the XML structure, resulting in simpler element names (root, element1, element2, element3) without any namespace prefix.


A timeout can be set on each orchestration request. By default, a connector timeout is set to 60sec. Should you wish to specify a timeout for this specific request, a millisecond timeout can be set here.

Change Request To

The “Change Request To” dropdown offers three options for modifying the request sent to the receiving system:

  • Don’t Change: Sends the request according to the request template/parameter configuration.
  • Pass Source Request: Passes through the incoming API request payload.
  • Pass Saved Responses: Allows you to pass a saved response from a previous orchestration where it has been saved under ‘Save Response As’. In the image below, the WalletResponse has been saved:

You could then reference WalletResponse in the ‘pass saved response’ option on the outbound orchestration.


If authentication is required by the receiving system, choose the appropriate pre-defined Auth Code from the provided list. Refer to the Authentication Collection for additional details.

Request Templates

If the Receiving System expects the message payload to be provided in a specific format, the template for such format (as defined within the Receiving System API Specification) should be used to populate the ‘Template’ field within the Request Manager Control Panel.

Remove Saved HTTP Cookies

For HTTP connectors, this feature enables the removal of cookies on outbound requests. Singular or Multiple cookies can be removed by specifying their names with comma delimiters. For example, xSessionID,yMonitorId

Enabling Thread Pool

A throttle can be applied to limit the number of transactions per second delivered to a specific receiving system. This is potentially useful when the receiving system faces performance or capacity bottlenecks.

Remove GLU Headers

By default, when sending a request to an outbound endpoint, the following headers are added:


When the ‘Remove GLU headers’ selection is made, the above headers will be removed from the outbound request.

Was this article helpful?

Related Articles

Fill the form and we’ll contact you shortly

    I agree with

    We uses cookies to make your experience on this website better. Learn more
    Accept cookies