Your question asked "how to use the httpClient from JavaScript?" But I think you really want to know, "how can I invoke the Avalara Tax Service from an Apigee Edge API Proxy?"
@Faij Ahmad is correct : the URL you mentioned is just a service description page. It gives information about the service (useful for humans) - it is not the endpoint for the service (useful for apps).
Searching on Google, I found the actual WSDL for the Avalara Tax service is here:
https://development.avalara.net/Tax/TaxSvc.wsdl
The WSDL is just a machine-readable service description (WSDL = Web Services Description Language). Again, it is not the app endpoint, but the WSDL tells me the app endpoint. It is https://development.avalara.net/Tax/TaxSvc.asmx?Ping
What I would do:
- Figure out how to construct a request to the Avalara service you want.
- Use ServiceCallout (not JS and httpClient) to invoke the service
By googling around and playing, and with no thanks to the avalara developer documentation which I found to be confusing, I was able to build a request to invoke the Ping operation on that TaxService, and get a real response.
My request was like this:
curl -i -X POST https://development.avalara.net/Tax/TaxSvc.asmx?Ping \
-H soapAction:http://avatax.avalara.com/services/Ping \
-H Content-Type:text/xml \
--data '
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:avalara="http://avatax.avalara.com/services">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soap:actor="http://schemas.xmlsoap.org/soap/actor/next">
<wsse:UsernameToken>
<wsse:Username>My-Account-Id</wsse:Username>
<wsse:Password>My-License-Key</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<avalara:Profile>
<avalara:Name>TEST</avalara:Name>
<avalara:Client>ClientSOAP</avalara:Client>
<avalara:Adapter>SOAP API</avalara:Adapter>
<avalara:Machine>MBPRO</avalara:Machine>
</avalara:Profile>
</soap:Header>
<soap:Body>
<avalara:Ping/>
</soap:Body>
</soap:Envelope>
'
and the response I got was a pretty standard SOAP fault:
<s:Envelope
xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<s:Fault>
<faultcode>s:Client</faultcode>
<faultstring xml:lang="en-US">The user or account could not be authenticated.</faultstring>
</s:Fault>
</s:Body>
</s:Envelope>
ok, so that says I got a good endpoint, but my security credentials were rejected. (I don't know why - I registered for a free trial account, but it's rejecting my creds). I'm assuming you have valid credentials for the Avalara service and you can insert them into place in the above.
How can you do the equivalent within an Apigee Proxy? Use ServiceCallout. The ServiceCallout also lets you template-ify the messaging being sent. Like this:
<ServiceCallout name='SC-AvalaraPing'>
<Request>
<Set>
<Headers>
<Header name='soapAction'>http://avatax.avalara.com/services/Ping</Header>
</Headers>
<Payload contentType='text/xml'>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ser="http://avatax.avalara.com/services">
<soap:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
soap:actor="http://schemas.xmlsoap.org/soap/actor/next">
<wsse:UsernameToken>
<wsse:Username>{avalara_accountid}</wsse:Username>
<wsse:Password>{avalara_licensekey}</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
<ser:Profile>
<ser:Name>Apigee TEST</ser:Name>
<ser:Client>Apigee Edge Client</ser:Client>
<ser:Adapter>SOAP API</ser:Adapter>
<ser:Machine>MBPRO</ser:Machine>
</ser:Profile>
</soap:Header>
<soap:Body>
<ser:Ping/>
</soap:Body>
</soap:Envelope>
</Payload>
<Verb>POST</Verb>
</Set>
</Request>
<Response>avalaraResponse</Response>
<HTTPTargetConnection>
<SSLInfo>
<Enabled>true</Enabled>
<IgnoreValidationErrors>true</IgnoreValidationErrors>
</SSLInfo>
<Properties>
<Property name='success.codes'>2xx, 3xx, 4xx, 5xx</Property>
</Properties>
<URL>https://development.avalara.net/Tax/TaxSvc.asmx?Ping</URL>
</HTTPTargetConnection>
</ServiceCallout>
Augment that policy with some XSL and an XMLToJSON policy and you can get a JSON response out.
Find attached a working API Proxy. avalara-sc-apiproxy-20180306-1145.zip
Deploy it to your org/env, and then Invoke it like this:
curl -i -u ${ACCOUNTID}:${LICENSEKEY} \
https://${ORG}-${ENV}.apigee.net/avalara-sc/ping
My response looks like this:
{
"Fault": {
"faultcode": "s:Client",
"faultstring": {
"lang": "en-US",
"$": "The user or account could not be authenticated."
}
}
}
LinkedIn
Twitter
