# Malaysia Government Tenders API — MyProcurement, English-Keyed (`celestjux/celestjux-my-tenders`) Actor

Malaysian government tenders, quotations, requisitions and award results from MyProcurement (Ministry of Finance) — English field names, original Malay values, optional detail-page enrichment (eligibility, document price, briefing dates).

- **URL**: https://apify.com/celestjux/celestjux-my-tenders.md
- **Developed by:** [Celest Jux](https://apify.com/celestjux) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 records

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

## Malaysia Government Tenders API — MyProcurement, English-Keyed

Structured, English-keyed feed of Malaysian government procurement notices from the
official MyProcurement portal (myprocurement.treasury.gov.my), operated by the
Kementerian Kewangan (Ministry of Finance) — English field names over the original Malay
values, with optional detail-page enrichment: eligibility text, document-sale price, and
briefing/site-visit dates.

**Pengiklanan perolehan kerajaan Malaysia — iklan tender, sebut harga, requisition dan
keputusan, dalam format berstruktur.**

### What you get

| Field | Type | Notes |
|---|---|---|
| `id` | string | Portal hash id (from the detail URL) |
| `type` | enum | `tender` / `quotation` / `requisition` / `result_tender` / `result_quotation` |
| `referenceNo` | string | Tender / quotation number as published |
| `title` | string | Original Malay title |
| `ministry` | string?null | As shown on the portal (Malay, uppercase) |
| `agency` | string?null | As shown on the portal |
| `procurementCategory` | string?null | `Bekalan` / `Kerja` / `Perkhidmatan Bukan Perunding` / `Perkhidmatan Perunding` |
| `kodBidang` | string\[]?null | Field codes, e.g. `["B01","B04"]` |
| `advertisedDate` | date?null | ISO `YYYY-MM-DD` |
| `closingDate` | date?null | ISO `YYYY-MM-DD` |
| `resultDate` | date?null | Award decision date (result types) |
| `displayedResultDate` | date?null | Date the result was published (result types) |
| `indicativePriceMYR` | number?null | `null` when the portal shows "Tiada Maklumat" |
| `awardees` | array?null | `[{name, acceptedPriceMYR}]` (result types) |
| `briefings` | array | `[{date, venue, note?}]` — `note` when details enabled |
| `siteVisits` | array | `[{date, venue, note?}]` |
| `detailUrl` | string | Absolute portal URL |
| `scrapedAt` | datetime | ISO 8601 UTC |
| `extraFields` | object | Any other label/value pairs the portal exposed — nothing is dropped |

With **Include detail pages** on, each record is enriched from its detail page:

| Field | Notes |
|---|---|
| `submissionOffice` | Tempat Tender Diterima |
| `eligibilityText` | Taraf Kelayakan (free text, e.g. CIDB registration) |
| `twoEnvelope` | true / false / null |
| `notes` | Catatan Iklan |
| `description` | Deskripsi Perolehan |
| `documentSale` | `{place, date, priceMYR, paymentMethod}` |
| `centreResponsible`, `validityPeriodDays`, `advertisementLocality`, ... | Quotation-specific fields |
| `mofRegistrationNo`, `rocRegistrationNo`, `acceptanceLetterDate` | Awardee registration (result detail pages) |

Missing values are `null` — never empty strings, never invented.

### Input

```json
{
    "types": ["tender", "quotation"],
    "keyword": "SEKOLAH",
    "includeDetails": true,
    "onlyNew": true,
    "maxItems": 1000
}
```

| Key | Type | Default | Notes |
|---|---|---|---|
| `types` | array | `["tender","quotation"]` | Any of: tender, quotation, requisition, result\_tender, result\_quotation |
| `keyword` | string | — | Title contains (portal-side filter) |
| `ministries` | array | — | Exact names from the portal dropdown — see below |
| `procurementCategories` | array | — | Bekalan / Kerja / Perkhidmatan Bukan Perunding / Perkhidmatan Perunding |
| `kodBidang` | array | — | e.g. `["B01"]` or `["060101"]` — each value is a separate portal query |
| `advertisedFrom` / `advertisedTo` | date | — | `YYYY-MM-DD`, Tarikh Pelawaan range (advertisements only) |
| `closingAfter` | date | — | Skip notices closing on/before this (client-side) |
| `includeDetails` | bool | `false` | Fetch each notice's detail page |
| `onlyNew` | bool | `false` | Only records not pushed by your previous run (KV-backed) |
| `maxItems` | int | `1000` | Hard cap |
| `maxTotalChargeUsd` | number | `0` | Pay-per-event budget cap; actor stops cleanly when reached |

#### Ministries (exact spellings accepted by the portal)

Jabatan Perdana Menteri · Kementerian Pertanian dan Keterjaminan Makanan ·
Kementerian Komunikasi dan Multimedia · Kementerian Pertahanan · Kementerian Digital ·
Kementerian Perdagangan Dalam Negeri dan Kos Sara Hidup · Kementerian Ekonomi ·
Kementerian Pendidikan · Kementerian Peralihan Tenaga dan Transformasi Air ·
Kementerian Pembangunan Usahawan dan Koperasi · Kementerian Kewangan ·
Kementerian Luar Negeri · Kementerian Kesihatan · Kementerian Pendidikan Tinggi ·
Kementerian Dalam Negeri · Kementerian Perumahan dan Kerajaan Tempatan ·
Kementerian Sumber Manusia · Kementerian Kementerian Pelaburan, Perdagangan dan Industri ·
Kementerian Perpaduan Negara · Kementerian Sumber Asli dan Kelestarian Alam ·
Kementerian Kementerian Perladangan dan Komoditi · Kementerian Kemajuan Desa dan Wilayah ·
Kementerian Sains, Teknologi dan Inovasi · Kementerian Pelancongan, Seni dan Budaya ·
Kementerian Pengangkutan · Kementerian Pembangunan Wanita, Keluarga dan Masyarakat ·
Kementerian Kerja Raya · Kementerian Belia dan Sukan

(The doubled "Kementerian Kementerian" in two names is exactly as the portal spells them.)

### Pricing (pay per event)

| Event | Price |
|---|---|
| `record` — each notice pushed | **$0.002** ($2.00 / 1,000) |
| `detail` — extra per record with details on | **$0.001** ($1.00 / 1,000) |

A full tender pull without details ≈ $2.24. Set `maxTotalChargeUsd` to bound your spend.

### Notes & limits

- **Public data only** — this actor reads publicly listed procurement notices.
  No login, no bypassing of access controls. Requests are rate-limited and honestly
  labelled (`CelestJux-MyTenders/1.0`).
- **Source**: MyProcurement only. ePerolehan (the ministry's primary system) is not
  covered yet — it is a separate JSF-based portal, planned for a future version.
- MyProcurement itself notes its listings may lag ePerolehan; for time-critical
  bidding, verify on ePerolehan before relying on closing dates.
- Archives are not included in this version (open notices and recent results only).
- Results datasets: the portal sometimes re-issues the same notice or points two
  reference numbers at one detail page; the actor deduplicates identical notices and
  keeps distinct reference numbers even when the portal merges their detail pages.
- Values are kept in original Malay; field *keys* are English and stable.

### Limitations / known walls

- If the portal introduces captcha/challenge pages, the actor **fails loudly and
  stops** — it does not attempt evasion.
- Server-side date filters apply to advertisements only (the results endpoint
  ignores them).

# Actor input Schema

## `types` (type: `array`):

Which notice types to pull: open advertisements and awarded results.

## `keyword` (type: `string`):

Only notices whose title contains this text (portal-side, case-insensitive).

## `ministries` (type: `array`):

Exact ministry names as they appear in the portal dropdown (see README). Run fetches one ministry at a time.

## `procurementCategories` (type: `array`):

Bekalan (supply) / Kerja (works) / services / consultancy, as on the portal.

## `kodBidang` (type: `array`):

e.g. B01 or 060101. Portal matches within the card's comma list; each value is fetched as a separate portal query.

## `advertisedFrom` (type: `string`):

Tarikh Pelawaan range start, YYYY-MM-DD (advertisements only).

## `advertisedTo` (type: `string`):

Tarikh Pelawaan range end, YYYY-MM-DD (advertisements only).

## `closingAfter` (type: `string`):

Skip notices whose closing date is not after this, YYYY-MM-DD (client-side, advertisements only).

## `includeDetails` (type: `boolean`):

Enrich each record from its detail page.

## `onlyNew` (type: `boolean`):

Skip records already pushed by a previous run (remembered in KV store celestjux-my-tenders-seen).

## `maxItems` (type: `integer`):

Hard cap on records pushed.

## `maxTotalChargeUsd` (type: `number`):

Pay-per-event cap. Actor stops cleanly when reached (0 = no cap; ignored when running locally).

## `proxyConfiguration` (type: `object`):

MyProcurement only answers Malaysian routes. Tested 2026-09-26: direct = timeout, SG datacenter = refused, Malaysia residential = works. Keep RESIDENTIAL + MY.

## Actor input object example

```json
{
  "types": [
    "tender",
    "quotation"
  ],
  "includeDetails": false,
  "onlyNew": false,
  "maxItems": 1000,
  "maxTotalChargeUsd": 0,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "MY"
  }
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

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

// Prepare Actor input
const input = {
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "MY"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("celestjux/celestjux-my-tenders").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 = { "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "MY",
    } }

# Run the Actor and wait for it to finish
run = client.actor("celestjux/celestjux-my-tenders").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 '{
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "MY"
  }
}' |
apify call celestjux/celestjux-my-tenders --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,celestjux/celestjux-my-tenders"
        }
    }
}
```

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/PPc9BHI6rf2rX1erF/builds/c6qr1tLcQlmXVmV6L/openapi.json