🧑‍💻 Manatal (careers-page.com) Job Feed — Any Employer Board

One structured job_record per public posting on a Manatal employer board. You supply a tenant (or list of tenants); the actor reads that board's public server-rendered page. Public, logged-out, robots-honoured.

Difference: each record carries the posting title, location, and department from the tenant’s server-rendered Manatal (careers-page.com) board, deduped by job id; company_name is the board owner, and only real openings are billed.

Output is one job_record row per result; billing is pay-per-event, the value event being one job record (a $0.02 start fee per run, then $0.05 per job record).

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

📊 Sample Output

Real rows from run nInQh95btm3Xxsfn1 on build 0.1.9 (2026-09-17), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

tenant	company_name	source_job_id	title	location	url
1st-jobscom	1st-jobscom	3WR9Y7XV	Technical Sales Executive – Flooring & Fit-Out Solutions	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/3WR9Y7XV
1st-jobscom	1st-jobscom	8X5379RV	Flooring Sales Executives	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/8X5379RV
1st-jobscom	1st-jobscom	4RR389W5	Customer Success Executive	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/4RR389W5
1st-jobscom	1st-jobscom	RYY87X3R	Admin / Listing Executive	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/RYY87X3R
1st-jobscom	1st-jobscom	X963V3Y3	Administrator Property Listing	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/X963V3Y3
1st-jobscom	1st-jobscom	V665Y978	Property Consultant (Rental)	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/V665Y978
1st-jobscom	1st-jobscom	6337V5X5	Senior Credit Underwriting Specialist (RNPL)	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/6337V5X5
1st-jobscom	1st-jobscom	X99RYVR3	Credit & Collection Officer (RNPL)	Dubai, United Arab Emirates	https://www.careers-page.com/1st-jobscom/job/X99RYVR3

The run finished with the status message: NORMAL: 20 postings across 1 tenant board(s) (0 duplicates collapsed). job_record billable=20 [requested_cap=20, delivered=20]

✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is null):

• tenant (string/null) — e.g. 1st-jobscom
• company_name (string/null) — e.g. 1st-jobscom
• source_platform (string/null) — e.g. manatal
• source_job_id (string/null) — e.g. 3WR9Y7XV
• title (string/null) — e.g. Technical Sales Executive – Flooring & Fit-Out Solutions
• department (string/null) — null in every sample row
• location (string/null) — e.g. Dubai, United Arab Emirates
• city (string/null) — null in every sample row
• state (string/null) — null in every sample row
• country (string/null) — null in every sample row
• is_remote (boolean/null) — null in every sample row
• employment_type (string/null) — null in every sample row
• url (string/null) — e.g. https://www.careers-page.com/1st-jobscom/job/3WR9Y7XV
• posted_at (string/null) — null in every sample row
• source_url (string/null) — e.g. https://www.careers-page.com/1st-jobscom
• record_type (string) — e.g. job_record
• source (string/null) — e.g. manatal-job-feed
• observed_at (string/null) — e.g. 2026-09-17T17:34:43Z
• terminal (string/null) — null in every sample row
• platform (string/null) — null in every sample row
• tenants_requested (integer/null) — null in every sample row
• tenants_ok (integer/null) — null in every sample row
• tenants_blocked (integer/null) — null in every sample row
• tenants_empty (integer/null) — null in every sample row
• tenants_error (integer/null) — null in every sample row
• raw_seen (integer/null) — null in every sample row
• duplicates (integer/null) — null in every sample row
• unique_found (integer/null) — null in every sample row
• delivered (integer/null) — null in every sample row
• reconcile (array/null) — null in every sample row
• per_tenant (array/null) — null in every sample row

What you get

One job_record per live opening, deduplicated on the source-native job id (scoped per tenant). Fields the board does not publish are honest null. A run_receipt carries per-tenant counts.

Every run also writes a RUN_RECEIPT record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

⚙️ Sample inputs

1. Quick start — the Store example (this is what the sample above came from)

{
  "tenants": [
    "1st-jobscom"
  ],
  "maxRecords": 20
}

The sample run charged exactly: 1 × $0.02 apify-actor-start + 20 × $0.05 job_record = $1.02 on the Free tier — every delivered row was billed.

2. A smaller, narrowed run

{
  "tenants": [
    "1st-jobscom"
  ],
  "maxRecords": 5
}

Caps the run at 5 rows — about $0.27 on the Free tier ($0.02 start + 5 × $0.05).

3. A full-size run

{
  "tenants": [
    "1st-jobscom"
  ],
  "maxRecords": 5000
}

Up to 5000 rows (the schema default for maxRecords) — about $250.02 on the Free tier ($0.02 start + 5000 × $0.05) if the source has that many.

🧾 JSON sample record

One real record from run nInQh95btm3Xxsfn1, exactly as it lands in the dataset (emails masked, long text shortened):

{
  "tenant": "1st-jobscom",
  "company_name": "1st-jobscom",
  "source_platform": "manatal",
  "source_job_id": "3WR9Y7XV",
  "title": "Technical Sales Executive – Flooring & Fit-Out Solutions",
  "department": null,
  "location": "Dubai, United Arab Emirates",
  "city": null,
  "state": null,
  "country": null,
  "is_remote": null,
  "employment_type": null,
  "url": "https://www.careers-page.com/1st-jobscom/job/3WR9Y7XV",
  "posted_at": null,
  "source_url": "https://www.careers-page.com/1st-jobscom",
  "record_type": "job_record",
  "source": "manatal-job-feed",
  "observed_at": "2026-09-17T17:34:43Z"
}

🔧 How it works

Transport. Plain HTTPS from the Apify platform, no proxy. robots.txt is read first and a disallowed path is never fetched. Every request carries an identified contact User-Agent.

Terminal states. A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

Charging. Each job record is charged at the moment it is pushed (job_record); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

How it behaves

Each tenant board is fetched only if robots allows. A blocked or errored board bills nothing; if every requested board is blocked the run fails loudly. Empty tenants deliver nothing and bill nothing. maxRecords caps the count.

What is not done. No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

⏰ Set it on a schedule

A single run is a snapshot. The value is the feed: open the actor in Apify Console → Schedules → Create new, add this actor with the input you want, and pick a cadence:

• Daily — 0 7 * * * (07:00 UTC): catch changes within a day.
• Weekly — 0 7 * * 1: a Monday digest.

Each run is independent; keep the same input on the schedule so the results stay comparable. Schedules can also POST results to a webhook (Console → Integrations).

💰 Pricing example

Event	Free	Bronze	Silver	Gold
Actor Start (apify-actor-start)	$0.02	$0.02	$0.02	$0.02
Job Record (job_record)	$0.05	$0.04	$0.04	$0.03

Worked at the live Free-tier price:

• 8 job records: $0.02 start + 8 × $0.05 = $0.42
• 25 job records: $0.02 start + 25 × $0.05 = $1.27
• 5000 job records: $0.02 start + 5000 × $0.05 = $250.02

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: NORMAL: 20 postings across 1 tenant board(s) (0 duplicates collapsed). job_record billable=20 [requested_cap=20, delivered=20]. maxRecords is a hard ceiling on what is delivered and billed, never a target.

⚖️ Legal & ToS

This actor reads public data only. It collects only what the source publishes to any visitor, keeps to the source's robots rules (checked on every run), identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

❓ FAQ

Q: Do I need an API key or a login?
A: No. the input schema has no key field and the actor carries no secrets.

Q: Why did my run return 0 rows?
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

Q: How many rows can one run return?
A: Up to maxRecords (default 5000). Raise the cap for a bigger run; you pay per delivered row.

Q: How fresh is the data?
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

Q: What formats can I export?
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

Q: How is this different from the other ATS job feeds actors?
A: Same output shape and billing model; this one covers Manatal (careers-page.com) Job Feed — Any Employer Board. The siblings under Related Actors cover the other sources or slices — run several on one schedule for a combined feed.

Q: Are there rate limits?
A: The actor paces itself against the source and honours its robots rules; there is no per-buyer limit beyond your Apify plan's concurrency.

🆘 Troubleshooting

• Run FAILED with BLOCKED → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
• Status says CAPPED → your cap (maxRecords) was reached → raise it for a bigger run.
• Input validation error on start → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
• Run TIMED-OUT → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

🔗 Related Actors

• Jobvite Job Feed — Any Employer Board — One structured jobrecord per public posting on a Jobvite employer board. You supply a tenant (or list of tenants); the actor reads that board's publi…
• Keka Careers Jobs Exporter — One structured job record per active opening from employer career portals powered by Keka Hire — title, company, location, apply link. Keyless, logge…
• LinkedIn Job Postings API — Public Hiring Data — Query public LinkedIn job postings by role, location, employment type, and posting age. Receive normalized records through an Apify dataset or API. P…
• Oracle Recruiting Jobs Exporter — One structured job record per open requisition across Oracle Recruiting Cloud career sites, read from the keyless candidate-experience contract — tit…
• PageUp Careers Jobs Exporter — One structured job record per publicly listed opening from employer career sites hosted by PageUp — title, employer, location, closing date, apply li…
• Paylocity Job Feed — Any Employer Board — One structured jobrecord per public posting on a Paylocity recruiting board. You supply boards as guid/slug (from the recruiting.paylocity.com URL);…
• 🏢 About NexGenData — NexGen Watch is NexGenData's fleet of 256 public monitoring and lookup actors built on official sources, pay-per-result. Browse the catalog at apify.com/nexgenwatch.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab — every one is read.