Skip to main content

idibu Test Portal

This Portal is meant to be your main test posting destination, allowing to simulate most Portal-related API usage scenarios, including:

Basic info​

Portal ID​

1234

Non-dynamic, but actually dynamic​

idibu Test Portal is recognized by idibu's API as a non-dynamic integration, as indicated by the <dynamic>no</dynamic> element in the Portal Management webservice responses. This is because it operates on a batch-upload basis where all Jobs land in an XML file hosted on idibu's servers.

Under typical circumstances (like, for example, in the case of Indeed), such files would then need to be processed by a job board at regular intervals, outside of idibu's system's scope. However, idibu Test Portal's functionality ends with the posting landing in the batch-upload file, the act of upload itself serving as a simulation of an actual dynamic posting process.

Therefore, for all practical purposes, idibu Test Portal can be treated as a dynamic integration that, immediately upon the Post leaving the Posting Queue, will provide a complete and functional response.

Login details​

There are two login Extra Fields that must be filled in when subscribing to idibu Developer Portal:

Email address (idibutest_user)​

Please use your email address - a notification email will be sent to it after the first successful posting for the given Client account, informing about the location of the jobs file.

Password (idibutest_pass)​

This is not validated in any way and can be anything!

Per-client files​

For every Client account that posts to idibu Test Portal, an XML file is automatically created. Upon the first successful posting for a given Client account, an email notification will be sent to the address specified in the idibutest_user Extra field (see Login details above), specifying the location of the file.

The file's URL will also be included in each successful <posting>'s <link> element of the Job's Detailed View webservice response.

Each file will store all currently live (non-deleted and non-expired) Jobs posted from the corresponding Client account to the idibu Test Portal. Within the XML, each <job> object will contain all idibu data relating to Job, User, and idibu Test Portal's Extra Fields, allowing you to see the full effect of your posting and debug the process.

XML file structure​

<job>
  <id>[integer]</id> <!-- Job ID; refer to https://docs.idibu.com/docs/v2/webservices/job-management -->
  <idibutest_user>[string]</idibutest_user>
  <idibutest_pass>[string]</idibutest_pass>
  <client_id>[integer]</client_id> <!-- ID of the Client account; refer to https://docs.idibu.com/docs/v2/webservices/service-management -->
  <!-- User data; refer to https://docs.idibu.com/docs/v2/webservices/user-management -->
  <user_id>[integer]</user_id> 
  <user_name>[string]</user_name>
  <user_office>[string]</user_office>
  <user_team>[string]</user_team>
  <user_phone>[string]</user_phone>
  <user_fax>[string]</user_fax>
  <user_email>[string:email]</user_email>
  <user_www>[string:url]</user_www>
  <user_address>[string]</user_address>
  <user_company>[string]</user_company>
  <!-- Job data; refer to https://docs.idibu.com/docs/v2/webservices/job-management -->
  <job_title>[string]</job_title>
  <job_reference>[string]</job_reference>
  <job_description>[string]</job_description>
  <job_start>[string]</job_start> <!-- YYYY-MM-DD unless overridden by idibutest_odat -->
  <job_duration>[string]</job_duration>
  <job_type>["contract"|"permanent"|"temporary"]</job_type>
  <job_time>["fulltime"|"parttime"]</job_time>
  <job_industry>[string]</job_industry>
  <job_location>[string]</job_location>
  <!-- for the two above, refer to https://docs.idibu.com/docs/v2/posting-api/categories-and-locations -->
  <salary_min>[string]</salary_min>
  <salary_max>[string]</salary_max>
  <salary_currency>[string]</salary_currency>
  <salary_period>["annum"|"month"|"week"|"day"|"hour"]</salary_period>
  <salary_extras>[string]</salary_extras>
  <salary_text>[string]</salary_text> <!-- autogenerated from all salary fields unless override by idibutest_osal -->
  <!-- idibu Test Portal Extra Fields; refer to https://docs.idibu.com/docs/v2/posting-api/portal-information and https://docs.idibu.com/docs/v2/posting-api/posts-section -->
  <idibutest_text>[string]</idibutest_text>
  <idibutest_area>[string]</idibutest_area>
  <idibutest_select>[string:enum]</idibutest_select>
  <idibutest_multi>[string:enum]</idibutest_multi> <!-- can be multiple -->
  <idibutest_double_parent>[string:enum]</idibutest_double_parent>
  <idibutest_double_child>[string:enum]</idibutest_double_child>
  <idibutest_dmulti_parent>[string:enum]</idibutest_dmulti_parent>
  <idibutest_dmulti_child>[string:enum]</idibutest_dmulti_child> <!-- can be multiple -->
  <!-- Post data -->
  <post_modified>[string:date]</post_modified> <!-- YYYY-MM-DD HH:mm:ss -->
  <post_expiry>[string:date]</post_expiry> <!-- YYYY-MM-DD HH:mm:ss -->
  <post_duration>[integer]</post_duration>
  <application_email>[string:email]</application_email> <!-- unique application email address - any email sent to this address will arrive in idibu as an Applicant for the given Job; refer to https://docs.idibu.com/docs/v2/webservices/applicant-management -->
  <application_url>[string:url]</application_url> <!-- idibu's autogenerated application page - anyone who completes the form will arrive in idibu as an Applicant for the given Job; will be overridden by app_url or idibutest_url -->
</job>

Application pages​

Unless you provide your own Application URL in the app_url Dynamic Core Field or the idibutest_url Extra Field, every posting to idibu Test Portal will automatically generate a simple application page under aptrack.co domain, similarly to the Aptrack Test Feed. This page's URL will be available as the <application_url> element of the corresponding <job> element in the XML file.

You can access the URL to see an example HTML-rendered display of your Job, with all its basic details and the application form at the bottom. Anyone who applies via this form will create a functional Applicant record under the Applicant Management webservice, effectively simulating a standard application process through a Portal's native form.