Skip to main content

Retrieving the data

Before building the jobposting XML - ideally prior to every posting - your software should utilize a set of idibu's services to determine the correct values that will constitute the complete advert. Some are documented as part of this section; others can be referred to in the Webservices documentation.

  • Categories and locations
    • Core idibu data, always required to create a Job.
    • Users should be able to select the appropriate values in your system.
    • Knowing the location of the posting in advance allows to obtain the Portal's detailed information more efficiently.
  • Sender info
    • Ideally, rather than creating new Users or detecting them based on the email as part of the posting process, their profiles should be created and managed through the User Management Webservice.
    • Knowing the User ID of the person who performs the posting in advance allows to obtain the Portal's detailed information more efficiently.
    • The consultant profile data will most likely be stored in your system - you just need to tie idibu's User ID to it.
  • Job data
    • If reposting or cloning an existing Job, this webservice can be used to obtain all its data (including Portals' Extra Fields, if you're utilizing Direct Posting rather than Post Completion Pages) and pre-fill it in your posting form for the user's convenience.
    • This webservice can also be used to list all existing Jobs and their Posts for your users to choose from and manage.
    • Knowing the Title of the Job in advance allows to obtain the Portal's detailed information more efficiently.
    • The vacancy data will most likely be stored in your system; idibu's Job data can be used to just supplement it in specific scenarios.
  • Portal information
    • Required only if you're utilizing Direct Posting rather than Post Completion Pages.
    • Users should be able to select from the Portals they are subscribed to, and then be able to fill in each Portal's Extra Fields.

With all the above data established - some could be done automatically based on your system data, some selected by the user as part of your system's UI - you are in a position to build the full jobposting XML.