# Remote Jobs API (`aspen-technology-labs-inc/remote-jobs-api`) Actor Find remote job postings by country, role, company, category, salary, posting age, employment type, and seniority. Built for remote job boards, recruiting products, and labor-market analysis. - **URL**: https://apify.com/aspen-technology-labs-inc/remote-jobs-api.md - **Developed by:** [Aspen Technology Labs, Inc.](https://apify.com/aspen-technology-labs-inc) (community) - **Categories:** Jobs, Other, Developer tools - **Stats:** 4 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.50 / 1,000 job records This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours, and optionally produces a well-defined JSON output, datasets with results, or files in key-value store. In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server. Actors are written with capital "A". ## How to integrate an Actor? If asked about integration, you help developers integrate Actors into their projects. You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready. The best way to integrate Actors is as follows. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use the [REST API](https://docs.apify.com/api/v2.md). For usage examples, see the [API](#api) section below. For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt). # README ## Remote Jobs API - JobsIndex by Aspen Tech Labs Access real-time remote job postings data through the JobsIndex API, built by Aspen Tech Labs. JobsIndex aggregates 11M+ active job listings daily from over 300K employer source sites worldwide. Job data is sourced directly from company career sites and ATS platforms, not scraped from job boards or aggregators. That means clean data with direct application links where available. This Actor serves two primary use cases: teams that want to publish remote job listings on their platform, and teams that need structured remote jobs data for matching algorithms, AI model training, or workforce intelligence. ### What You Can Use It For - Power a job board, niche remote careers site, or job search feature with fresh, deduplicated remote job postings - Feed a matching platform or recommendation engine with structured remote job data, filterable by role, category, company, or location - Analyze remote hiring demand across markets, employers, and geographies for workforce analytics or competitive intelligence - Collect remote job postings for training datasets, research, or product development ### Built-In Search Preset This Actor is fixed internally to `remote=remote`. The remote/work-arrangement preset is not exposed as an input parameter. Users can narrow the search by country, structured location, role keywords, salary, company, category, posting age, employment type, seniority, and pagination fields. ### Quick Start ```json { "country": "United States", "page": 0, "size": 5 } ```` ### Input Parameters | Parameter | Description | Example | |---|---|---| | `salary` | Salary amount or range filter. | `20h-30h` | | `what` | Main job search query. Supports keywords, boolean logic, exact phrases, and field-targeted search such as `@title engineer` or `@(title,description) (python)`. | `software engineer` | | `where` | Free-text location search. Supports place names, boolean logic, and field-targeted search such as `@country United States` or `@(city,metro_area) (Denver)`. Prefer structured location fields for exact filters. | `Germany` | | `country` | Country filter. | `United States` | | `region` | State, province, or region. | `California` | | `city` | City filter. | `New York` | | `postal_code` | Postal or ZIP code filter. | `90210` | | `metro_area` | Metropolitan area filter. | `Denver-Aurora-Centennial, CO` | | `title` | Job title filter. | `Software Engineer` | | `company_name` | Company name filter. | `IBM` | | `company_domain` | Company website domain. | `ibm.com` | | `category` | Job category. | `Information Technology` | | `sub_category` | More specific job function or role. | `Software Developer` | | `industry` | Company industry filter. | `Food Products` | | `posted` | Relative posting age or ISO date. | `1w` | | `employment_type` | Employment type. | `Full-Time` | | `seniority` | Seniority level. | `Senior` | | `page` | Page number, starting from 0. | `0` | | `size` | Number of results per page. Default 5, min 1, max 100. | `5` | ### Salary Filter Format Use: ```text NUMBER[UNIT] ``` or: ```text NUMBER[UNIT]-NUMBER[UNIT] ``` Supported units: - `h` - per hour - `d` - per day - `w` - per week - `m` - per month - `y` - per year Examples: - `20h-30h` - hourly rate between 20 and 30 - `35h` - fixed hourly rate - `20h-200000y` - range from hourly to yearly comparison ### Advanced Filters `what` and `where` support plain-text search, boolean logic, and field-targeted search. If no field is provided, the API expands the search across a default set of relevant fields. Plain keyword examples: ```text what = engineer OR manager where = United States ``` Field-specific examples: ```text what = @title engineer OR manager where = @country United States ``` Multi-field examples: ```text what = @(title,description) (python) what = @(title,title_raw,description) (engineer OR manager) what = @(title,description) (python AND developer) where = @(country,region,city,metro_area,county,sub_city) (United States) where = @(city,region,metro_area) (San Francisco OR California) where = @(city,region,metro_area) (California) ``` When using `where`, avoid sending separate structured location parameters for the same request unless you want those structured parameters to take priority. For example, `country`, `region`, `city`, `postal_code`, and `metro_area` can override or narrow `where`. Common job/content fields for `what`: - `title`, `title_raw`, `description`, `reference` - `category`, `sub_category`, `seniority`, `industry`, `company_type` - `company_name`, `company_domain`, `company_name_raw` - `employment_type`, `remote`, `language` - `posted`, `posted_raw`, `expired` - `url_source`, `url_apply` - `salary_value`, `salary_currency`, `salary_unit` - `id` Common location fields for `where`: - `country`, `region`, `city`, `metro_area`, `county`, `sub_city`, `postal_code` ### Limits and Pagination This Actor uses the JobsIndex jobs API. Results are paginated with `page` and `size`. | Parameter | Default | Min | Max | |---|---:|---:|---| | `page` | 0 | 0 | Depends on `size` and the item cap | | `size` | 5 | 1 | 100 | Invalid `page` or `size` values can return `400 Invalid page or size parameters`. #### Item Caps The maximum number of retrievable jobs depends on the query shape: | Query shape | Max items | Effective max `size` | Over-size behavior | |---|---:|---:|---| | No company filter | 1000 | 100 | Validation error; not silently capped | | Company filter plus another keyword or filter | 20 | 20 | Silent cap with capping metadata | | Company filter only | 5 | 5 | Silent cap with capping metadata | A company filter means `company_name`, `company_domain`, or a company field referenced inside `what`. Another keyword or filter means anything in `what` other than `company_*`, or a value in fields such as `title`, `category`, `sub_category`, `industry`, `posted`, `salary`, `employment_type`, or `seniority` where available on this Actor. When a company-filtered request asks for `size` greater than the effective cap, the API returns up to the capped number of results instead of erroring. The response metadata includes: - `size_requested` - the original requested `size` - `size_capped_by` - `"company"` for the 5-item cap or `"company|keywords"` for the 20-item cap On uncapped responses, `size_requested` and `size_capped_by` are not present. No-company-filter requests are not silently capped. If the request exceeds the 1000-item retrieval window, the API can return `400 Item limit reached. Maximum of 1000 items can be retrieved`. #### Free-Text Query Limits `what` and, where available, `where` support advanced matching syntax but have safety limits: | Limit | Value | Error behavior | |---|---:|---| | Raw URL length before decoding | 700 characters | `400 'what' or 'where' parameters exceed 700 characters` | | Decoded text length | 500 characters | `400 MATCH input exceeds length limit` | | Combined operator characters: `?`, `+`, pipe, `@` | 20 | `400 Too many MATCH operators` | | Unsafe SQL-like keywords | blocked | `400 Unsafe MATCH expression` | Unsupported characters may be normalized before search. Unbalanced quotes and trailing `@` characters may be stripped. #### Field Validation Invalid filter values can return `400 Invalid value for parameter: `. Common validation examples include malformed company domains, invalid dates or relative `posted` values, invalid salary format, invalid job IDs, unsupported location formats, or overly long field values. #### ID Lookup Shortcut When `id` is provided, the search query is bypassed and the API returns the matching job record or records. Job IDs must be numeric; otherwise the API returns `400 Invalid job id format`. ### Output Each run stores job records in the default Apify dataset. The dataset schema includes an `Overview` table for the most useful fields and a `Raw data (all fields)` table for the complete JobsIndex record. Common fields include `id`, `title`, `title_raw`, `category`, `sub_category`, `company_name`, `company_domain`, `country`, `region`, `city`, `metro_area`, `salary_value`, `salary_currency`, `salary_unit`, `employment_type`, `remote`, `posted`, `expired`, `url_source`, `url_apply`, and `description`. Field availability depends on the source job posting. ### Custom Remote Jobs Data For custom job data needs, including custom job scraping of specific companies or tailored job feeds, contact us via [JobsIndex](https://jobsindex.com/) or by [email](mailto:inquiry+apify@aspentechlabs.com). You can also explore [JobMarketPulse](https://jobmarketpulse.com/), our next-generation labor and job market intelligence platform. # Actor input Schema ## `id` (type: `string`): Optional job ID filter. Use a specific JobsIndex job ID to retrieve known job records. ## `what` (type: `string`): Main job search query. Supports keywords, exact phrases, boolean logic (AND, OR, NOT or &, |, !), and field targeting. Examples: python developer OR junior javascript, "data scientist", @(title) (manager), @(title,description) (python), @(company\_name) ((="google, inc.") OR (microsoft AND corporation)). ## `where` (type: `string`): Location filter. Supports place names, boolean logic, and location field targeting. Examples: Germany, San Francisco, @(address\_city) ((San Francisco) OR (Palo Alto)), @(address\_country) ((Germany) OR (Austria)). ## `country` (type: `string`): Country for job location filter. ## `region` (type: `string`): Region, state, or province. ## `city` (type: `string`): City filter. ## `postal_code` (type: `string`): Postal or ZIP code. ## `metro_area` (type: `string`): Metropolitan area filter. ## `title` (type: `string`): Job title filter. ## `company_name` (type: `string`): Company name filter. ## `company_domain` (type: `string`): Company website domain, for example ibm.com. ## `category` (type: `string`): Job category, for example Healthcare or Retail. ## `sub_category` (type: `string`): More specific job function. ## `industry` (type: `string`): Company industry. ## `posted` (type: `string`): Relative posting age. Examples: 1h, 1d, 1w, 1m. ## `salary` (type: `string`): Salary amount/range filter. Examples: 20h-30h, 35h, 20h-200000y. ## `employment_type` (type: `string`): Employment type, for example Full-Time or Part-Time. ## `seniority` (type: `string`): Seniority level, for example Junior, Middle, Senior. ## `page` (type: `integer`): Page number. Starts from 0. ## `size` (type: `integer`): Number of results per page. Maximum 100. ## Actor input object example ```json { "id": "", "what": "", "where": "", "country": "United States", "region": "", "city": "", "postal_code": "", "metro_area": "", "title": "", "company_name": "", "company_domain": "", "category": "", "sub_category": "", "industry": "", "posted": "", "salary": "", "employment_type": "", "seniority": "", "page": 0, "size": 5 } ``` # Actor output Schema ## `results` (type: `string`): No description ## `meta` (type: `string`): No description # API You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup. ## JavaScript example ```javascript import { ApifyClient } from 'apify-client'; // Initialize the ApifyClient with your Apify API token // Replace the '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = {}; // Run the Actor and wait for it to finish const run = await client.actor("aspen-technology-labs-inc/remote-jobs-api").call(input); // Fetch and print Actor results from the run's dataset (if any) console.log('Results from dataset'); console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`); const { items } = await client.dataset(run.defaultDatasetId).listItems(); items.forEach((item) => { console.dir(item); }); // 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs ``` ## Python example ```python from apify_client import ApifyClient # Initialize the ApifyClient with your Apify API token # Replace '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = {} # Run the Actor and wait for it to finish run = client.actor("aspen-technology-labs-inc/remote-jobs-api").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{}' | apify call aspen-technology-labs-inc/remote-jobs-api --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=aspen-technology-labs-inc/remote-jobs-api", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Remote Jobs API", "description": "Find remote job postings by country, role, company, category, salary, posting age, employment type, and seniority. Built for remote job boards, recruiting products, and labor-market analysis.", "version": "0.1", "x-build-id": "UKpzrUBiHj7I2JHLK" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/aspen-technology-labs-inc~remote-jobs-api/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-aspen-technology-labs-inc-remote-jobs-api", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/aspen-technology-labs-inc~remote-jobs-api/runs": { "post": { "operationId": "runs-sync-aspen-technology-labs-inc-remote-jobs-api", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/aspen-technology-labs-inc~remote-jobs-api/run-sync": { "post": { "operationId": "run-sync-aspen-technology-labs-inc-remote-jobs-api", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "id": { "title": "Job ID", "type": "string", "description": "Optional job ID filter. Use a specific JobsIndex job ID to retrieve known job records.", "default": "" }, "what": { "title": "Job search query", "type": "string", "description": "Main job search query. Supports keywords, exact phrases, boolean logic (AND, OR, NOT or &, |, !), and field targeting. Examples: python developer OR junior javascript, \"data scientist\", @(title) (manager), @(title,description) (python), @(company_name) ((=\"google, inc.\") OR (microsoft AND corporation)).", "default": "" }, "where": { "title": "Location search query", "type": "string", "description": "Location filter. Supports place names, boolean logic, and location field targeting. Examples: Germany, San Francisco, @(address_city) ((San Francisco) OR (Palo Alto)), @(address_country) ((Germany) OR (Austria)).", "default": "" }, "country": { "title": "Country", "type": "string", "description": "Country for job location filter.", "default": "United States" }, "region": { "title": "Region", "type": "string", "description": "Region, state, or province.", "default": "" }, "city": { "title": "City", "type": "string", "description": "City filter.", "default": "" }, "postal_code": { "title": "Postal code", "type": "string", "description": "Postal or ZIP code.", "default": "" }, "metro_area": { "title": "Metro area", "type": "string", "description": "Metropolitan area filter.", "default": "" }, "title": { "title": "Job title", "type": "string", "description": "Job title filter.", "default": "" }, "company_name": { "title": "Company name", "type": "string", "description": "Company name filter.", "default": "" }, "company_domain": { "title": "Company domain", "type": "string", "description": "Company website domain, for example ibm.com.", "default": "" }, "category": { "title": "Category", "type": "string", "description": "Job category, for example Healthcare or Retail.", "default": "" }, "sub_category": { "title": "Sub-category", "type": "string", "description": "More specific job function.", "default": "" }, "industry": { "title": "Industry", "type": "string", "description": "Company industry.", "default": "" }, "posted": { "title": "Posted time frame", "type": "string", "description": "Relative posting age. Examples: 1h, 1d, 1w, 1m.", "default": "" }, "salary": { "title": "Salary filter", "type": "string", "description": "Salary amount/range filter. Examples: 20h-30h, 35h, 20h-200000y.", "default": "" }, "employment_type": { "title": "Employment type", "type": "string", "description": "Employment type, for example Full-Time or Part-Time.", "default": "" }, "seniority": { "title": "Seniority", "type": "string", "description": "Seniority level, for example Junior, Middle, Senior.", "default": "" }, "page": { "title": "Page number", "minimum": 0, "type": "integer", "description": "Page number. Starts from 0.", "default": 0 }, "size": { "title": "Page size", "minimum": 1, "maximum": 100, "type": "integer", "description": "Number of results per page. Maximum 100.", "default": 5 } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```