# OnlineJobs.ph Scraper (`inatanli/onlinejobs-ph-scraper`) Actor

Extract job postings from OnlineJobs.ph — the largest marketplace for hiring Filipino virtual assistants and remote workers. Search by keyword, set how many pages to crawl, and get back a structured dataset ready for export.

- **URL**: https://apify.com/inatanli/onlinejobs-ph-scraper.md
- **Developed by:** [Ina Li](https://apify.com/inatanli) (community)
- **Categories:** Jobs
- **Features:** Limited permissions
- **Stats:** 168 total users, 24 monthly users, 100.0% runs succeeded, 4 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.90 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## OnlineJobs.ph Scraper

OnlineJobs.ph doesn't offer a public API, but this scraper acts as an unofficial **OnlineJobs.ph API** to help you extract the job data you need, when you need it, and at scale. Just type in a search keyword, set how many pages to crawl, and get clean, structured job listings exported in the format of your choice.

Built with [Crawlee](https://crawlee.dev/python/) (BeautifulSoup parser + httpx client) and deployed as an [Apify](https://apify.com/) Actor.

### What does OnlineJobs.ph Scraper do?

OnlineJobs.ph Scraper extracts job postings from [OnlineJobs.ph](https://www.onlinejobs.ph) — the largest marketplace for hiring Filipino virtual assistants and remote workers — and exports them into JSON, CSV, Excel, or HTML. You can then use this data in your own data projects, hiring pipelines, market reports, and applications.

- 🔎 Search **any keyword** (e.g. `virtual assistant`, `gtm`, `seo`) — or leave it blank to scrape all jobs
- 📄 Scrape job listings across **multiple search-result pages** (30 jobs per page)
- 🧾 Extract job title, employer, employment type, salary, posted date, description, and required skills
- 📝 Get **full job descriptions** by default, or switch `fetchDetails` off for a run that is ~30x faster
- ⚡ In fast mode a whole page of 30 jobs costs a single request, so a 5-page crawl finishes in seconds
- 📤 Export data in multiple formats: JSON, CSV, Excel, or HTML
- 🔌 Connect to any AI chatbot or workflow using the Apify API, MCP server, webhooks, and SDKs (Python & Node.js)

### What data can you get from OnlineJobs.ph?

|                      |                         |                     |
| -------------------- | ----------------------- | ------------------- |
| 🧑‍💼 Job title         | ⏱ Employment type       | 💵 Salary           |
| 📅 Date posted       | 📅 Date last updated    | 🏷️ Required skills  |
| 📝 Description       | 🏢 Employer name        | 🔗 Job detail URL   |

> **Note:** `employerName` is only available for employers who have uploaded a logo (roughly 15% of postings) — it comes from the logo's alt text on the search results. The employer section on the job page itself is behind a login wall, so there is no way to fill it in for the rest.

### Why scrape OnlineJobs.ph?

- 🕵️ Research the Filipino remote-work and VA market by role, salary, and recency
- 📈 Monitor hiring trends and in-demand skills over time
- 💸 Benchmark salaries across roles and employment types
- 🗂 Build a custom database of available positions
- 🤺 Track competitors' job postings and hiring activity
- 📩 Feed an automated job-search or lead-generation pipeline

### How to use OnlineJobs.ph Scraper

OnlineJobs.ph Scraper is built for an easy start, even if you've never scraped before:

1. Create a free [Apify account](https://console.apify.com/sign-up) using your email.
2. Open OnlineJobs.ph Scraper.
3. Enter a **Job Keyword** and the **Max Pages** you want to crawl. Untick **Fetch full job descriptions** if you don't need the untruncated description — the run gets about 30x faster.
4. Click **Start** and wait for the data to be extracted.
5. Download your data in JSON, CSV, Excel, HTML, or XML.

### Input

The input is a simple JSON object. OnlineJobs.ph Scraper recognizes the following parameters:

| Parameter    | Type    | Required | Default | Description                                                         |
| ------------ | ------- | -------- | ------- | ------------------------------------------------------------------- |
| `jobKeyword`   | string  | No       | —       | Search keyword (e.g. `virtual assistant`, `gtm`). Blank = all jobs.  |
| `maxPages`     | integer | No       | `5`     | Maximum search-result pages to crawl (30 jobs per page).             |
| `fetchDetails` | boolean | No       | `true`  | Open each job's page for `fullDescription` and `dateUpdated`. Costs 31 requests per page instead of 1; set to `false` for a much faster run. |

#### Input example

```json
{
  "jobKeyword": "virtual assistant",
  "maxPages": 3,
  "fetchDetails": true
}
```

### Output

The results are wrapped into a dataset you can find in the **Storage** tab and access via the API. Each scraped job is a separate item in the dataset.

You can manage the results in any language (Python, PHP, Node.js). See the [API reference](https://docs.apify.com/api/v2) to learn more about getting results from this Actor.

#### Scraped OnlineJobs.ph job listings

The structure of each item looks like this:

```json
{
  "jobUrl": "https://www.onlinejobs.ph/jobseekers/job/Virtual-Assistant-1234567",
  "jobTitle": "Executive Virtual Assistant",
  "employerName": "Acme Remote Staffing",
  "employmentType": "Full Time",
  "salary": "$4-6 per hour",
  "datePosted": "2026-05-31",
  "dateUpdated": "2026-05-31",
  "descriptionSnippet": "We are looking for an experienced executive virtual assistant to manage calendars, handle email, and support day-to-day...",
  "fullDescription": "We are looking for an experienced executive virtual assistant to manage calendars, handle email, and support day-to-day operations...",
  "skills": ["Email Management", "Calendar Management", "Customer Support"]
}
```

#### Output fields

Every record carries the same keys regardless of input, so the dataset schema is stable across runs.

| Field                | Type           | Description                                                                    |
| -------------------- | -------------- | ------------------------------------------------------------------------------ |
| `jobUrl`             | string (URL)   | Canonical job detail URL                                                       |
| `jobTitle`           | string         | Job title                                                                      |
| `employerName`       | string | null | Employer name; `null` unless the employer uploaded a logo                      |
| `employmentType`     | string         | `Full Time`, `Part Time`, `Gig`, or `Any`                                      |
| `salary`             | string | null | Raw salary string (e.g. `$4-6 per hour`); `null` if absent                     |
| `datePosted`         | string         | Date posted, ISO `YYYY-MM-DD`                                                  |
| `dateUpdated`        | string | null | Date last updated, ISO `YYYY-MM-DD`. `null` if `fetchDetails` is off           |
| `descriptionSnippet` | string         | First ~300 characters of the description, as shown on the search results       |
| `fullDescription`    | string | null | Complete description, `<ojfilter>` tags stripped. `null` if `fetchDetails` is off |
| `skills`             | string\[]       | Listed skills / top-skill labels; empty if the posting has none                |

### During the run

The scraper reads most fields straight off the search-results pages, which already carry the title, employer, employment type, salary, posted date, skills, and a description snippet for all 30 jobs in **a single request per page**.

With `fetchDetails` on (the default), it adds a second phase that opens each job's own page for the two fields the results page can't give you — the untruncated `fullDescription` and `dateUpdated`. That costs **31 requests per page instead of 1**: roughly 30 seconds per page, so a 5-page run takes about 3 minutes. Make sure the Actor's run timeout has room for it, or switch `fetchDetails` off to get the same run in seconds without those two fields.

The crawler caps itself at **60 requests/minute across 5 workers**. OnlineJobs.ph publishes `Crawl-delay: 5` in its `robots.txt`; the listing-first design means a default crawl now makes *far* fewer requests in total than the old one-request-every-5-seconds approach did, while finishing in seconds rather than minutes.

Jobs whose detail page has been deleted (HTTP 410 or a 404 body) are skipped rather than recorded as empty rows.

### Integrations

You can connect OnlineJobs.ph Scraper with almost any cloud service or web app. Apify offers integrations with Make, Zapier, Slack, Google Sheets, Google Drive, GitHub, and more, plus webhooks to trigger actions whenever a run finishes.

#### Using the Apify API

The [Apify API](https://docs.apify.com/api/v2) gives you programmatic access to run the Actor, schedule it, and fetch results. Use the [`apify-client`](https://docs.apify.com/api/client/js/) NPM package for Node.js or the [`apify-client`](https://docs.apify.com/api/client/python/) PyPI package for Python.

#### Using an MCP server

With the Apify API you can use this Actor through an MCP server and connect it to clients like Claude Desktop, or build your own. Read more about [setting up Apify Actors with MCP](https://docs.apify.com/platform/integrations/mcp).

### Is it legal to scrape OnlineJobs.ph?

This scraper only collects data that employers have chosen to publish publicly, and it rate-limits itself. It does not extract data behind the login wall (such as employer contact details).

# Actor input Schema

## `jobKeyword` (type: `string`):

Search keyword (e.g. virtual assistant, gtm). Leave blank to return all jobs.

## `maxPages` (type: `integer`):

Maximum number of search result pages to crawl (30 jobs per page).

## `fetchDetails` (type: `boolean`):

Open every job's detail page to get the untruncated description and the date it was last updated. This costs one extra request per job (31 instead of 1 per page), so a crawl takes roughly 30x longer. Turn it OFF for a much faster run that still returns every other field, including a truncated description snippet, from the search results alone.

## Actor input object example

```json
{
  "jobKeyword": "virtual assistant",
  "maxPages": 5,
  "fetchDetails": true
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset items containing scraped job postings (jobUrl, jobTitle, employerName, employmentType, salary, datePosted, dateUpdated, descriptionSnippet, fullDescription, skills). dateUpdated and fullDescription are populated only when the fetchDetails input is enabled.

# 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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "jobKeyword": "virtual assistant",
    "maxPages": 5,
    "fetchDetails": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("inatanli/onlinejobs-ph-scraper").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 '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "jobKeyword": "virtual assistant",
    "maxPages": 5,
    "fetchDetails": True,
}

# Run the Actor and wait for it to finish
run = client.actor("inatanli/onlinejobs-ph-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "jobKeyword": "virtual assistant",
  "maxPages": 5,
  "fetchDetails": true
}' |
apify call inatanli/onlinejobs-ph-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,inatanli/onlinejobs-ph-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/pfZg6cAdIOfE7oYis/builds/c6SV7Fm8dTaLUl6EW/openapi.json