null

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Note

The credentials provided as a result of this call will be required for almost all subsequent calls and is used as a security measure to receive specific information,

In this instance I am making a call to loggin into my uat environment through postman, as I require my Session credentials to perform any further Web Service Calls.

Endpoint: https://bau-uat-ws.azurewebsites.net/Data/ChainIT/DataService.svc

Headers: 

Body:

SOAP Web Service Call Body Example
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:cha="http://www.opensys.com.au/ChainIT/4.0/ChainITDataServices">
   <soapenv:Header/>
   <soapenv:Body>
<!-- Requirements of each soapAction can be found http://support-ws.azurewebsites.net/Data/ChainIT/DataService.svc?xsd=xsd0 -->

				<!-- Example XSD Schema available for Login

					<xs:element name="Login">
						<xs:complexType>
							<xs:sequence>
								<xs:element minOccurs="0" name="userName" nillable="true" type="xs:string"/>
								<xs:element minOccurs="0" name="password" nillable="true" type="xs:string"/>
							</xs:sequence>
						</xs:complexType>
				</xs:element> 

				Example XSD Schema available for Login -->

<!--Below Content Dependent on soapAction Selected  -->

      <cha:Login>
         <!--Mandatory:-->
         <cha:userName>blah@exampleemail.com</cha:userName>
         <!--Mandatory:-->
         <cha:password>Password1@</cha:password>
      </cha:Login>


   </soapenv:Body>
</soapenv:Envelope>


2) How to make a Web Service Call


Filter by label

There are no items with the selected labels at this time.



  • No labels