Jobillico

The Network of Employers
 

JobIllico-API

Jobillico-API is an interface which provides businesses with a means of automating job posting submissions. Businesses can also add job postings to their existing accounts or retrieve some information. Here are some key points to consider when using the interface :
  • For all (Pull) type requests that are aimed at recovering information, use the entry point https://www.jobillico.com/api/info.
  • For all (Push) type requests aimed at modifying or adding a job posting, use the entry point https://www.jobillico.com/api/push.
  • Each query is made in the form of an XML (encoded as a utf-8) which must be submitted in POST. You will find both a description and an example of each type of query in XML format which are accepted in the submenus.
  • Each action must be described by a node that is clean. Bear in mind that several actions can be listed in the same XML. It is important to respect the nomenclature defined in this document when sending a request or else an error might occur.
  • The first node in the query in XML must be <request>.
  • All actions (commands) described by a node will have a written reply in the same node name.
  • Please note that, by default, you will be working in a testing environment (sandbox). Once your tests are conclusive, please contact us so that we can grant you access to the API for production.

All API requests must contain the <oauth> node used to authenticate yourself. It is imperative that it appears before all other commands. It contains 2 mandatory subnodes. The first <sparam> subnode must contain the Login, the second subnode must contain the password. The order is obligatory.

Exemple:

<oauth>
        <sparam><![CDATA[jobillico_user@jobillico.com]]></sparam>
        <sparam><![CDATA[jobillico]]></sparam>
 </oauth>
                

N.B.:

In the case of an offer insertion, this node is alternative by another: , which defines the first sub-node(according to the same structure) the login of the creator of the offer.... The second sub-node is not necessary.