# Korea Cosmetics Regulatory Data (MFDS) in English (`cm504/korea-cosmetics-mfds`) Actor

Korean MFDS cosmetics data as clean English JSON: new functional cosmetics filings (brightening, anti-wrinkle, sunscreen) with English product and company names, the official ingredient dictionary, ingredient restrictions by country, and GMP manufacturers.

- **URL**: https://apify.com/cm504/korea-cosmetics-mfds.md
- **Developed by:** [KH C](https://apify.com/cm504) (community)
- **Categories:** Business, E-commerce
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.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

## Korea Cosmetics Regulatory Data (MFDS) in English

Official Korean cosmetics regulatory data from the **Ministry of Food and Drug Safety (MFDS, 식품의약품안전처)**, as clean JSON with English field names and English product and company names.

Four registries in one Actor:

| Dataset | What it is | Size |
|---|---|---|
| **Functional cosmetics filings** | Every product reported to MFDS as a functional cosmetic (brightening, anti-wrinkle, sunscreen, hair-loss care and more): product, company, filing date, SPF/PA, domestic or imported, manufacturer and country | ~200,000 products, updated daily, newest first |
| **Ingredient restrictions by country** | Prohibited and restricted cosmetic ingredients with conditions (max concentration, product types, warnings) for Korea, EU, China, ASEAN, Japan, the US, Canada, Taiwan and more | ~31,000 rules |
| **Cosmetic ingredient dictionary** | The official Korean ingredient names with English names, CAS numbers, synonyms and origin | ~22,000 ingredients |
| **CGMP manufacturers** | Cosmetics manufacturers certified for Good Manufacturing Practice | ~200 companies |

### Who uses this

- **K-beauty importers, distributors and retailers** checking which products and brands are officially registered in Korea.
- **Brands and agencies tracking competitors**: see every new brightening, anti-wrinkle or sunscreen product filed in Korea, by brand, the day after it is filed.
- **Regulatory and formulation teams** checking whether an ingredient is prohibited or limited in the EU, China, ASEAN, Korea or other markets, with the exact conditions.
- **Sourcing teams** looking for certified Korean OEM/ODM manufacturers.
- **AI agents and apps** that need Korean cosmetics data through the Apify API or MCP.

### Example output

Functional cosmetics filing:

```json
{
  "reportId": "2026033714",
  "reportDate": "2026-11-10",
  "productNameKo": "미모바이마몽드카멜리아피디알엔탄력크림",
  "productNameEn": "Mamonde Camellia PDRN Firming Cream",
  "companyKo": "(주)아모레퍼시픽",
  "companyEn": "Amorepacific Corporation",
  "reportType": "Manufactured in Korea",
  "manufacturerCountry": null,
  "spf": null,
  "pa": null,
  "cancelled": false
}
```

Ingredient restriction:

```json
{
  "ingredientNameEn": "4-Benzyloxyphenol (Hydroquinone monobenzyl ether)",
  "casNo": "103-16-2, 622-62-8",
  "country": "ASEAN",
  "regulation": "Prohibited",
  "conditions": null
}
```

### Input

- **Dataset**: which registry to read.
- **Search**: product, company or ingredient name, CAS number or synonym, in Korean or English (e.g. `niacinamide`, `레티놀`, `PDRN`).
- **Company**: only one company's filings (Korean name, e.g. `아모레퍼시픽`).
- **Countries**: for ingredient restrictions, only these jurisdictions (e.g. `EU`, `China`, `ASEAN`).
- **Filed on or after** and **Only new filings since the last run**: for daily or weekly monitoring of new functional cosmetics.
- **English product and company names**: on by default.

### Monitoring tip

Schedule the Actor daily with **Only new filings since the last run** on, optionally with a **Company** or **Search** filter, and connect the dataset to Slack, email or Google Sheets through Apify integrations. You get every new Korean functional cosmetic filing the morning after it appears.

### Pricing

You pay per record, nothing else: **$3 per 1,000 records**. English names are included.

### Notes

- English product and company names are produced by AI from the Korean names; the Korean originals are always included.
- Searching across all ~200,000 functional cosmetics filings by text scans the registry from the newest filing backwards, so set **Maximum records** or **Filed on or after** to keep runs short.
- Data comes from MFDS open data published on data.go.kr with no usage restrictions. This Actor is not affiliated with MFDS.

# Actor input Schema

## `dataset` (type: `string`):

Which MFDS registry to read.

## `search` (type: `string`):

Text to match in product, company or ingredient names, CAS number or synonyms (Korean or English), e.g. niacinamide, 레티놀, 7732-18-5.

## `company` (type: `string`):

Functional cosmetics and GMP manufacturers: only this company, e.g. 아모레퍼시픽 or 엘지생활건강.

## `countries` (type: `array`):

Only rules for these jurisdictions, e.g. EU, China, ASEAN, United States, Japan, South Korea.

## `reportedSince` (type: `string`):

YYYY-MM-DD.

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

For scheduled monitoring of functional cosmetics: return only filings newer than the previous run with the same monitor name.

## `monitorName` (type: `string`):

Keeps separate 'only new' starting points for different schedules.

## `includeCancelled` (type: `boolean`):

Functional cosmetics: also return filings that were later cancelled.

## `translateNames` (type: `boolean`):

Add English product names (official brand romanization + translated product type) and English company names, produced by Claude (Anthropic).

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

Stop after this many records.

## Actor input object example

```json
{
  "dataset": "functional_cosmetics",
  "search": "",
  "company": "",
  "countries": [],
  "onlyNew": false,
  "monitorName": "default",
  "includeCancelled": false,
  "translateNames": true,
  "maxItems": 50
}
```

# Actor output Schema

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

MFDS cosmetics records, one item per product filing, ingredient, restriction rule or manufacturer.

# 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 = {
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("cm504/korea-cosmetics-mfds").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 = { "maxItems": 50 }

# Run the Actor and wait for it to finish
run = client.actor("cm504/korea-cosmetics-mfds").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 '{
  "maxItems": 50
}' |
apify call cm504/korea-cosmetics-mfds --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,cm504/korea-cosmetics-mfds"
        }
    }
}
```

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/nqdbrtc30aycWapPo/builds/65WpVLQPHQq2bG2YP/openapi.json
