Exploring Taleo Webservice

First things first get the WebAPI doc from here http://www.taleo.com/products/business-edition-integration-web-api.php

They mention that first you get a web address from the dispatcher and then you use that for your queries. They mention testing with soapUI to test out your requests. You can get soapUI from here http://www.soapui.org/

So in soapui I created a new project and pointed it at this WSDL http://tbe.taleo.net/wsdl/DispatcherAPI.wsdl

Just for grins I pressed the green arrow, which of course responded back that it didn’t know my company name… hmm so how to pass it my credentials. Look in the guide for info about the getUrl

Ok, in soap I edit the request this line has a ? which needs to be replaced with our orgCode

<orgCode xsi:type=”xsd:string”>?</orgCode>

After editing I press go, and in response I get an https://tbe.taleo.net/etc…/etc&#8230;

Ok, so now I am assuming I will need to log on to this dispatched site.

I create a new project in soapUI and then use this link as the wsdl http://tbe.taleo.net/wsdl/WebAPI.wsdl

Scrolling around I see a login request. Doubling clicking on it I see

<in0>?</in0>
<in1>?</in1>
<in2>?</in2>

Checking the WebAPI.doc I can see that this is what is expected

Data Field Name Data Field Type Required Acceptable Values
in0 String Yes Company Code
in1 String Yes User ID
in2 String Yes Password

So I will fill in those tags with my creds and see what happens. Hmm I wonder how I tell it to use the dispatched URL….

Hmm so that is a roadblock, java.lang.IllegalStateException: No value for key [org.hibernate.impl.SessionFactoryImpl@3710b205] bound to thread [TP-Processor19]</faultstring>
<detail>

So, then I decided I should fire up Altova Mapforce (I love that software) unfortuantely I couldn’t get it to work either…

Hmm… well I will continue investigating

I was extremely amused by this post about EDI and SaaS

http://blogs.gartner.com/benoit_lheureux/2009/03/17/saas-apis-are-retro-%E2%80%93-you-know-just-like-edi/

As the guy who gets to read really long EDI specs I can emphasize with this post. Even more amusing was the fact that I had implemented the 48 page Target 850 purchase… and am in the middle of reading and implementing the Taleo API docs. It was like this blog post was written for me!