# Changelog of Advanced LinkedIn Job Search API (`fantastic-jobs/advanced-linkedin-job-search-api`) Actor

- **URL**: https://apify.com/fantastic-jobs/advanced-linkedin-job-search-api/changelog.md
- **Full Actor documentation**: https://apify.com/fantastic-jobs/advanced-linkedin-job-search-api.md

## Changelog

### 2026-06-22 — New filter parameters

Added four new input parameters, matching the latest API:

- **AI Language** (`aiLanguageFilter`) — filter by the AI-detected language of the job description (matches `ai_job_language`).
- **Company Size** (`organizationSizeFilter`) — filter by LinkedIn company-size bucket (e.g. `51-200`; matches `org_linkedin_size`).
- **Industry Exclusion Filter** (`industryExclusionFilter`) — exclude jobs from specific LinkedIn industries.
- **Has No Location** (`hasNoLocation`) — return only jobs with no normalized location (`locations_derived` is null).

> **Update (2026-06-22): all changes in this changelog have now been applied.** The migration to the v1 API is complete — new field and parameter names are live, the deprecated renamed output fields have been removed, and the `old-api` build has been retired. Please make sure your integration uses the new names.

### New Fantastic.jobs API

We're launching our new API on [Fantastic.jobs](https://developer.fantastic.jobs)! This comes with some changes to this Apify Actor as well. Please review the changes below carefully.

Some features of our new API are not available on Apify. Also, if you're retrieving more than 20,000 jobs per month, the API will likely be a better deal:

- ATS, LinkedIn, Y Combinator, and Wellfound jobs combined under a single plan
- Expired jobs endpoints with hourly refresh, compared to daily refresh on Apify
- Endpoints to count the number of jobs before retrieving them
- Advanced filtering parameters with Boolean search for job title, location, and description
- Much faster response times

If you're interested, start building with the new API: [developer.fantastic.jobs](https://developer.fantastic.jobs)
If not, please carry on below!

### Timeline

#### On 2026-06-08

- All field and parameter changes in this changelog will be applied.
- **If you need more time to switch your infrastructure to accommodate the changes, especially the new `id` format, change the Actor Build to `old-api`.** See Apify's [Builds documentation](https://docs.apify.com/platform/actors/running/runs-and-builds) for how to choose a build. This is the current version of the Actor, and we will keep it active for two additional weeks until 2026-06-22.
- Renamed fields will stay active under both the old and new names until 2026-06-22, so you can use both fields at the same time during the transition. This overlap period is only for name changes; removed fields, including `remote_derived` and `external_apply_url`, will be removed on 2026-06-08.

#### On 2026-06-22

- The `old-api` build and deprecated renamed fields will be removed per this changelog.

### Breaking change: `id` is now an integer

The `id` field now returns as an integer instead of a stringified number. If your integration stores IDs as strings, validates response schemas, or compares IDs without type coercion, update that logic before 2026-06-08, or keep using the old built 'old-api' until 2026-06-22 the latest.

Important: `id` was already stored as an integer in the expired endpoints.

### Removed input parameters

The following organization-description search parameters will be removed on 2026-06-08:

- `organizationDescriptionSearch`
- `organizationDescriptionExclusionSearch`

The following external-apply URL parameters will also be removed on 2026-06-08:

- `externalApplyUrl`
- `populateExternalApplyURL`

### Removed input parameter: `includeAi`

The `includeAi` input parameter will be removed on 2026-06-08. AI-enriched fields will be included by default.

### Deprecated input parameters

`EmploymentTypeFilter` will be deprecated in favor of `aiEmploymentTypeFilter` on 2026-06-08.

`aiHasSalary` will become `hasSalary` on 2026-06-08. `aiHasSalary` will remain available as a deprecated alias with the same functionality.

`remote` will be deprecated in favor of `aiWorkArrangementFilter` on 2026-06-08. When enabled, it is translated to `ai_work_arrangement` (`Remote OK` and `Remote Solely`). It is ignored if you set `aiWorkArrangementFilter` explicitly. `remote` will remain available as a deprecated alias with the same functionality.

### Removed output fields

**`remote_derived` will be removed.** Use `ai_work_arrangement` instead.

**`external_apply_url` will be removed** due to being no longer available

### Renamed output fields

| Current field | New field |
| --- | --- |
| `date_validthrough` | `date_valid_through` |
| `locations_raw` | `locations` |
| `location_requirements_raw` | `location_requirements` |
| `salary_raw` | `salary` |
| `ai_salary_minvalue` | `ai_salary_min_value` |
| `ai_salary_maxvalue` | `ai_salary_max_value` |
| `ai_salary_unittext` | `ai_salary_unit_text` |
| `ai_education_requirements` | `ai_education` |
| `directapply` | `direct_apply` |
| `linkedin_org_employees` | `org_linkedin_headcount` |
| `linkedin_org_url` | `org_linkedin_website` |
| `linkedin_org_size` | `org_linkedin_size` |
| `linkedin_org_slogan` | `org_linkedin_slogan` |
| `linkedin_org_industry` | `org_linkedin_industry` |
| `linkedin_org_followers` | `org_linkedin_followers` |
| `linkedin_org_headquarters` | `org_linkedin_headquarters` |
| `linkedin_org_type` | `org_linkedin_type` |
| `linkedin_org_foundeddate` | `org_linkedin_founded_date` |
| `linkedin_org_specialties` | `org_linkedin_specialties` |
| `linkedin_org_locations` | `org_linkedin_locations` |
| `linkedin_org_description` | `org_linkedin_description` |
| `linkedin_org_slug` | `org_linkedin_slug` |
| `linkedin_org_recruitment_agency_derived` | `org_linkedin_recruitment_agency_derived` |

- `linkedin_id` will be returned as a number instead of text.

### New output fields

- `ai_employment_type` - Employment type as derived from the job description.