Purpose
This Web Service Call allows a third party application to retrieve a valid session in order to call / access the other API functions of this web service. The credentials must be provided by your assigned solutions consultant. A OneFlo login is not advisable for use in these instances.
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,
*Learn how to chain this call in Creating Chained Requests
In this instance I am making a call to login 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
This is not the production endpoint. The production endpoint will be provided once all requests have been validated to work correctly.
Headers:
- Key: Content-Type Value: text/xml
- Key: SoapAction Value: http://www.opensys.com.au/ChainIT/4.0/ChainITDataServices/IChainITService/Login
Body:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="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 --> <Login> <!--Mandatory:--> <userName>blah@exampleemail.com</userName> <!--Mandatory:--> <password>Password1@</password> </Login> </soapenv:Body> </soapenv:Envelope>
Related articles
Filter by label
There are no items with the selected labels at this time.