# WHO PQ FPP Reference Number Portfolio Status Monitor (`plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor`) Actor

Watch WHO PQ Reference Numbers; emit APPEARED/DROPPED/BASIS\_OF\_LISTING\_CHANGED and related events from the official FPP CSV. Not EMA/FDA twin; not a full WHO PQ dump billed as rows.

- **URL**: https://apify.com/plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** AI, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 who pq fpp status event delivereds

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

## WHO Prequalification FPP Reference Number Portfolio Status Event Monitor

Watch a **book of WHO Prequalification Reference Numbers** (Finished Pharmaceutical Products / Biotherapeutic Products) and emit typed status events when a product **appears, drops, or changes Basis of Listing / Product Type / Therapeutic Area / Applicant / product name / dosage form / alternative basis / Date of Prequalification** on the official WHO PQ CSV export.

### Source

- Official CSV export: [Finished Pharmaceutical Products export](https://extranet.who.int/prequal/medicines/prequalified/finished-pharmaceutical-products/export?page&_format=csv) (~653 unique WHO Reference Numbers; ~130 KB)
- Browse UI: [WHO PQ FPP list](https://extranet.who.int/prequal/medicines/prequalified/finished-pharmaceutical-products)
- Durable key: **WHO Reference Number** (e.g. `BT-ON013`, `AP001`, `ANDA 077267 USFDA`)
- Status field: **Basis of Listing** (`Prequalification - Full` / `Prequalification - Abridged` / `Alternative Listing` / …)
- Also tracked: Product Type, Therapeutic Area, Applicant, INN/strength, Dosage Form, Basis of alternative listing, Date of Prequalification
- **Honest lag** — WHO’s Drupal CSV is a live export **without** a reliable `Last-Modified` header. Updates are irregular as products are prequalified or removed. Schedule this Actor **weekly–monthly**. `DROPPED` means the reference is **absent from the current export**, not a formal WHO delisting notice with an effective date. This is a snapshot-diff monitor, not a real-time WHO PQ API.

### Events (PPE)

| Event | Meaning |
|-------|---------|
| `APPEARED` | Reference present after previously missing |
| `DROPPED` | Reference absent after previously present |
| `BASIS_OF_LISTING_CHANGED` | Basis of Listing change (Full / Abridged / Alternative / …) |
| `PRODUCT_TYPE_CHANGED` | Product Type change (FPP / Biotherapeutic / …) |
| `THERAPEUTIC_AREA_CHANGED` | Therapeutic Area change |
| `APPLICANT_CHANGED` | Applicant change (attributes group) |
| `PRODUCT_NAME_CHANGED` | INN / Dosage Form and Strength change (attributes) |
| `DOSAGE_FORM_CHANGED` | Dosage Form change (attributes) |
| `ALTERNATIVE_BASIS_CHANGED` | Basis of alternative listing change (attributes) |
| `PQ_DATE_CHANGED` | Date of Prequalification change (attributes) |

Non-billable: `RUN_STATUS` (including `FIXTURE_HEALTH`). First observation stores baseline with **no** charge.

### Not this Actor

- **Not** EMA / FDA / TGA / Swissmedic national medicines twin (different regimes)
- **Not** a full WHO PQ medicines dump billed as rows
- **Not** a real-time WHO PQ API (snapshot CSV lag only)

### Pricing

- `who-pq-fpp-status-event-delivered` @ **$0.02** / unique delivered event
- `apify-actor-start` @ **$0.00005**

### Input

```json
{
  "whoReferenceNumbers": ["BT-ON013", "AP001", "ANDA 077267 USFDA"],
  "sourceMode": "live",
  "signalGroups": ["directory", "status", "attributes"],
  "maxRunSeconds": 180
}
```

`sourceMode=fixture` (default) is Store/CI health — no network, `RUN_STATUS` / `FIXTURE_HEALTH` only unless `emitFixtureDemoEvents=true`.

### Who this is for

- Global health / PQ procurement teams watching a named WHO Reference Number book
- Pharma regulatory intelligence tracking WHO PQ listing membership and basis changes
- Supply-chain / tender diligence workflows that need membership and status change events (not full-register dumps)

# Actor input Schema

## `whoReferenceNumbers` (type: `array`):

WHO Prequalification Reference Numbers to monitor against the official FPP CSV export (e.g. BT-ON013, AP001, ANDA 077267 USFDA). Invalid entries skipped with no charge. Not a full WHO PQ dump bill.

## `whoRefs` (type: `array`):

Optional alias for whoReferenceNumbers — same durable WHO Reference Number keys, merged into the watchlist.

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), status (BASIS\_OF\_LISTING\_CHANGED/PRODUCT\_TYPE\_CHANGED/THERAPEUTIC\_AREA\_CHANGED), attributes (APPLICANT\_CHANGED/PRODUCT\_NAME\_CHANGED/DOSAGE\_FORM\_CHANGED/ALTERNATIVE\_BASIS\_CHANGED/PQ\_DATE\_CHANGED). Default: directory+status.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget (CSV download + parse + watchlist diff). WHO PQ FPP CSV is small (~130 KB / ~653 refs).

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume WHO Reference Number snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = Store/CI health default (no network; RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official WHO PQ FPP CSV export (no API key; irregular Drupal export lag).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true push fabricated change events from local fixtures. Default false so Store daily auto-tests never emit fake WHO PQ events or charge who-pq-fpp-status-event-delivered.

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

Optional soft budget hint for delivered change events.

## `asOfHint` (type: `string`):

Optional as\_of label for events / RUN\_STATUS. Defaults to Last-Modified when present, else snapshot calendar day UTC (WHO export typically omits Last-Modified).

## `whoPqCsvUrl` (type: `string`):

Optional override for the official WHO PQ Finished Pharmaceutical Products CSV export URL.

## Actor input object example

```json
{
  "whoReferenceNumbers": [
    "BT-ON013",
    "AP001",
    "ANDA 077267 USFDA",
    "BT-CV001"
  ],
  "signalGroups": [
    "directory",
    "status"
  ],
  "maxRunSeconds": 180,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, WHO PQ FPP coverage limits

# 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("plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor").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("plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor").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 plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/who-pq-fpp-reference-number-portfolio-status-monitor"
        }
    }
}
```

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/BBinGvAh6g5o2I0DX/builds/ty8QEanr77g45cQNy/openapi.json