Skip to main content

LinkedIn Jobs

Basic info​

Portal ID​

1697

LiveAuth API​

LinkedIn Jobs integration utilizes idibu's LiveAuth API - Clients need to connect their LinkedIn Recruiter account and select their Contract for your system to fill in the Contract ID (linjobs_cid) subscription field.

To see an example UX of how this flow is handled in practice, you can review the article that describes the process in idibu's standalone UI.

Basic vs. Premium jobs​

idibu's LinkedIn Jobs integration allows posting both Basic and Premium jobs. Consult this article for more info.

Important aspects to keep in mind:

  • LinkedIn has stipulated that staffing/recruitment agencies and businesses can only post Premium jobs. LinkedIn manages this based on the Client's business profile.
  • If the Client is not eligible for Basic postings, their Posts will still appear as successful in idibu - but will not be visible on LinkedIn until upgraded to Premium.
  • Any Client account that has been created less than 30 days ago will not be able to post Basic adverts to LinkedIn Jobs - the Post will automatically fail after leaving idibu's Posting Queue.
  • Premium posting is only available with a valid Contract ID, connected through the LiveAuth API (see above).

Apply Connect / Easy Apply​

idibu's LinkedIn Jobs integration supports the Apply Connect feature, allowing candidates to apply directly via Easy Apply using their LinkedIn profile. For more information on the feature, consult this article.

Apply Connect is only available:

  • for Premium jobs posted under a valid Contract ID;
  • when no Application URL is used (both the app_url DCF and the linjobs_url Extra Field are empty).

Double status verification and webhooks​

Once a Post to LinkedIn Jobs leaves the Posting Queue, the status returned for that Post will only constitute an initial response from LinkedIn's API. It usually takes a bit longer for LinkedIn to fully process and authorize the posting - which is why idibu performs the final posting status verification every 10 minutes.

This means that, after the initial successful posting, the final status can still change in the next 10th minute of the hour (:00, :10, :20, :30, :40, :50). Only this final status will be reported by idibu's Post webhooks.

Therefore, if you see a <status> of a LinkedIn Jobs <posting> that is either posted or updated under the Job's detailed view method, and has not yet been reported by the corresponding webhook, its status has most likely not yet been updated. If the <link> becomes available, a successful posting can be considered finalized.

Login details​

Company ID (linjobs_rid)​

This article explains how Clients can obtain their Company ID.

This field is required and, if used without the Contract ID (see below), will only allow Basic posting (see above).

Contract ID (linjobs_cid)​

This field is optional, but must be filled in via a successful LiveAuth connection (see above) to allow Premium posting.

Default Listing Type (linjobs_statadm)​

This optional drop-down field allows the BASIC or PREMIUM value and defines the default listing type that idibu will apply to each posting. Please keep in mind, however, that Premium postings will not work without a valid, LiveAuth-connected Contract ID.

The choice in this field can be overridden on a per-posting basis using the linjobs_sta Extra Field.

Apply Connect (linjobs_appadm)​

This optional drop-down field allows the ENABLE or DISABLE value. By default - unless DISABLE is selected - Apply Connect will be enabled for all Premium jobs that do not use the Application URL. See above for more info.

The choice in this field can be overridden on a per-posting basis using the linjobs_app Extra Field.

Show Poster Info (linjobs_hide)​

This optional drop-down field allows the false or true value, deciding whether LinkedIn would display the poster information on the job description page. The default value is false (no posting consultant info displayed on LinkedIn).

The posting profile is determined by LinkedIn based on the posting User's email address.

Portal's detailed information requirements​

To correctly obtain all Extra Field data for LinkedIn Jobs, the following non-required parameters of the Portal's detailed information method are necessary:

  • country - required to generate the matching linjobs_loc list of options;
  • location - required to generate the matching linjobs_loc list of options;
  • profileID - provide it if the posting User (or Office or Team to which that User belongs) has a specific linjobs_cid and/or linjobs_rid value.

Location handling​

The Location Override (linjobs_city) Extra Field is a free-text field that accepts any location input (preferably in a "place name, region/county/state, country" format) and, if filled in, will be used instead of the Location (linjobs_loc) field regardless of its value.

Under normal circumstances, if the country and location values provided when querying the Portal's detailed information method match valid locations in LinkedIn's API, such matching options will be returned in the linjobs_loc Extra Field.

However, if the linjobs_loc field returns no location values (either due to the lack of country and location values, or these values not matching any valid location in LinkedIn's API), the NONE value can always be selected in the field, and the linjobs_city field can be used to override it - either by providing your system's location data or by allowing the user manual entry. LinkedIn will then attempt to automatically match the location, which, at that point, will be outside of idibu's control. The results may vary, especially for limited input.

In fact, even if the linjobs_city field is empty and the linjobs_loc field is set to NONE, idibu will still attempt to send its own core location to allow LinkedIn's automated matching. Please be aware that results may vary.

Hidden Extra Fields​

There are four extrafield elements of type="hidden" returned in LinkedIn Jobs' Portal's detailed information:

  • linjobs_sec - present for legacy reasons only; will be removed at some point; please ignore
  • linjobs_skills - present for legacy reasons only; will be removed at some point; please ignore
  • linjobs_altloc - this is for a feature that's still in review; please ignore for now

The remaining linjobs_url hidden Extra Field is a standard Application URL Dynamic Core Field.