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.
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. Extra incoming parameters are rejected, and any non-configured output parameters are excluded from the response.
False: The system can process any external request, regardless of the configured parameters, but still enforces validation rules applied to the parameters.
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.

Based on the configured parameters, endpoint URL, and operation name, the system generates the WSDL. Any configuration changes automatically update the WSDL URL.
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 WSDLs in Qntrl
How to make a SOAP WSDL Request
Method: GET
URL Format: https://core.qntrl.com/webservice/soap/<ZSOID>/<source_endpoint>?WSDL
Authentication: Include necessary authentication details in the request header (e.g., API key, OAuth, or 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: POST
URL Format: https://core.qntrl.com/webservice/soap/<ZSOID>/<source_endpoint>
Authentication: Include necessary authentication details in the request header (e.g., API key, OAuth, or basic authentication).
Body: The body should contain the raw XML request data.
Sample SOAP Request:
<soapenv:Envelope
<soapenv:Header>
<ord:AuthHeader>
<ord:companyName>Zoho Corp</ord:Username>
</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>