# Japan PMDA Drug Approvals Scraper (`nexgenwatch/japan-pmda-drug-approval-watch`) Actor

Scrape Japan PMDA new drug approvals: product, company, indication and approval date. Every run returns the current records as a dataset. Optional watch mode returns only what changed since your last run. Pay per result.

- **URL**: https://apify.com/nexgenwatch/japan-pmda-drug-approval-watch.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** News, Automation, Developer tools
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $134.00 / 1,000 drug approval deltas

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## 🛡️ Japan PMDA Drug Approvals Scraper

**Scrape Japan PMDA new drug approvals: product, company, indication and approval date.** Run it once and you get the current records as a dataset — that is the default. Turn on watch mode and a scheduled run returns only what changed since the last run (see *Optional: run it on a schedule*).

Japanese new-drug approvals as PMDA records them: approval date, brand name, marketing-authorisation holder with its corporate number, active ingredient, approval kind (new approval vs partial change) and the approved indication. Read from PMDA's own fiscal-year approval workbook, so a delta means a drug was approved — not that a document was regenerated.

Output is one `drug_approval_record` row per result; billing is pay-per-event, the value event being one drug approval delta (a $0.02 start fee per run, then $0.20 per drug approval delta plus one $0.10 source check per run that reads the source). Source: www.pmda.go.jp.

**Who buys this**

Buyers usually search for **PMDA** or **Japan drug approvals**.

- Regulatory-affairs, quality and product-safety teams monitoring PMDA.
- Distributors, retailers and supply-chain risk teams checking Japan drug approvals.
- Analysts and consultants tracking approvals, recalls and alerts in their market.

### 📊 Sample Output

[![Japan PMDA Drug Approvals Scraper sample output — a table of real drug approval delta rows (approval_date, brand_name, holder, corporate_number) from run bcZfPfXcR8RiIGnvq on build 0.1.24](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/japan-pmda-drug-approval-watch-sample-nw)](https://apify.com/nexgenwatch/japan-pmda-drug-approval-watch?fpr=2ayu9b)

Real rows from run `bcZfPfXcR8RiIGnvq` on build 0.1.24 (2026-09-28), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

| approval_date | brand_name | holder | corporate_number | ingredient | indication |
|---|---|---|---|---|---|
| 2026-05-11 | ミムリット皮下注用 | 第一三共㈱ | 1010001095640 | 弱毒生麻しんウイルス（ＡＩＫ－Ｃ株）、弱毒生ムンプスウイルス（ＲＩＴ４３８５株）、弱毒生風しんウイルス（高橋株） | 麻しん、おたふくかぜ及び風しんの予防を効能・効果とする新有効成分含有医薬品及び新医療用配合剤 |
| 2026-05-18 | ゼップバウンド皮下注2.5 mgアテオス | 日本イーライリリー㈱ | 3140001012176 | チルゼパチド | 肥満症 ただし、高血圧、脂質異常症又は耐糖能障害（2型糖尿病、耐糖能異常等）のいずれかを有し、食事療法・運動療法を行っても十分な効果が得られ |
| 2026-05-18 | ソーティクツ錠6 mg | ブリストル・マイヤーズスクイブ㈱ | 9011101044273 | デュークラバシチニブ | 既存治療で効果不十分な下記疾患 ○乾癬性関節炎 を効能・効果とする新効能医薬品 |
| 2026-05-18 | ジャスケイド錠9 mg | 日本ベーリンガーインゲルハイム㈱ | 1010701019774 | ネランドミラスト | 特発性肺線維症 進行性肺線維症 を効能・効果とする新有効成分含有医薬品 【希少疾病用医薬品】 |
| 2026-05-18 | ファセンラ皮下注30 ｍｇシリンジ | アストラゼネカ㈱ | 9120001073652 | ベンラリズマブ（遺伝子組換え） | 好酸球増多症候群を効能・効果とする新効能・新用量医薬品 【希少疾病用医薬品】 |
| 2026-05-18 | エムネクスパイク筋注シリンジ12歳以上用 | モデルナ・ジャパン㈱ | 4010401159678 | SARS-CoV-2のスパイクタンパク質のN－末端部位及び受容体結合部位をコードするmRNA | SARS-CoV-2による感染症の予防を効能・効果とする新有効成分含有医薬品 |
| 2026-05-18 | アレセンサカプセル150 mg | 中外製薬㈱ | 5011501002900 | アレクチニブ塩酸塩 | ALK 融合遺伝子陽性の進行・再発の固形癌を効能・効果とする新効能・新用量医薬品 |
| 2026-05-18 | アレックスビー筋注用 | グラクソ・スミスクライン㈱ | 2011001026329 | RSウイルスPreF3抗原 | RSウイルスによる感染症の予防を効能・効果とする新用量医薬品 |

The run finished with the status message: `NORMAL: emitted 10 item(s)`

### ✅ What you get

One row per record delivered by Japan PMDA New Drug Approval Watch; in watch mode a delta row carries delta_type, before, after and changed_fields. Field names come from the actor's real output; fields the source does not publish are null.

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`):

- `record_key` (string/null) — e.g. `pmda:2026:2026-05-11:ミムリット皮下注用`
- `fiscal_year` (string/number/integer/boolean/null) — e.g. `2026`
- `approval_date` (string/number/integer/boolean/null) — e.g. `2026-05-11`
- `review_division` (string/number/integer/boolean/null) — e.g. `ワクチン`
- `sequence_no` (string/number/integer/boolean/null) — e.g. `1`
- `brand_name` (string/number/integer/boolean/null) — e.g. `ミムリット皮下注用`
- `holder` (string/number/integer/boolean/null) — e.g. `第一三共㈱`
- `corporate_number` (string/number/integer/boolean/null) — e.g. `1010001095640`
- `approval_kind` (string/number/integer/boolean/null) — e.g. `承 認`
- `ingredient` (string/number/integer/boolean/null) — e.g. `弱毒生麻しんウイルス（ＡＩＫ－Ｃ株）、弱毒生ムンプスウイルス（ＲＩＴ４３８５株）、弱毒生風しんウイルス（高橋株）`
- `indication` (string/number/integer/boolean/null) — e.g. `麻しん、おたふくかぜ及び風しんの予防を効能・効果とする新有効成分含有医薬品及び新医療用配合剤`
- `sheet` (string/number/integer/boolean/null) — e.g. `承認品目5月分`
- `record_type` (string) — e.g. `drug_approval_record`
- `delta_type` (string/null) — null in every sample row
- `before` (object/array/string/number/integer/boolean/null) — null in every sample row
- `after` (object/array/string/number/integer/boolean/null) — null in every sample row
- `changed_fields` (array/object/string/null) — null in every sample row
- `observed_at` (string/null) — null in every sample row

**✅ What you get**

**✅ What you get**

- `record_key` (string/null) — e.g. `pmda:2026:2026-05-11:ミムリット皮下注用`
- `fiscal_year` — e.g. `2026`
- `approval_date` — e.g. `2026-05-11`
- `review_division` — e.g. `ワクチン`
- `sequence_no` — e.g. `1`
- `brand_name` — e.g. `ミムリット皮下注用`
- `holder` — e.g. `第一三共㈱`
- `corporate_number` — e.g. `1010001095640`
- `approval_kind` — e.g. `承 認`
- `ingredient` — e.g. `弱毒生麻しんウイルス（ＡＩＫ－Ｃ株）、弱毒生ムンプスウイルス（ＲＩＴ４３８５株）、弱毒生風しんウイルス（高橋株）`
- `indication` — e.g. `麻しん、おたふくかぜ及び風しんの予防を効能・効果とする新有効成分含有医薬品及び新医療用配合剤`
- `sheet` — e.g. `承認品目5月分`
- `record_type` (string) — e.g. `drug_approval_record`
- `delta_type` (string/null) — null in every sample row

Every run also writes a `RUN_RECEIPT` record to its key-value store with the source checks it made and the counts it charged — diagnostics never land in the paid dataset.

### ⚙️ Sample inputs

**1. Quick start — the Store example (this is what the sample above came from)**

```json
{
  "fiscal_year": "2026",
  "brand_contains": [],
  "max_items": 10,
  "watch_mode": false,
  "baseline_id": "default"
}
```

The sample run charged exactly: 1 × $0.02 apify-actor-start + 1 × $0.10 source-check + 0 × $0.20 drug-approval-delta = **$0.12** on the Free tier — snapshot preview rows are delivered unbilled; only the source check and the start fee were charged.

**2. A smaller, narrowed run**

```json
{
  "fiscal_year": "2026",
  "brand_contains": [],
  "max_items": 5,
  "watch_mode": false,
  "baseline_id": "default"
}
```

Caps the run at 5 rows; same billing shape as the sample run above. `fiscal_year` narrows what the source is asked for.

**3. Optional watch mode (changes only, for a schedule)**

```json
{
  "fiscal_year": "2026",
  "brand_contains": [],
  "max_items": 10,
  "watch_mode": true,
  "baseline_id": "default"
}
```

The first run seeds a private baseline and emits zero deltas; every later run emits one row per change, billed at $0.20 each plus the $0.10 source check; billed deltas are capped at 500 per run.

### 🧾 JSON sample record

One real record from run `bcZfPfXcR8RiIGnvq`, exactly as it lands in the dataset (emails masked, long text shortened):

```json
{
  "record_key": "pmda:2026:2026-05-11:ミムリット皮下注用",
  "fiscal_year": "2026",
  "approval_date": "2026-05-11",
  "review_division": "ワクチン",
  "sequence_no": "1",
  "brand_name": "ミムリット皮下注用",
  "holder": "第一三共㈱",
  "corporate_number": "1010001095640",
  "approval_kind": "承 認",
  "ingredient": "弱毒生麻しんウイルス（ＡＩＫ－Ｃ株）、弱毒生ムンプスウイルス（ＲＩＴ４３８５株）、弱毒生風しんウイルス（高橋株）",
  "indication": "麻しん、おたふくかぜ及び風しんの予防を効能・効果とする新有効成分含有医薬品及び新医療用配合剤",
  "sheet": "承認品目5月分",
  "record_type": "drug_approval_record",
  "schema_version": "1.0",
  "output_mode": "preview",
  "preview_cap": 25,
  "preview_truncated": 0
}
```

### 🔧 How it works

**Source.** The actor reads www.pmda.go.jp — endpoints: `https://www.pmda.go.jp`, `https://www.pmda.go.jp/review-services/drug-reviews/review-information/`. Public pages and feeds only; nothing behind a login.

**Transport.** Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

**Watch semantics.** Snapshot mode (`watch_mode: false`) returns a preview capped at 25 records. Watch mode keys every record on a source-native id, stores a private baseline in a named key-value store, and on each later run emits one delta row per change (new / changed / removed). A blocked fetch is never diffed, so a source outage cannot show up as a mass removal.

**Terminal states.** A run ends NORMAL, CAPPED (your cap was reached), PARTIAL (something was withheld and the message says what), GENUINE_EMPTY (the source was read and truly had nothing in scope) or BLOCKED (the source refused or changed shape — the run FAILS loud and bills nothing). A zero-row run is never reported as a silent success.

**Charging.** Each drug approval delta is charged at the moment it is pushed (`drug-approval-delta`); a row that fails to charge is not delivered, so the dataset count always equals the charged count. One `source-check` is charged per run that actually read the source.

**🔧 How it works**

**🔧 How it works**

**Source**

PMDA fiscal-year new-drug approval list, 承認品目一覧（新医薬品）(public, logged-out)

- https://www.pmda.go.jp/review-services/drug-reviews/review-information/p-drugs/0010.html

Public, logged-out only — no API key, login, cookie or CAPTCHA.

**Snapshot mode is a PREVIEW**

`watch_mode: false` returns at most **25 records**, hard-capped in code
regardless of any input, labeled `output_mode: "preview"`. This actor sells
change detection, not bulk record export.

**Watch semantics**

The first watch run stores a private baseline and emits **zero** deltas. Later
runs emit `NEW` / `CHANGED` / `REMOVED` keyed on the source-native id with
`before` / `after` and `changed_fields`. Billed deltas are capped at 500 per
run; the overflow is reported as a named PARTIAL withholding, is never billed,
and is re-detected on the next run.

**Terminal states**

`NORMAL` · `SUCCEEDED-0: GENUINE_EMPTY` · `SUCCEEDED-0` (no change) · `PARTIAL` · `BLOCKED`.
A zero with no evidence FAILS loud rather than exiting 0 quietly.

**Approvals arrive in batches, not on a daily drip**

PMDA approves new drugs in rounds and republishes its fiscal-year workbook in batches, so this
feed is lumpy by construction. Measured on 2026-07-27: **38 approvals across a 39-day span in
the FY2026 workbook, about 6.8 a week — but 0 in the trailing 30 days**, newest approval dated
2026-06-19.

That is the source behaving normally, not this Actor failing. Expect long quiet stretches and
then several deltas in a single run. Read a `SUCCEEDED-0` (no change) as *"the workbook has not
been republished since the last read"*, not as *"no drugs were approved"* — and budget against
the batch rather than against a daily average.

**What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

### ⏰ Optional: run it on a schedule

A single run returns the current records. If you also want to be told what changed over time, open the actor in Apify Console → **Schedules** → **Create new**, add this actor with the watch-mode input above (`watch_mode: true`) so each run returns only the changes, and pick a cadence:

- **Daily** — `0 7 * * *` (07:00 UTC): catch changes within a day.
- **Weekly** — `0 7 * * 1`: a Monday digest.

The baseline persists in a named key-value store between runs, so every scheduled run compares against the last one; use a different `baseline_id` for independent watches. Schedules can also POST results to a webhook (Console → Integrations).

### 💰 Pricing example

| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Source check (`source-check`) | $0.10 | $0.09 | $0.08 | $0.067 |
| Drug Approval Delta (`drug-approval-delta`) | $0.20 | $0.18 | $0.16 | $0.134 |

Worked at the live Free-tier price (watch mode, one delta per change):

- 8 drug approval deltas: $0.02 start + $0.10 source check + 8 × $0.20 = **$1.72**
- 25 drug approval deltas: $0.02 start + $0.10 source check + 25 × $0.20 = **$5.12**
- 400 drug approval deltas: $0.02 start + $0.10 source check + 400 × $0.20 = **$80.12**

A run that delivers zero rows charges the $0.02 start fee plus the $0.10 source check (the source was read and reported empty). A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 1024 MB.

Yield on the sample run: `NORMAL: emitted 10 item(s)`. `max_items` is a hard ceiling on what is delivered and billed, never a target. Snapshot output is capped at 25 records regardless of the cap you set; watch mode is the full feed.

### ⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by www.pmda.go.jp. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

### ❓ FAQ

**Q: Do I need an API key or a login?**\
A: No. The source (www.pmda.go.jp) is read logged-out; the input schema has no key field and the actor carries no secrets.

**Q: Why did my run return 0 rows?**\
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input (in watch mode the first run always seeds the baseline and returns zero deltas); BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee plus one source check.

**Q: How many rows can one run return?**\
A: Up to `max_items` (default 400); snapshot previews stop at 25. Raise the cap for a bigger run; you pay per delivered row.

**Q: What does watch mode remember between runs?**\
A: A private baseline of source-native record ids in a named key-value store (`baseline_id` names it, so several independent watches can coexist). Each later run diffs the live source against it and emits only changes.

**Q: How fresh is the data?**\
A: Every run reads the source live at run time; nothing is cached between runs except the watch baseline. Put it on a schedule for a continuous feed.

**Q: What formats can I export?**\
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

**Q: How is this different from the other product safety and approvals scrapers actors?**\
A: Same output shape and billing model; this one covers www.pmda.go.jp. The siblings under **Related Actors** cover the other sources or slices — run several on one schedule for a combined feed.

### 🆘 Troubleshooting

- **Run FAILED with BLOCKED** → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
- **Status says CAPPED** → your cap (`max_items`) was reached → raise it for a bigger run.
- **Input validation error on start** → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
- **Run TIMED-OUT** → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.
- **First watch run shows no deltas** → expected: it seeds the baseline; changes appear from the second run.

### 🔗 Related Actors

- [FDA Device Establishment Listings](https://apify.com/nexgenwatch/fda-device-establishment-listings?fpr=2ayu9b) — One establishment_record per FDA device establishment registration from the official openFDA endpoint — keyless, logged-out
- [FDA Drug Approvals (Drugs@FDA) Scraper](https://apify.com/nexgenwatch/fda-drug-approvals?fpr=2ayu9b) — Clean, structured records of FDA drug approvals, sourced live from the official openFDA Drugs@FDA API (https://api.fda.gov/drug/drugsfda.json) — an a…
- [FDA NDC Product Directory](https://apify.com/nexgenwatch/fda-ndc-product-directory?fpr=2ayu9b) — One drug_product_record per product in the official FDA National Drug Code (NDC) Directory via openFDA — keyless, logged-out
- [New Zealand Medsafe Recalls Scraper](https://apify.com/nexgenwatch/new-zealand-medsafe-recall-watch?fpr=2ayu9b) — Scrape New Zealand Medsafe medicine and device recalls: product, sponsor, reason and recall date. Every run returns the current records as a dataset.…
- [UK MHRA Medicine and Device Alerts Scraper](https://apify.com/nexgenwatch/uk-mhra-medicine-device-alert-watch?fpr=2ayu9b) — Scrape UK MHRA medicine and device safety alerts and recalls: product, issue, action and date. Every run returns the current records as a dataset. Op…
- [US FDA Recalls Scraper - Drug, Device, Food](https://apify.com/nexgenwatch/us-fda-recall-lifecycle-watch?fpr=2ayu9b) — Scrape US FDA recalls for drugs, devices and food: product, firm, classification, reason and status. Every run returns the current records as a datas…
- 🏢 **About NexGen Watch** — NexGen Watch is a catalog of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b).

### ⭐ Found this useful?

If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/japan-pmda-drug-approval-watch?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab — every one is read.

# Actor input Schema

## `fiscal_year` (type: `string`):

Japanese fiscal year to read, e.g. 2026. Leave blank for the newest year PMDA publishes.

## `brand_contains` (type: `array`):

Optional substrings matched against the brand name (販売名).

## `max_items` (type: `integer`):

Hard cap on approval rows processed (bounds runtime).

## `watch_mode` (type: `boolean`):

First run seeds a private baseline and emits ZERO deltas. Off by default: a run without this flag returns the current records.

## `baseline_id` (type: `string`):

Names the private baseline so several watches can run side by side.

## Actor input object example

```json
{
  "fiscal_year": "2026",
  "brand_contains": [],
  "max_items": 10,
  "watch_mode": false,
  "baseline_id": "default"
}
```

# Actor output Schema

## `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 = {
    "fiscal_year": "2026",
    "brand_contains": [],
    "max_items": 10,
    "watch_mode": false,
    "baseline_id": "default"
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/japan-pmda-drug-approval-watch").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 = {
    "fiscal_year": "2026",
    "brand_contains": [],
    "max_items": 10,
    "watch_mode": False,
    "baseline_id": "default",
}

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/japan-pmda-drug-approval-watch").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 '{
  "fiscal_year": "2026",
  "brand_contains": [],
  "max_items": 10,
  "watch_mode": false,
  "baseline_id": "default"
}' |
apify call nexgenwatch/japan-pmda-drug-approval-watch --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgenwatch/japan-pmda-drug-approval-watch"
        }
    }
}
```

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/2TuaURbR9cIS0jmZ9/builds/doskTqSiFzanGM8Jz/openapi.json