This section examines all the different (Pull) type requests. You must always use the entry point https://www.jobillico.com/api/info. Here are the various actions that can be carried out to retrieve information using the API.

Please note that the “bsandboxoff” node is optional. By default, the request is processed in our “sandbox” environment. The following nomenclature will enable you to make a request directly through our production environment: <bsandboxoff>1</bsandboxoff>.

1. locations : A request for information on locations.

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <locations>
                   <icompany><![CDATA[535]]></icompany>
                   <ilocation><![CDATA[327]]></ilocation>
           </locations>
   </request>
                   

   Several nodes <icompany> (containing a company number) or <ilocation> (containing a location number) can be set as child nodes in the information request

   If no child nodes are present, all locations to which the user has access will be returned

   The answer consists of a list of <olocation> objects :

   • ilocation: The identifier of the current object.
   • icompany: the company’s identifier.
   • bmain: it indicates whether this object is the default location of the company.
   • saddress: the address of the current object.
   • iradius: radius of action in which to search if necessary.
   • scity: the relevant city
   • sregion: the relevant region
   • estate: the relevant province
2. departments : A request for information on departments.

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <departments>
                   <icompany><![CDATA[535]]></icompany>
                   <idepartment><![CDATA[>2]]></idepartment>
           </departments>
   </request>
                   

   Several nodes <icompany> (containing a company number) or <idepartment> (containing a department number) can be set as child nodes in the information request

   If no child nodes are present, all departments to which the user has access will be returned

   The answer consists of a list of <odepartment> objects :

   • idepartment: The identifier of the current object.
   • icompany: the company’s identifier.
   • slabel: Name of the current object
3. jobfunctions : A request for the information on all areas of profession.

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <jobfunctions />
   </request>
                   

   The answer consists of a list of <ojobfunction> objects :

   • ijobfunction: The identifier of the current object.
   • slabel_fr: the French name of the current object
   • slabel_en: the English name of the current object
4. 1. benefits : A request for the information related to all the benefits of the company.

      Exemple:

      <?xml version="1.0" encoding="utf-8"?>                
      <request>
              <bsandboxoff>1</bsandboxoff>
              <oauth>
                      <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                      <sparam><![CDATA[your_password]]></sparam>
              </oauth>
              <benefits>
                  <icompany><![CDATA[535]]></icompany>
              </benefits>
      </request>
                              

      Several nodes <icompany> (containing a company number) can be put as a child node in the information request

      If no child nodes are present, all benefits to which the user has access will be returned

      The answer consists of a list of <obenefit> objects :

      • icompany: the company’s identifier.
      • ibenefit: The identifier of the current object.
      • slabel_fr: The French designation of the benefit
      • slabel_en: The English designation of the benefit
   2. allbenefits : A request for the information related to all the benefits

      Exemple:

      <?xml version="1.0" encoding="utf-8"?>                
      <request>
              <bsandboxoff>1</bsandboxoff>
              <oauth>
                      <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                      <sparam><![CDATA[your_password]]></sparam>
              </oauth>
              <allbenefits />
      </request>
                              

      The answer consists of a list of <obenefit> objects :

      • ibenefit: The identifier of the current object.
      • slabel_fr: The French designation of the benefit
      • slabel_en:The English designation of the benefit
5. Jobs : A request for the information on all the jobs

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <jobs>
                   <icompany><![CDATA[535]]></icompany>
                   <ijob><![CDATA[2042182]]></ijob>
           </jobs>
   </request>
                   

   Several nodes <icompany> (containing a company number) or <ijob> (containing a job number) can be put as child nodes in the information request

   At least one node <icompany> (containing a company number) is required

   The answer consists of a list of <ojob> objects :

   • ijob: Posting Identification Number
   • icompany: the company’s identifier.
   • boffer: Specify whether this is a posting (1) or an opportunity (0).
   • sreference: Internal Reference Number at client business.
   • stitle_fr: French Job title.
   • stitle_en: English Job title.
   • dmodification: Modification date of the job posting
   • dexpiration: Expiry date of the job posting
   • icreator: Creator's ID Number
   • irecruiter: Recruiter’s ID Number.
6. Companies : A request for information about the companies managed by this account

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <companies/>
   </request>
                   

   The answer consists of a list of <ocompanie> objects :

   • icompany: The identifier of the current object.
   • sname: Name of the current object
7. Recruiters : A request for information about recruiters

   Exemple:

   <?xml version="1.0" encoding="utf-8"?>                
   <request>
           <bsandboxoff>1</bsandboxoff>
           <oauth>
                   <sparam><![CDATA[your_email@jobillico.com]]></sparam>
                   <sparam><![CDATA[your_password]]></sparam>
           </oauth>
           <recruiters>
               <irecruiter><![CDATA[32957]]></irecruiter>
               <icompany><![CDATA[535]]></icompany>
           </recruiters>
   </request>
                   

   Several nodes <icompany> (containing a company number) or <irecruiter> (containing a recruiter number) can be set as child nodes in the information request

   If no child nodes are present, all recruiters to which the user has access will be returned

   The answer consists of a list of <orecruiter> objects :

   • irecruiter: The identifier of the current object.
   • icompany: The company ID to which the current object can connect
   • slogin: Email address of the current subject
   • sname: Name of the current object