
Early Access
This feature is not enabled for all users. If you’d like to try it out, please email our support team for early access.
Inbound SOAP Web Services allow you to create endpoints that external systems can call to interact with your Qntrl instance. When a SOAP request is sent from an external system, Qntrl processes the request and sends back a response based on predefined operations. To define and structure these SOAP-based interactions, WSDL (Web Services Description Language) contracts are used which describes the available operations, the expected request parameters, and the format of the response.
Example:
A third-party system sends a SOAP request to your Qntrl instance to retrieve customer details. Qntrl processes this request and sends the customer details as an XML response.
Creating an Inbound SOAP Web Service
To create an inbound SOAP web service in Qntrl:
1. Navigate to
(settings) >> WEB SERVICES >> Inbound >> Select SOAP. 2. Define the service :
Name: Provide a unique name for the SOAP service.
Source Endpoint: The endpoint URL that will be used to interact with your SOAP service.
Operation: The operation the service will perform. Default: execute.
Resource: Choose an existing function or create a new one to define the actions for the SOAP service. Only SOAP-type functions will be shown in the list. If you create a new function, write the script in the editor. The function will automatically appear in the function module with a generated name, which you can change later.
Authentication Type: Choose the authentication type for the API call. Qntrl supports three authentication types:
Mandate WSDL Compliance: Select the option to enable WSDL compliance.
True
Only the configured request and response parameters are allowed. Any extra parameters in the incoming request will be rejected.
Non-configured output parameters will be excluded from the response.
The operation name in the request must exactly match the one defined in the WSDL — otherwise, the request will fail.
False
The system accepts any external request, even if it contains parameters not defined in the WSDL.
However, it still applies validation rules to the parameters you have configured.
Request Params: Define the parameters to be passed in the request.
Param Name: Define the name of the input parameter.
Type: Select the data type.
Allowed Regex: Set restrictions for the parameter values.
Min Length: Define the minimum length of the input.
Max Length: Define the maximum length of the input.
Default Value: Set default values for parameters.
Mandatory: Specify whether the parameter is mandatory. If a mandatory parameter is missing, an error will occur.
Response Params
Validation ensures incoming requests meet the expected format. If validation fails, the request will be rejected.

Qntrl automatically generates the WSDL based on the endpoint URL, operation name, and the configured request/response parameters. Any changes made to these configurations will automatically update the WSDL.
To download the WSDL, send a GET request to the endpoint URL using the selected authentication method.
Processing Requests and Responses
The Editor provides a flexible environment to process both SOAP requests and responses, and to handle errors efficiently using CodeX SDK's.
Handling SOAP Requests
Managing SOAP Responses
Handling Errors
Calling and Processing WSDL in Qntrl
How to make a SOAP WSDL Request
Method: Any HTTP method (e.g., GET)
URL: https://core.qntrl.com/webservice/soap/<org-id>/<source_endpoint>?WSDL
Authentication (must be added in the request header):
OAuth Token
API Key
Basic Authentication
You need to append ?wsdl to the service URL. The WSDL defines the operations and message structure for the service.This will return the WSDL for the specified API, which external systems can use to interact with the service.
How to Send a SOAP Message Request
Method: Any HTTP method (e.g., POST)
URL: https://core.qntrl.com/webservice/soap/<org-id>/<source_endpoint>
Authentication (must be added in the request header):
OAuth Token
API Key
Basic Authentication
Body: The body should contain the raw XML request data.
Sample SOAP Request:
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:ord="https://98173384.core.localqntrlhost.com/webservice/98173384/orderManagement">
<soapenv:Header>
<ord:AuthHeader>
<ord:companyName>Zoho Corp</ord:companyName>
</ord:AuthHeader>
</soapenv:Header>
<soapenv:Body>
<ord:PlaceOrder>
<ord:OrderID>12345</ord:OrderID>
<ord:CustomerID>98765</ord:CustomerID>
<ord:ProductID>10111</ord:ProductID>
<ord:Quantity>3</ord:Quantity>
<ord:OrderDate>2025-03-28</ord:OrderDate>
</ord:PlaceOrder>
</soapenv:Body>
</soapenv:Envelope>
Other Actions
Enable or Disable a SOAP Request
You can control the activation of individual SOAP requests from the configuration panel:
Navigate to
(settings) >> WEB SERVICES >> Inbound >> Select SOAP.
Under the Resources section on the left panel, locate the SOAP message.
Use the toggle button next to the message name to enable or disable it.
Delete a SOAP Request
To remove a SOAP request:
Navigate to
(settings) >> WEB SERVICES >> Inbound >> Select SOAP.
Select the message you want to delete.
Click the delete icon at the top right of the message details page.