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 the Context Name, Method and Content Type to be used for the request. This definition can be different depending on the connector protocol. See the APIs and Connectors for more details.

Where the context name is specified to include variables – see URL Path Variables

Remove namespace

The remove namespace checkbox will remove namespace references on an outbound orchestration XML request.

Example: This payload will be transformed as below

<ns:root xmlns:ns=””>
















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

Change request to dropdown allows for three options on what should be sent to the receiving system.

  • Don’t Change: The request sent out will be as per request template / parameter configuration.
  • Pass Source Request: This will do a pass through of the incoming API request payload.
  • Pass Saved Responses: This 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.


Should the receiving system require Authentication, the pre-defined Auth Code should be selected from the list. For more details see here: Authentication Collection

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 allows you to remove cookies on outbound requests. The name of the cookie that you want to be removed on the outbound request can be added here. Multiple can be added through the use of comma delimiter example: xSessionID,yMonitorId

Enabling Thread Pool

Finally, a throttle on each specific receiving system Request can be applied. The Throttle can be used to limit the number of transactions per second that are delivered to a Receiving System. Potentially useful when the Receiving System has performance or capacity bottlenecks.

Remove GLU Headers

By default, when sending a request to an outbound endpoint, the following headers are added: GLU_TRX_ID, TRACE_ID, GLU_ID
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