Workable JobRelay field reference guide

This page outlines all of the data that is received in WordPress from Workable 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 created in Workable. The job description contains the description, the requirements and the benefits combined together. These fields are available individually below.

Fields which need mapping

These are fields sent in the data feed from Workable 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.

JSON nodeData typeExample valueNotes
descriptionstring<p>This is the job description.</p>The main description of the job. It can contain the following HTML elements:
requirementsstring<ul><li>This is the job description.</li></ul>An unordered list of the job requirements added in Workable.
benefitsstring<p>These are the job benefits.</p>The job benefits. Allowed HTML as description.
job_referencestring22C8EFE84AThe unique reference for the job. This is the shortcode is Workable.
created_atstring2023-11-28T11:26:09ZThe timestamp when the job was created.
application_urlstring URL to the application form for the job, hosted by Workable.
salary_currencystringgbpCurrency code for the salary
salary_fromfloat10000A number (float) for the lower salary.
salary_tofloat15000A number (float) for the upper salary.
job_salarystring1000 – 15000The salary from and to value.
job_locationstringLondon, UKThe formatted location string.
job_location_rawstringNewcastle upon Tyne, England, United KingdomThe raw location string.
telecommutingbooleantrueTrue is the job is a telecommuting job and false otherwise
working_arrangementstringRemoteEither remote, hybrid or on_site
employment_typestringFull-timeThe assigned employment type to the job.
functionstringHealth Care ProviderThe job’s function.
industrystringHospital & Health CareThe job’s industry.
member_namestringJohn SmithThe name of the member associated with this job in Workable.
member_emailstringjohn.smith@example.comThe email address of the member associated with the job.
member_headlinestringSample headlineThe headline of the member.

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.