BLUE-COLLAR JOB POSTING API

Job posting data,ready for your API workflow.

Query normalized blue-collar vacancies collected from public employer career sites, without maintaining the collection and normalization pipeline yourself. AI assists with classification and enrichment; it does not generate listings.

Request API sample Inspect the format

22,563 active records Source context retained Snapshot dated 08 Aug 2026

ILLUSTRATIVE API FORMATREAD JOB DATA

GET/v1/jobs?occupation=electrician&city=rotterdam

{
  "job_id": "job_01HX7...",
  "title": "Maintenance Electrician",
  "company": "Example Employer",
  "city": "Rotterdam",
  "occupation": "Electrical trades",
  "first_seen": "2026-08-02",
  "last_seen": "2026-08-08",
  "source_url": "https://example.com/jobs/..."
}

STRUCTURED JSONSOURCE CONTEXT RETAINED

01SOURCE-DIRECT

Public employer career pages

02NORMALIZED

Comparable records and fields

03AI-ENHANCED

Classification and enrichment

04TRACEABLE

Source and observation context

01 / THE BUYER PROBLEM

READ LISTINGS / DO NOT PUBLISH THEM

Build with job listings, not job-board integrations.

Many searches for a job posting API lead to tools that publish vacancies. Blue Collar Job Data is for the other direction: reading public job postings as structured data for products, analysis and workflows.

Tell us what you need

02 / WHAT YOU GET

QUERYABLE JOB DATA

A consistent record layer for products and decisions.

Query the records you need

Scope requests by market, occupation, employer, place and observation date instead of moving an entire dataset.

Follow listing activity

Use first-seen and last-seen observations to understand when a vacancy appeared and when it was most recently found.

Keep the source attached

Preserved source context lets your team inspect the public listing behind a normalized record.

Build with structured JSON

Put consistent job-posting fields into recruitment products, alerts, analytics and internal workflows.

03 / AI-ASSISTED ENHANCEMENT

STRUCTURE THE EVIDENCE

AI helps make the records comparable.

AI assists with occupation classification, location normalization and selected field enrichment. It does not invent vacancies. The source title, source route and observation context remain available so buyers can understand what changed between source and record.

Review the methodology

04 / DATASET ANATOMY

FIELDS THAT REMEMBER THEIR SOURCE

Know what each job record contains.

These representative fields show how original values, classifications and observation history can travel together. Confirm the full field set for your requested delivery.

FIELDTYPEBUYER USE

job_idstring

Stable normalized record identifier

titlestring

Original job title retained from the source

companystring

Employer named on the source listing

citystring

Normalized location for filtering and comparison

occupationstring

Consistent occupation classification

first_seendate-time

First successful source observation

last_seendate-time

Most recent successful source observation

source_urlURL

Route back to the public source page

Need the complete field dictionary?Request a sample package matched to your market and use case.

Get the field list

05 / DELIVERY CHOICE

ONE RECORD LAYER / TWO WORKFLOWS

Choose access around the work you need to do.

JOB POSTING API

Query narrower slices

Best for product features, alerts and workflows that retrieve records by filter or market.

Request API access

BULK JOB DATA

Move larger extracts

Best for warehouse imports, models, research and reproducible market snapshots.

Explore bulk delivery

06 / BUYER OUTCOMES

FROM RECORD TO DECISION

Use the same data layer for different questions.

Recruitment products

Power search, matching, alerts and market-facing product features.

Workforce analytics

Compare skilled and frontline demand across places, employers and occupations.

Hiring signals

Track where employers appear to add, change or remove public vacancies.

Data and AI workflows

Supply normalized, source-linked records to models, agents and automations.

07 / FAQ

QUESTIONS DATA BUYERS ASK

Before you evaluate the job posting API.

Need a field, market or delivery detail that is not covered here? Email the team and include the workflow you are building.

[email protected]

01Does this API read job listings or publish them?

It is designed to supply job-posting data for reading, analysis and software products. It does not send vacancies to job boards or applicant-tracking systems.

02Is the job posting API self-service today?

Public self-service access and documentation are still being prepared. Buyers can request sample records now and discuss a scoped API evaluation with the team.

03How does AI enhance the data?

AI assists with tasks such as occupation classification, location normalization and selected field enrichment. It does not generate job listings, and source evidence remains attached to the record.

04What market is represented in the current snapshot?

The current verified launch snapshot covers the Netherlands. Any sample or commercial discussion should state the market, snapshot date, source definition and known exclusions.

05Can I receive the same job data in bulk?

Yes. Bulk delivery is the better fit when you need a larger extract for a warehouse, model, research project or recurring analysis.

08 / NEXT STEP

START WITH REAL RECORDS

See whether the data fits your product.

Tell us the market, occupations and workflow you want to evaluate. We will use that context to shape the most relevant sample and answer the important coverage questions before a sales call.

Request API sample Review current coverage

SAMPLE REQUEST / INCLUDE

MARKET: Country or region
OCCUPATIONS: Trades or frontline roles
WORKFLOW: Product, analysis or research
DELIVERY: API evaluation

Email [email protected]