Web Services in Qntrl – REST & SOAP Integration Explained | Inbound REST | Outbound REST | Inbound SOAP | Outbound SOAP

Web Services Overview

Alert

Early Access  

Web Services is not enabled for all users. If you’d like to try it out, please email our support team for early access.

Web services enable different applications to communicate with each other over a network using standard protocols, enabling the exchange of data and execution of remote operations. The Qntrl platform supports two types of web services:
  1. Inbound Web Services: These services allow your system to receive requests from external systems.
    • Inbound REST Web Services
    • Inbound SOAP Web Services
  2. Outbound Web Services: These services allow your system to send requests to external systems.
    1. Outbound REST Web Services

    2. Outbound SOAP Web Services
 

REST Web Services 

REST (Representational State Transfer) is a lightweight, flexible architecture widely used for building web APIs. RESTful services communicate using standard HTTP methods like GET, POST, PUT, and DELETE, and typically exchange data in formats such as JSON or XML.

Key features

  • Stateless: Each request from the client to the server must contain all the information needed to process the request.
  • Resource-based: Interactions are centered around resources (data objects), each identified by a unique URL.
  • Lightweight: Minimal overhead with easy integration and better performance.
Info

  • Ideal for mobile and web applications.

  • Common in modern APIs where fast, scalable communication is required.

  

SOAP Web Services

SOAP (Simple Object Access Protocol) is an XML-based protocol used for exchanging structured information in web services. It follows specific guidelines:
  • Request and Response Format: Both must be in XML.
  • HTTP Method: The request must be sent via POST method.
  • Request Payload: Must be included in the body, not in query parameters or headers. The request message follows a specific structure with operations defined in the XML request tags.
 

Key features 

  • Strict standards: Uses WSDL (Web Services Description Language) for describing service structure.
  • Highly secure and reliable: Supports advanced features like WS-Security, transactions, and message-level encryption.
  • Platform and language independent.
Info

  • Preferred in enterprise environments where security, transaction integrity, or formal contracts are required.

  • Common in integrations with legacy systems or large-scale business applications.

 

WSDL in SOAP Web Services  

WSDL (Web Services Description Language) is an XML-based definition that describes the structure of a SOAP web service. It outlines the service operations, input and output data types, communication protocols, and endpoint locations. Both Inbound and Outbound SOAP services in Qntrl use WSDL to define and facilitate communication between systems.
  • Inbound SOAP Service: When you create an Inbound SOAP service in Qntrl, a WSDL file is generated automatically. This WSDL acts as a service contract that defines the available operations, expected request formats, and the response structure. External systems can access this URL to download the WSDL and configure their SOAP client to interact with your web service.
  • Outbound SOAP Service: For an Outbound SOAP service, you need to provide the WSDL file of the external service. Qntrl uses it to understand the operations supported by the external service and format outgoing SOAP requests accordingly.
 



Next:




    • Related Articles

    • Overview of Bridge

      What is a Bridge? Bridge is an installable, lightweight independent agent that can be deployed on the customer’s local network. It is compatible both on Windows and Linux machines with 32 and 64-bit OS. Its role is to facilitate communication between ...

    • Configure Inbound SOAP Web Service

      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 ...

    • Configure Inbound REST Web Service

      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. Qntrl’s Inbound REST Web Service allows you to create custom API endpoints that external users or systems can call to ...

    • Configure Outbound SOAP Web Service

      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. Outbound SOAP services in Qntrl enable communication with external SOAP-based APIs. These services rely on WSDL (Web ...

    • Configure Outbound REST Web Service

      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. Outbound REST Web Services enables users to interact with external web services by sending HTTP requests to retrieve, ...

    You are currently viewing the help articles of Qntrl 3.0. If you are still using our older version and require guidance with it, Click here.