> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inploi.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Job Import
> How vacancies flow from your ATS into your inploi careers site.
inploi pulls vacancies from your ATS on a regular schedule and keeps your careers site up to date automatically. You manage roles in the ATS; inploi handles the rest.
## What it does
* **Creates** new listings on your careers site when a role is opened in the ATS.
* **Updates** existing listings when the title, location, description, or salary changes.
* **Expires** listings when a role is closed or filled, so candidates cannot apply to jobs that are no longer available.
Imports run automatically throughout the day — you do not need to trigger them manually.
## How it works
inploi calls your ATS and retrieves the current list of open vacancies.
Each job is matched to a unique key (your ATS job ID + your organisation). New jobs are created; existing jobs are updated with the latest data from the ATS.
Any job that was live in inploi but is no longer returned by the ATS is marked as expired and removed from your careers site.
## What to expect
* Changes made in the ATS (title, salary, location) will appear on your careers site after the next sync — typically within 15 minutes.
* If a job disappears from your site unexpectedly, the most likely cause is that it was closed or removed in the ATS.
* If something looks wrong, contact your Customer Success Manager. inploi has a full log of every import run.
The exact source fields your ATS sends are configured during implementation. The section below describes the job content inploi expects once mapped.
## Field mapping
When jobs are imported, your ATS sends job content that inploi maps into a standard set of fields. The source field names differ between ATSs, but the content itself is the same. This section covers what we need from the ATS — not system fields inploi manages itself, such as internal IDs, timestamps, or map coordinates (which inploi works out from the address).
| Field | Importance | What it is |
| ------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ATS job ID** | Required | The unique identifier for the role in your ATS. inploi uses this to match jobs across syncs — creating new listings, updating existing ones, and expiring roles that are no longer open. |
| **Job title** | Required | The role name shown on your careers site, in search results, and on job board feeds. |
| **Apply URL** | Required | The link candidates use to apply. Without this, there is no application path for the role. Some integrations skip jobs missing any of the required fields. |
| **Job description** | Recommended | The main body of the job page. Drives SEO, job alerts, and feed quality. Jobs can import without one, but the listing will be thin. |
| **Department / category** | Recommended | The team or job family (for example "Retail", "Engineering"). Used for filtering and search. |
| **Employment type** | Recommended | Whether the role is full-time, part-time, contract, and so on. Shown on listings and required for some job board feeds. |
| **Location type** | Recommended | Whether the role is on-site, remote, or hybrid. |
| **Address line 1** | Recommended | Street address or site name. Improves map accuracy. |
| **Town** | Recommended | Town, county, or region. |
| **City** | Recommended | City. |
| **Postcode** | Recommended | Postcode or ZIP code. Important for map accuracy, distance search, and UK Find a Job distribution. Jobs without a postcode are excluded from Find a Job even if they import successfully. |
| **Country** | Recommended | Country name. Used to work out the country code and filter jobs by market. UK Find a Job requires a UK location. |
| **Salary** | Recommended | A single salary figure, or a minimum and maximum for a range. |
| **Pay period** | Recommended | Whether the salary is hourly, weekly, monthly, or annual. Needed for sensible salary display. |
| **Currency** | Recommended | The currency symbol or code (for example £ or GBP). |
| **ATS reference** | Optional | A secondary identifier from the ATS (for example a requisition code), when this differs from the job ID. Useful for support and debugging. |
| **Address line 2** | Optional | Additional address detail. |
| **Contract type** | Optional | Permanent, fixed term, and so on. |
| **Industry** | Optional | Sector or industry label, when the ATS provides it. |
| **Skills** | Optional | Structured skills list, when the ATS provides it. |
| **Number of vacancies** | Optional | How many openings the role has. |
| **Company name** | Optional | Hiring brand or subsidiary name. Defaults to your organisation if not sent. |
| **Company logo** | Optional | Logo URL. Defaults to your organisation logo if not sent. |
| **Custom data** | Optional | Extra fields from the ATS, or values added via the [custom data marker](/integrations/ats/custom-data-from-description) in the job description. |
| **Locale** | Optional | Language or locale code (for example `en-GB`), mainly relevant for multi-language feeds. |
The more precise the location, the more accurate the map pin. Vague location (city only, or postcode only) still imports, but several jobs can end up sharing the same map point. See [how job locations on the map are set](/integrations/ats/job-coordinates). Salary can be hidden on the careers site if your ATS sends a "mask salary" flag.
## Frequently asked questions
Imports usually bring in a job's location as text (address, town, postcode) rather than precise map coordinates. inploi works out the coordinates automatically so jobs can appear on a map and be filtered by distance. If a job is in the wrong place, or you want to understand why several jobs share the same map point, see [how job locations on the map are set](/integrations/ats/job-coordinates).
If your ATS cannot send a field inploi needs, you can add it inside the job description and inploi will pull it into the job's custom data during import — no integration changes required. See [Custom data via the job description](/integrations/ats/custom-data-from-description).