JobStreet Company Profile

Disclosure: Apify links with fpr=aiagentapi are referral links. An eligible signup may support AgentX without changing the user’s price.

JobStreet Company Profile turns one supported JobStreet, JobsDB, or SEEK company-profile URL into a source-dependent employer record with identity, market, ratings, jobs, reviews, salary, culture, and processing fields.

• One required URL keeps each run attributable to a specific company profile and market.
• The schema documents 43 possible top-level fields while empty source values may be omitted from a returned row.
• Eight supported markets cover Singapore, Australia, Hong Kong, Malaysia, New Zealand, the Philippines, Thailand, and Indonesia.
• A live MCP check on July 23, 2026 returned Google Singapore with 36 populated top-level fields, 352 jobs, and 10 reviews.

Run one company profile

Use the Apify API

Source sections can be absent, blocked, or temporarily inconsistent. A successful run proves that a Dataset row was written; it does not prove that every tab, job, review, salary, counter, or media item was complete.

Why Choose This API

JobStreet Company Profile provides one normalized record for a company page hosted by JobStreet, JobsDB, or SEEK. It combines company identity and About data with whichever Life and Culture, Salaries, Reviews, Jobs, gallery, related-company, and rating sections are accessible during the run. That makes it useful for employer research without forcing downstream systems to reconcile several page layouts themselves.

The input is intentionally narrow. It accepts a supported profile URL containing the company slug and numeric profile identifier. It does not search by employer name, resolve an arbitrary website, or accept a general jobs-search URL. The domain identifies one of eight supported markets and becomes the returned country, country_code, and platform zone context.

Returned data keeps source semantics visible. claimed is the platform’s claimed-profile flag, not independent business verification. job_count and review_count are source summary values and can differ from the lengths of the jobs and reviews arrays. Salary ranges, recommendation scores, rating breakdowns, AI summary text, and culture statements belong to the source profile; this Actor does not independently validate them.

The record is designed for inspection as well as automation. Identity and provenance fields make it possible to trace a row back to the submitted URL and processing time. Nested arrays preserve useful job, review, salary, perk, gallery, and related-company detail when available, while source-empty fields may be left out instead of being converted into invented values.

Quick Start Guide

Use a supported company profile URL rather than a home page, job listing, or search-results URL. This verified Singapore example is suitable for a bounded first check:

{
  "company_url": "https://sg.jobstreet.com/companies/google-168550267780768"
}

Submit the input in Apify Console and wait for a terminal status. Then open the default Dataset and verify the returned url, company_id, name, country, and platform before relying on nested content. The July 23, 2026 baseline resolved the intended Google Singapore profile, returned country code SG, rating 4.7, review count 10, and job count 352.

Inspect array lengths independently. In the same run, jobs contained 352 records and reviews contained 10, while salaries was empty. Another company or a later run can return different lengths because the source profile changes, individual sections can be unavailable, and pagination can stop when a later page is not accessible.

One run accepts one company URL. For a list of companies, start separate bounded runs, retain each source URL, and deduplicate on a deliberate key such as the domain plus company_id. Avoid treating a company name alone as a stable cross-market identifier.

Input Parameters

Parameter	Type	Required	Accepted shape	Purpose
company_url	string	Yes	Supported /companies/{slug}-{numeric_id} profile URL	Selects the company profile and one of the eight supported markets.

Supported domains are sg.jobstreet.com, my.jobstreet.com, ph.jobstreet.com, id.jobstreet.com, hk.jobsdb.com, th.jobsdb.com, www.seek.com.au, and nz.seek.com. The URL must use HTTP or HTTPS and contain both a company slug and numeric identifier in the company-profile path.

The Actor rejects unsupported domains and malformed profile paths. There is no keyword, employer-name, location, date, review limit, job limit, salary filter, login, cookie, language, proxy, or batch input. Because there is no public limit for nested jobs or reviews, choose the company deliberately and apply a run timeout when testing an unfamiliar, high-volume profile.

Extra public properties are rejected. The required field has the same prefill and example so the Console can launch a reproducible first run without silently adding optional request filters.

Output Data Schema

The Dataset schema lists 43 possible top-level fields in runtime order. They fall into these groups:

Area	Possible fields
Identity and market	type, url, company_id, org_id, name, synonym, country, country_code, zone, claimed
Company profile	website, size, industry, industry_id, location, description, specialities
Culture and media	mission, statement, featured, awards, culture, perks, gallery, logo, cover
Ratings and summaries	rating, review_count, job_count, recommended, salary_rating, rating_breakdown, review_aspects, ai_summary, review_dates
Collections	related, salaries, jobs, reviews
Processing	status, processor, processed_at, platform

This abbreviated but field-faithful sample reflects the populated top-level keys observed in the Google Singapore baseline:

{
  "type": "company",
  "url": "https://sg.jobstreet.com/companies/google-168550267780768",
  "company_id": "168550267780768",
  "org_id": "4946",
  "name": "Google",
  "country": "Singapore",
  "country_code": "SG",
  "zone": "asia-7",
  "claimed": true,
  "website": "https://www.google.com.sg",
  "industry": "Information & Communication Technology",
  "location": "Singapore",
  "description": ["Source profile description block"],
  "specialities": ["Source speciality"],
  "mission": {"description": ["Source mission block"]},
  "statement": {"title": "Source culture statement"},
  "featured": {"title": "Source featured content"},
  "perks": [{"title": "Source perk"}],
  "gallery": [{"link": "https://example.com/source-gallery-image.jpg"}],
  "logo": "https://example.com/source-company-logo.png",
  "rating": 4.7,
  "review_count": 10,
  "job_count": 352,
  "recommended": 94,
  "salary_rating": 86,
  "rating_breakdown": {"company_rating5_star_count": 8},
  "review_aspects": [{"rating": 4.5, "count": 10, "description": "Work/Life balance"}],
  "review_dates": {"reviews_date_from": "2023-01-01T00:00:00.000Z"},
  "related": [{"name": "Related company", "slug": "related-company-1", "id": "1"}],
  "salaries": [],
  "jobs": [{"id": "example-job", "title": "Example source job", "location": "Singapore"}],
  "reviews": [{"id": "example-review", "title": "Example source review", "overall_rating": 5}],
  "status": "success",
  "processor": "https://apify.com/agentx/jobstreet-company-profile?fpr=aiagentapi",
  "processed_at": "2026-07-23T19:33:46+00:00",
  "platform": "JobStreet Company Profile"
}

The sample shortens nested arrays and replaces review text. Seven possible keys were absent from that live row because their source values were empty. Empty arrays are retained for selected collection fields, while many empty scalar, object, or optional array values are omitted. Consumers should therefore validate keys defensively and distinguish a missing value from zero, false, or an empty list.

Integration Examples

The public Actor name is agentx/jobstreet-company-profile; its stable Actor ID is aQtWqjZNEbpcDkIXu. Start the verified scenario through HTTP:

curl -X POST "https://api.apify.com/v2/acts/agentx~jobstreet-company-profile/runs?token=$APIFY_TOKEN&timeout=180" \
  -H "Content-Type: application/json" \
  -d '{"company_url":"https://sg.jobstreet.com/companies/google-168550267780768"}'

Poll the run ID, then read the default Dataset. A terminal success should be followed by an item-count and identity check. Keep the API token in an environment variable or secrets manager and remove employee review text or personal data from support examples.

For a hosted MCP client, configure the Actor and use the same single input:

{
  "mcpServers": {
    "apify-jobstreet-company": {
      "url": "https://mcp.apify.com?tools=agentx/jobstreet-company-profile",
      "headers": {"Authorization": "Bearer <APIFY_TOKEN>"}
    }
  },
  "exampleToolArguments": {
    "company_url": "https://sg.jobstreet.com/companies/google-168550267780768"
  }
}

See the Apify MCP documentation for current client configuration. Bound tests with a timeout and enough pay-per-event allowance for Actor Start, usage, and one Result; a charge cap does not limit how many nested jobs or reviews the source profile may expose.

Pricing & Cost Calculator

Publishing metadata declares three event types:

Event	Billing unit	Price
actor_usage	Metered runtime, proxy, and storage event	$0.00001
apify-actor-start	Platform start event, one per GB with a one-event minimum	$0.01
result	One successfully pushed Dataset company record	Tier-dependent

Result prices are $0.25000 Free, $0.24167 Bronze, $0.23333 Silver, and $0.22500 Gold, Platinum, or Diamond. One successful 256 MB run has the one-event Actor Start minimum, one Result at the account tier, and metered usage. Ten successful Bronze results correspond to $2.41670 in Result events before starts and usage.

The Result event is charged once per pushed company row, not once per nested job or review. A sparse row can still be a result, so validate its identity and required business fields. Platform pricing and plan behavior can change; review the Actor pricing surface and account spending controls before scheduled or high-volume use.

A read-only helper contains an unused-looking legacy $0.03 Result constant. The publishing metadata and hosted pricing surface determine customer billing. That drift is recorded for a separate runtime-code cleanup and is not presented as a discount.

Use Cases & Applications

Recruiting and talent-intelligence teams can compare active hiring signals across a documented list of APAC employers. Employer-research workflows can combine current source ratings, review aspects, culture statements, perks, and job records with an internal company identifier. Compensation analysts can inspect source-provided salary ranges, while treating missing ranges and platform formatting as limitations rather than inferred market benchmarks.

Sales and partnership teams can enrich an existing company record with the source website, profile market, industry, location, company size, related companies, and current hiring activity. The claimed flag should remain labeled as a source-platform attribute and must not be converted into independent identity verification.

Monitoring workflows can schedule repeat observations and calculate changes outside the Actor. Store the processing timestamp, company ID, source URL, and prior row; counters and nested arrays represent snapshots and the Actor does not calculate deltas. Review text may contain personal or sensitive statements, so minimize retention and restrict access according to the stated purpose.

FAQ

Can I enter a company name instead of a URL?

No. The public input requires a supported company-profile URL with a numeric company ID.

Which markets are supported?

Singapore, Australia, Hong Kong, Malaysia, New Zealand, the Philippines, Thailand, and Indonesia through the documented JobStreet, JobsDB, and SEEK domains.

Does it always return all jobs and reviews?

No. It attempts to collect accessible pages, but source changes, blocking, missing sections, and later-page failures can produce partial or empty arrays.

Why are some of the 43 fields missing?

The normalized output removes many empty source values. Treat keys as optional unless your own validation establishes otherwise.

Is claimed: true business verification?

No. It reproduces the source platform’s claimed-profile flag and is not independent verification.

Why does job_count differ from jobs.length?

The count is a source summary while the array contains records accessible during this run. They can update at different times or be only partially retrievable.

Are salary values verified market benchmarks?

No. They are source-provided role ranges and can be absent, stale, differently formatted, or based on limited observations.

What should I check after a successful run?

Confirm Dataset item count, source URL, company ID, name, market, populated sections, array lengths, event charges, and any unexpected omissions.

Trust & Certifications

The public schema, read-only execution path, pricing events, and a live MCP Dataset were checked on July 23, 2026. The baseline returned the intended company and market with one row, 36 populated top-level keys, 352 job records, 10 review records, and no salary rows. This is reproducible evidence for one time and source profile, not a completeness guarantee.

This page does not claim an external security, privacy, data-quality, or compliance certification. Apify provides the platform controls described in its documentation; users must evaluate those controls and the source data for their own requirements. Keep run IDs, build versions, redacted inputs, and expected field lists for regression evidence.

Legal & Compliance

Use the Actor only for company-profile content you are authorized to access and process. Users are responsible for the applicable SEEK Terms of Use, SEEK Privacy Policy, JobStreet or JobsDB terms, employment and privacy rules, database rights, and contractual restrictions in each market.

Employee reviews, job descriptions, images, and profile text may be copyrighted or contain personal information. Collect only what the stated purpose requires, protect retained data, avoid individual profiling or discriminatory employment decisions, and delete information according to an appropriate retention policy. Do not use the Actor to bypass access controls or represent source flags and summaries as independent verification.

Related Tools

• LinkedIn Company Lookup adds a separate professional-network company view.
• LinkedIn Jobs Scraper supports job-search workflows on LinkedIn.
• All Jobs Scraper provides a multi-platform jobs entry point.
• LinkedIn Profile Lookup enriches an authorized individual professional profile.

Support & Community

The Actor, schemas, pricing path, runtime contract, Store links, and Google Singapore MCP sample were last checked on July 23, 2026. Source sections, counts, arrays, URLs, and access conditions can change after that date.

• AgentX community
• Contact the AgentX team
• Actor Store page
• Apify API reference
• Apify MCP documentation

For support, include the Actor URL, stable ID, run ID, build number, redacted company URL, expected identity, actual item count, and the names of missing sections. Never send API tokens, cookies, private company data, or unredacted employee review content.

Run one company profile

Use the Apify API