# Malaysia ILP Fund Prices (`subimpact/my-ilp-fund-prices`) Actor

Daily unit prices for Malaysia investment-linked insurance (ILP) funds across 5 insurers: Prudential PRULink (71), Sun Life (24), Zurich Takaful (10), PruBSN Takafulink (11), Etiqa Life/Takaful (21 funds, MSN primary + PDF fallback, 1Y history). Clean JSON/CSV.

- **URL**: https://apify.com/subimpact/my-ilp-fund-prices.md
- **Developed by:** [subimpact](https://apify.com/subimpact) (community)
- **Categories:** Automation
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 source fetches

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — 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

## Malaysia ILP Fund Prices

Daily unit prices for Malaysia **investment-linked insurance (ILP) funds** — the sub-funds behind PRULink, Takafulink, Lion, Premier and Shariah insurance portfolios. Pulled from each insurer's **official public page**, normalized into one clean dataset.

### Why this exists

Malaysian insurers publish ILP unit prices on scattered, inconsistent pages — static HTML tables, embedded JS arrays, and PDFs. None of it is machine-readable as-is, and no Apify actor serves this lane. This actor turns 5 insurers' official pages into a single normalized JSON/CSV stream.

### Sources (all official public pages, live-verified 2026-08-10)

| Source | Funds | Method |
|---|---|---|
| Prudential PRULink (prufundprice.com) | 71 | embedded JS array |
| Sun Life Malaysia | 24 | static HTML tables (conventional + Islamic) |
| Zurich Takaful | 10 | static HTML table |
| Prudential BSN Takaful | 11 | HTML table (Incapsula; Chrome TLS fingerprint) |
| Etiqa Life + Takaful | 15 + 6 | daily price PDFs (~130 valuation dates of history) |

**~137 funds current + ~2,700 historical rows** per full run.

### Input

| Field | Default | Notes |
|---|---|---|
| `sources` | all | subset: `prudential`, `sunlife`, `zurich`, `prubsn`, `etiqa` |
| `includeHistory` | true | false = latest valuation date only |
| `format` | json | json or csv |
| `webhookUrl` | — | POST result file after run |

### Output

- **Dataset records** — one per fund × valuation date, streamed incrementally during the run:
  `source, fund_name, category, currency, price, valuation_date, previous_price, change, change_pct, raw_date, pricing_lag_days`
- **Key-value store** — `ilp_fund_prices.json` (or `.csv`) + `run_meta.json` (per-source counts, run time)
- `pricing_lag_days`: 2 for Prudential `#`-marked funds (2-business-day pricing), 1 otherwise

### Pricing

Pay-per-event: **$0.01 per source successfully fetched** (5 sources = $0.05 per full run). No charge on failed/empty sources.

### Notes & caveats

- All data is from insurers' official public pages; verify against your insurer before financial decisions.
- Etiqa history spans ~Feb–Aug of the current year (their daily PDF carries the full matrix).
- Sun Life/Zurich pages show the valuation date; Prudential/PruBSN/Etiqa include per-row dates.
- Allianz, AIA, Great Eastern, Tokio Marine, Hong Leong Assurance are **not** included in v1 (WAF/JS-rendered); a v2 via MSN Finance's public API is under evaluation.

# Actor input Schema

## `sources` (type: `array`):

Which insurers' fund prices to pull. Options: prudential (71 PRULink funds), sunlife (24 funds), zurich (10 shariah funds), prubsn (11 Takafulink funds), etiqa (Life + Takaful daily price tables with ~6 months history). Empty = all.

## `includeHistory` (type: `boolean`):

Etiqa PDFs carry ~144 valuation dates (Feb-Aug 2026) per fund. When true, all historical rows are emitted; when false, only the latest valuation date per fund.

## `format` (type: `string`):

Dataset records are always JSON; this controls the additional file delivered to the key-value store.

## `webhookUrl` (type: `string`):

POST the combined result file to this URL after the run (3 retries with backoff). Leave empty to skip.

## Actor input object example

```json
{
  "sources": [
    "prudential",
    "sunlife",
    "zurich",
    "prubsn",
    "etiqa"
  ],
  "includeHistory": true,
  "format": "json"
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("subimpact/my-ilp-fund-prices").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("subimpact/my-ilp-fund-prices").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 '{}' |
apify call subimpact/my-ilp-fund-prices --silent --output-dataset

```

## MCP server setup

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

```

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/Q31pyflZoRMr2JGWd/builds/ZQB1chrQZW42iM3nh/openapi.json