To build a job board from APIs, import listings from job APIs into a jobs custom post type with Ingestics, paginate through the full result set, and refresh on a daily schedule so stale listings do not linger. The connection and mapping work on Free; a usable board needs Lite for the post type, pagination, and scheduling, with Pro adding relevance filters and update sync.

Where does job listing data come from?

Aggregatable sources with public or keyed APIs include Remotive and Arbeitnow (remote/tech jobs, JSON, no key), Adzuna and Jooble (broad coverage, free API keys), plus many ATS and niche-board APIs. Check two things per source:

1. Terms — most job APIs allow aggregation with attribution and a link to the original application page; some require their apply link. Honor both.
2. Fields — you want title, company, location, description, posted date, apply URL, and ideally salary and a stable job ID.

RSS-based job feeds work too — Ingestics handles them as RSS providers in the same pipeline.

How do you set up the jobs post type?

Create a job_listing custom post type and point each provider at it (per-provider post type is Lite). Jobs get their own archive, single template, and search, separate from your blog.

Structured facts go to post meta via Pro’s Advanced Field Mapper: company, location, salary, employment type, apply URL, source job ID — ACF-compatible, and the basis for any filterable job search UI your theme builds.

How do you map listing fields?

Typical JSON mapping:

• title (+ company) → post title (“Senior PHP Developer — Acme”)
• description → content
• company, location, salary, url → meta fields (Pro) or content (Free/Lite)
• publication_date → publish date
• Category/tags from the API → taxonomy (Lite dynamic category mapping; Pro ordered keyword-to-taxonomy rules for consistent filing across sources)
• Company logo URL → featured image; Pro’s fallback media covers logo-less listings

First fetch in Draft mode; check salary formatting and HTML in descriptions before publishing.

How do you fetch the full result set?

Job APIs page their results — 20 to 50 listings per response. Lite’s page/offset pagination walks the pages until the set is complete; Pro adds cursor pagination for token-based APIs and exponential retry for rate-limited ones. Cap total items sensibly: a 300-listing niche board beats a 30,000-listing dump nobody curates.

How do you filter to your niche?

A niche board lives or dies on relevance:

• Query at the API (all tiers) — most job APIs take search, category, and location parameters in the URL; Pro’s query builder manages them as a UI.
• Content filters (Pro) — drop listings missing your keywords, wrong locations, or agencies you exclude.
• Blocked keywords (Business) — brand-safety list at scale.

How do you keep listings fresh and retire dead ones?

Jobs expire fast, and a board full of closed roles kills trust:

• Daily refresh — Lite scheduled fetches; duplicate detection (keyed on the job’s URL/ID) means re-fetched listings do not duplicate.
• Updates in place (Pro) — the Advanced Sync Engine matches by job ID and updates changed listings (salary corrections, reposted closing dates) instead of duplicating them.
• Expiry — map the posted or expiry date to meta and have templates hide listings past an age threshold (30 days is conventional). Items leaving the feed are not auto-deleted, so retirement is a template rule or an editorial pass; Business lifecycle policies automate aging at scale.

How do you display the board?

The job post type’s archive is the board; meta fields drive company, location, and salary display plus any filtering UI. Lite’s [auto_api_feed] shortcode, block, and grid layout cover “Latest jobs” sections; Pro adds Elementor/Bricks support. Pro’s affiliate URL rewriting applies if your sources pay per referred candidate. Shortcode reference in the documentation.

Which Ingestics tier does this build need?

• Free — 3 job APIs, manual fetch, basic mapping. Prototype territory.
• Lite — jobs post type, pagination, daily schedules, category mapping, display. A functioning board.
• Pro — relevance filters, meta/ACF mapping for filterable search, sync updates, cursor pagination, affiliate rewriting.
• Business — blocked keywords, lifecycle policies, unlimited sources.

The sibling build is the property listing site — same CPT-and-sync pattern. Feed-based sources are covered in the XML import guide, and more automated publishing workflows are on the use cases hub.