JobAdder JobRelay field reference guide
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 node | Data type | Example value | Notes |
|---|---|---|---|
| job_title | string | WordPress Developer | The job title – no HTML allowed. |
| job_description | string | | the main description of the job. It can contain the following HTML elements<img><a><strong><em><ul><ol><li> |
| job_short_description | string | A short summary | A string of text to summarise the job. |
| job_source | string | Awesome Job Posting Service | A string representing the source of the job (where it was written). For example Broadbean, LogicMelon or Idibu |
Fields which need mapping
These are fields sent in the data feed from JobAdder 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 node | Data type | Example value | Notes |
|---|---|---|---|
| salary_from | string | 1000 | A number (float) for the lower salary. |
| salary_to | float | 1500 | A number (float) for the upper salary. |
| salary_per | float | PerAnnum | The salary per value. |
| salary | string | 1500 PerAnnum | A combination of the salary_to and salary per fields |
| salary_benefits | string | Laptop & healthcare | Freetext, additional salary information. |
| job_location | string | London, UK | The job locatin string |
| job_type | string | Contract | The job/work type assigned. |
| job_industry | string | IT | The job industry or category assigned. |
| job_sub_category | string | Accounting | The sub category |
| job_bullet_points | string | <ul><li>Point one</li></ul> | The HTML of bullet points added in JobAdder |
| job_jid | string | 1568044 | The internal job id from JobAdder |
| application_email | string | email@domain.com | An email address which applications should be sent to. |
| application_url | string | https://apply.jobadder.com/ref | The JobAdder hosting application form URL for this job. |
Custom fields unique to client feeds
It may be that your unique XML feed to JobRelay from JobAdder contains custom fields. This are usually unique classifications and/or fields.
The are converted to lowercase and spaces replaced with underscores. For example, if you have a custom field with the name of “Display Location”, this will come through in the JobRelay feed named display_location.
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 node | Data type | Example value | Notes |
| geo_lat | float | 53.19339 | The latitude of the job location. |
| geo_long | float | -2.89075 | The longitude of the job location. |
| geo_formatted_address | string | Chester, UK | The formatted address of the location sent. |
| geo_city | string | Chester | The name of the city for the geo located location |
| geo_country_short | string | GB | The shortened country name for the geo located location |
| geo_country_long | string | United Kingdom | The long country name for the geo located location |
| geo_administrative_area_level_2_short | string | Cheshire West and Chester | The short version of the second level administrative area. |
| geo_administrative_area_level_2_long | string | Cheshire West and Chester | The long version of the second level administrative area. |
| geo_administrative_area_level_1_short | string | England | The short version of the first level administrative area. |
| geo_administrative_area_level_1_long | string | England | The 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.