Skip to end of metadata
Go to start of metadata

Create SOAP Object

  1. Select File > New > Web Service Request from the main menu. The New Web Service Request dialog will be displayed.

    Provide the name for the new service request object, select SOAP as Request Type then click OK.

  2. A new service request object is created under Object Repository of Katalon Studio.

  3. In the opened editor of the new service request object, enter all required information.


    Request MethodThe request method indicates the expected action to be executed on the specified resource. Katalon Studio supports following SOAP methods: SOAP, SOAP 1.2, POST, GET.
    Request URLThe WSDL address registered for the SOAP web service.
    Service FunctionThe function/method of the SOAP web service that you want to use in this SOAP request. The list will be retrieved after clicking Load from WSDL.

    Credential for HTTP authentication.

    HTTP Headers

    The header information that you want to transmit in this SOAP request object.

    You can select headers from the list of suggested options (by double clicking on the Name cell) or enter another header of your interest. Refer to Supported HTTP Headers for more details.

    Request Message

    The information that you want to transmit in this SOAP request object. You can enter directly or import content from external text files.


    The retrieved message from web service server when you click Test Request.

  4. Save the service request object when you're done. The service request defined here can be utilized in other test cases. Refer to Use WebService in Test Case for more details.


Supported HTTP Headers 

Here’s the list of HTTP headers initially supported in Katalon Studio:

Header field name



Content-Type items acceptable for the response.


Character sets that are acceptable.


List of acceptable encodings.


List of acceptable human languages for response.


Authentication credentials for HTTP authentication.


Used to specify directives that must be obeyed by all caching mechanisms along the request-response chain


Control options for the current connection and list of hop-by-hop request fields.


The length of the request body in octets (8-bit bytes)


The MIME type of the body of the request (used with POST and PUT requests).


An HTTP cookie previously sent by the server with Set-Cookie.


Requests a web application to disable their tracking of a user. This is Mozilla's version of the X-Do-Not-Track header field (since Firefox 4.0 Beta 11). Safari and IE9 also have support for this field.


The date and time that the message was sent (in "HTTP-date" format as defined by RFC 7231 Date/Time Formats.


Indicates that particular server behaviors are required by the client.


The email address of the user making the request.


Non-standard header field used by Microsoft applications and load-balancers.


The domain name of the server (for virtual hosting), and the TCP port number on which the server is listening. The port number may be omitted if the port is the standard port for the service requested. Mandatory since HTTP/1.1.


Only perform the action if the client supplied entity matches the same entity on the server. This is mainly for methods like PUT to only update a resource if it has not been modified since the user last updated it.


Allows a 304 Not Modified to be returned if content is unchanged.


Allows a 304 Not Modified to be returned if content is unchanged.


If the entity is unchanged, send me the part(s) that I am missing; otherwise, send me the entire new entity.


Only send the response if the entity has not been modified since a specific time.


Limit the number of times the message can be forwarded through proxies or gateways.


Initiates a request for cross-origin resource sharing (asks server for an 'Access-Control-Allow-Origin' response field).


Implementation-specific fields that may have various effects anywhere along the request-response chain.


Authorization credentials for connecting to a proxy.


Implemented as a misunderstanding of the HTTP specifications. Common because of mistakes in implementations of early HTTP versions. Has exactly the same functionality as standard Connection field.


Request only part of an entity. Bytes are numbered from 0.


This is the address of the previous web page from which a link to the currently requested page was followed. (The word “referrer” has been misspelled in the RFC as well as in most implementations to the point that it has become standard usage and is considered correct terminology).


The transfer encodings the user agent is willing to accept: the same values as for the response header field Transfer-Encoding can be used, plus the "trailers" value (related to the "chunked" transfer method) to notify the server it expects to receive additional fields in the trailer after the last, zero-sized, chunk.


Ask the server to upgrade to another protocol.


The user agent string of the user agent.


Informs the server of proxies through which the request was sent.


A general warning about possible problems with the entity body.


Allows easier parsing of the MakeModel/Firmware that is usually found in the User-Agent String of AT&T Devices


Used to prevent cross-site request forgery. Alternative header names are: X-CSRFToken and X-XSRF-TOKEN.


A de facto standard for identifying the originating IP address of a client connecting to a web server through an HTTP proxy or load balancer.


A de facto standard for identifying the original host requested by the client in the Host HTTP request header, since the host name and/or port of the reverse proxy (load balancer) may differ from the origin server handling the request.


A de facto standard for identifying the originating protocol of an HTTP request, since a reverse proxy (or a load balancer) may communicate with a web server using HTTP even if the request to the reverse proxy is HTTPS. An alternative form of the header (X-ProxyUser-Ip) is used by Google clients talking to Google servers.


Requests a web application override the method specified in the request (typically POST) with the method given in the header field (typically PUT or DELETE). Can be used when a user agent or firewall prevents PUT or DELETE methods from being sent directly (note that this either a bug in the software component, which ought to be fixed, or an intentional configuration, in which case bypassing it may be the wrong thing to do).


Mainly used to identify Ajax requests. Most JavaScript frameworks send this field with value of XMLHttpRequest.


Server-side deep packet insertion of a unique ID identifying customers of Verizon Wireless; also known as "perma-cookie" or "supercookie".


Links to an XML file on the Internet with a full description and details about the device currently connecting. In the example to the right is an XML file for an AT&T Samsung Galaxy S2.

Refer to for more info.




  • No labels