Idibu JobRelay field reference guide

This page outlines all of the data that is received in WordPress from Idibu in the JobRelay feed.

Auto mapped fields

These fields are sent by the posting provider and automatically mapped to be saved in WordPress. Job title is saved as the post title, job description saved to the post content and the job short description is saved as the post excerpt.

JSON nodeData typeExample valueNotes
job_titlestringWordPress DeveloperThe job title – no HTML allowed.
job_descriptionstringthe main description of the job. It can contain the following HTML elements
job_short_descriptionstringA short summaryA string of text to summarise the job.
job_sourcestringAwesome Job Posting ServiceA string representing the source of the job (where it was written). For example Broadbean, LogicMelon or Idibu

The job post date will be the date and time when the job was posted to JobRelay.

Fields which need to be mapped

These are fields sent in the data feed from Idibu that need a mapping in WordPress. If they are not mapped to either meta or taxonomies, they will not be saved.

Learn how to map JobRelay fields in WordPress.

Standard fields

These fields don’t have values that are selected in Idibu. The values are entered into the Idibu inputs.

JSON nodeData typeExample valueNotes
contact_namestringJane SmithThe recruiters name.
contact_emailstringjane.smith@mail.comThe recruiters email
contact_telephonestring01234567890The recruiters telephone number.
contact_urlstring/urlhttps://site.urlThe recruiters website URL.
company_namestringJobRelayThe company name where the position is.
company_taglinestringRelaying JobsThe company tagline where the position is.
company_websitestring/urlhttps://jobrelay.ioThe company website where the position is.
company_twitterstring@jobrelayThe company twitter handle where the position is including the @ symbol.
company_logostring/url company logo where the position is. This should be a hosted image URL.
expiry_datedate2020-12-01When the job expires or no longer takes applications. Should be in the format of YYY-MM-DD.
start_datestring2021-01-10 or ASAPWhen the job starts. Can be any string including in a date format.
salary_currencystringGBPCurrency code for the salary
salary_fromfloat10000A number (float) for the lower salary.
salary_tofloat£20 per hour + Holiday PayA salary string.
salary_perstringannumFor more information please see our Default Values.
salary_benefitsstringLaptop & healthcareFreetext, additional salary information.
salarystring15000A number (float) for the salary.
featuredboolean11 to mark as featured or 0 (default) to not be featured.
job_locationstringLondon, UK
job_imagestring URL of an image. Also accepts and image ID.
custom_datastringSome custom dataThis is an open text field for any additional information.

Multi-select fields

These are the fields that have multi-options from which to select from in Idibu.

JSON nodeData typeExample valueNotes
job_typestringContractA pipe (|) separated list of job types.
job_industrystringITA pipe (|) separated list of job industries.
job_hoursstringFull TimeA pipe (|) separated list of job hours. Used for full time and part time.
working_arrangementstringRemoteOne of either “Remote”, “Hybrid” or “Office based”. If none selected and empty field is sent.
experience_levelstringSeniorA pipe (|) separated list of experience levels.
job_rolestringConsultantA pipe (|) separated list of job roles.

Note: the options that appear in the multi-select fields are pulled from WordPress. Therefore editing these in WordPress, for example adding new terms to a mapped taxonomy will shortly be reflected in the options seen in Idibu.

Geo location fields

These fields are available for all providers. The providers don’t actually send this data. It is generated by JobRelay for each job and then sent onto your WordPress website.

JSON nodeData typeExample valueNotes
geo_latfloat53.19339The latitude of the job location.
geo_longfloat-2.89075The longitude of the job location.
geo_formatted_addressstringChester, UKThe formatted address of the location sent.
geo_citystringChesterThe name of the city for the geo located location
geo_country_shortstringGBThe shortened country name for the geo located location
geo_country_longstringUnited KingdomThe long country name for the geo located location
geo_administrative_area_level_2_shortstringCheshire West and ChesterThe short version of the second level administrative area.
geo_administrative_area_level_2_longstringCheshire West and ChesterThe long version of the second level administrative area.
geo_administrative_area_level_1_shortstringEnglandThe short version of the first level administrative area.
geo_administrative_area_level_1_longstringEnglandThe long version of the first level administrative area.

It is worth noting that not all of this data is available for every job. JobRelay uses the Google Geo coding API to obtain Geo data for each job, using the job_location field.

The location is run through the API and the resulting data sent on. Depending on the location string, not all this data may be available.

For example, if the location sent via JobRelay is Lancashire, UK, a geo_city value will not be present. This is because the location is not specific enough to return a city value.