This page documents all enum values, object structures, and special values used in the Jobven API.

Industries

Filter and classify jobs by industry category. Use the Value column in API queries.

Remote Types

Work arrangement classification for job positions.

Experience Levels

Seniority classification for job positions.

Employment Types

Classification of employment arrangement.

Job Status

Status values differ between query parameters and response fields.

Query Parameter Values

Use these when filtering jobs with the status query parameter:

Response Field Values

Jobs in responses may have these status values:

Education Levels

Required or preferred education qualifications.

Salary Object

Compensation information when available.

{
  "min": 120000,
  "max": 180000,
  "currency": "USD",
  "period": "year"
}

Currency Codes

ISO 4217 currency codes supported:

Salary Periods

Skills Object

AI-enriched skill categorization for job requirements.

{
  "primary_skills": ["React", "TypeScript", "Node.js"],
  "secondary_skills": ["Docker", "AWS", "PostgreSQL"],
  "soft_skills": ["Communication", "Leadership", "Problem-solving"]
}

Skills Filtering

When filtering jobs by skills, the API matches against all skill categories:

GET /v1/public/jobs?skills[]=react&skills[]=typescript

This returns jobs where React OR TypeScript appears in any skill category (primary, secondary, or soft skills).

Benefits

Benefits are returned as a string array of lowercase, underscore-separated tokens extracted from job descriptions. The vocabulary is open rather than a fixed enum, so treat unfamiliar tokens as valid, but in practice virtually every value follows the token form — match on exact strings, not on prose.

["health_insurance", "dental_insurance", "paid_time_off_vacation_personal_days", "remote_work_hybrid_work_options", "pensions_401k"]

The most common tokens are:

Location Object

Geographic location information for job positions.

{
  "streetAddress": "123 Main St",
  "addressLocality": "San Francisco",
  "addressRegion": "California",
  "postalCode": "94105",
  "addressCountry": "US",
  "workLocation": "hybrid"
}

workLocation vs remoteType

• workLocation (in location object): Work arrangement for a specific office location
• remoteType (top-level job field): Overall remote policy for the job

A job may have multiple locations with different workLocation values. The top-level remoteType represents the general policy.

Country Codes

ISO 3166-1 alpha-2 country codes are used for location filtering.

Common Country Codes

Special Value: XX

The code XX means the job carries no location information at all — no city, no region, no street address. These are typically "work from anywhere" postings with no geographic restriction.

GET /v1/public/jobs?country=XX&remoteType[]=remote

XX does not by itself mean the job is remote. Check workLocation (or the top-level remoteType) for that.

When addressCountry is absent

A location can have a city but no addressCountry. That means the job has a known location whose country we could not identify with confidence. Usually the posting names a place that exists in several countries, or a small town we cannot place from the listing alone. We leave the country absent rather than guess, because a wrong country is harder to work around than a missing one.

{
  "addressLocality": "Springfield",
  "workLocation": "onsite"
}

These jobs match no country filter, including country=XX. If you need them, request without a country filter and read addressLocality yourself.

Supported Countries

All 249 ISO 3166-1 alpha-2 country codes are accepted, plus the special value XX.

Language Codes

ISO 639-1 two-letter language codes for job language requirements.

Common Language Codes

All Supported Languages

The API supports 40 language codes: en, fr, es, de, zh, ja, ko, pt, it, ru, ar, hi, nl, sv, no, da, fi, pl, tr, he, id, th, vi, cs, el, hu, ro, uk, bg, hr, fa, ms, tl, bn, ta, te, ur, gu, kn, ml

Travel Percentage

The travelPercentage field indicates required travel as a percentage (0-100).

Timestamps

postedAt and expiresAt are Unix timestamps in seconds, returned as JSON numbers. The postedAfter and postedBefore filters take the same unit.

JavaScript's Date constructor expects milliseconds, so multiply by 1000:

const posted = new Date(job.postedAt * 1000)

Python's datetime.fromtimestamp takes seconds, so no conversion is needed:

from datetime import datetime, timezone
posted = datetime.fromtimestamp(job["postedAt"], tz=timezone.utc)

A value of null means the date is unknown — expiresAt is null for most jobs, since few postings publish a closing date.

Handling Null and Optional Fields

Most response fields are optional and may be null or undefined. Only these fields are guaranteed:

Always Present

• id - Job UUID
• title - Job title
• description - Job description (HTML)
• status - Job status
• companies - Array with at least one company

Often Null

All other fields may be null depending on available data:

• summary, locations, remoteType
• skills, salary, benefits
• experienceLevel, employmentType
• educationRequirement, industry
• minYearsExperience, travelPercentage
• hasVisaSponsorship, hasRelocation, requiresTravel
• inLanguage, postedAt, expiresAt, applyUrl

Safe Access Pattern

Always check for null values before accessing nested properties:

// JavaScript/TypeScript
const salary = job.salary?.min
  ? `$${job.salary.min.toLocaleString()}+`
  : 'Not specified';

const skills = job.skills?.primary_skills?.join(', ') || 'Not listed';

const location = job.locations?.[0]?.addressLocality || 'Location not specified';

# Python
salary = f"${job['salary']['min']:,}+" if job.get('salary', {}).get('min') else 'Not specified'

skills = ', '.join(job.get('skills', {}).get('primary_skills', [])) or 'Not listed'

locations = job.get('locations', [])
location = locations[0].get('addressLocality', 'Location not specified') if locations else 'Location not specified'

Next Steps