# ESMA Prospectus Register Check (`nexgenwatch/prospectus-check`) Actor

One prospectus_check verdict per issuer name you submit, resolved against ESMA's official Prospectus Register (the EU register of approved prospectuses and final terms, read through its public search service at registers.esma.europa.eu).

- **URL**: https://apify.com/nexgenwatch/prospectus-check.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Automation, Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 prospectus checks

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

## 🔔 ESMA Prospectus Register Check

One `prospectus_check` verdict per issuer name you submit, resolved against ESMA's official Prospectus Register (the EU register of approved prospectuses and final terms, read through its public search service at registers.esma.europa.eu). A verification CHECK, not a dump: each query comes back FOUND — with the issuer's registered name, the count of approved documents, the date of the latest approval filing, the document types seen and the national document id as evidence — or NOT_FOUND (the register has no such issuer), AMBIGUOUS (several issuers match; the candidates are listed so you can refine the query), or SERVICE_FAULT (the register did not answer, which is never billed).

Built for capital-markets compliance, KYC and onboarding teams, fund administrators and anyone who must confirm that an issuer has an ESMA-approved prospectus on file before relying on it.

Output is one `prospectus_check` row per result; billing is pay-per-event, the value event being one prospectus check (a $0.02 start fee per run, then $0.05 per prospectus check). Source: registers.esma.europa.eu.

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

### 📊 Sample Output

[![ESMA Prospectus Register Check sample output — a table of real prospectus check rows (input, query, verdict, issuer_name) from run fqxLXAK1cwZ598dWc on build 0.1.7](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/prospectus-check-sample)](https://apify.com/nexgenwatch/prospectus-check?fpr=2ayu9b)

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

| input | query | verdict | issuer_name | latest_approval_filing_date | sample_doc_types |
|---|---|---|---|---|---|
| UBS AG | UBS AG | FOUND | UBS AG | 2026-09-16T00:00:00Z | Final terms, including the summary of the individual issue annexed to  |
| Barclays Bank PLC | Barclays Bank PLC | FOUND | Barclays Bank PLC | 2021-04-16T00:00:00Z | Final terms, including the summary of the individual issue annexed to  |
| ZZZ Notareal Issuer 999 | ZZZ Notareal Issuer 999 | NOT_FOUND |  |  |  |

The run finished with the status message: `PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | prospectus_check charged=2`

### ✅ What you get

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_type` (string) — e.g. `prospectus_check`
- `input` (string/null) — e.g. `UBS AG`
- `query` (string/null) — e.g. `UBS AG`
- `source` (string/null) — e.g. `https://registers.esma.europa.eu/solr/esma_registers_priii_securities/select`
- `verdict` (string/null) — e.g. `FOUND`
- `issuer_name` (string/null) — e.g. `UBS AG`
- `approved_document_count` (string/null) — e.g. `3959668`
- `latest_approval_filing_date` (string/null) — e.g. `2026-09-16T00:00:00Z`
- `sample_doc_types` (string/null) — e.g. `Final terms, including the summary of the individual issue annexed to them`
- `national_doc_id` (string/null) — e.g. `DE000UP32U54`
- `candidates` (string/null) — null in every sample row
- `unbilled_reason` (string/null) — e.g. `not_found: no approved prospectus documents for this exact issuer`

### ⚙️ Sample inputs

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

```json
{
  "queries": [
    "UBS AG",
    "Barclays Bank PLC",
    "ZZZ Notareal Issuer 999"
  ]
}
```

The sample run charged exactly: 1 × $0.02 apify-actor-start + 2 × $0.05 prospectus_check = **$0.12** on the Free tier — every delivered row was billed.

This actor takes no size cap or filter beyond the input above, so the Store example is the one input to run; put it on a schedule to keep the data current.

### 🧾 JSON sample record

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

```json
{
  "record_type": "prospectus_check",
  "input": "UBS AG",
  "query": "UBS AG",
  "source": "https://registers.esma.europa.eu/solr/esma_registers_priii_securities/select",
  "verdict": "FOUND",
  "issuer_name": "UBS AG",
  "approved_document_count": "3959668",
  "latest_approval_filing_date": "2026-09-16T00:00:00Z",
  "sample_doc_types": "Final terms, including the summary of the individual issue annexed to them",
  "national_doc_id": "DE000UP32U54",
  "candidates": null,
  "unbilled_reason": null
}
```

### 🔧 How it works

**Source.** The actor reads registers.esma.europa.eu — endpoints: `https://registers.esma.europa.eu/solr/esma_registers_priii_securities/select`. 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.

**Charging.** Each prospectus check is charged at the moment it is pushed (`prospectus_check`); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

**Source.** ESMA's Prospectus Register search service (`https://registers.esma.europa.eu/solr/esma_registers_priii_securities/select`), the same endpoint the register's own website queries; public, keyless, read logged-out with an identified contact User-Agent.

**Resolution.** Each query is matched against issuer names in the register. One issuer with approved documents = FOUND; no issuer = NOT_FOUND; several plausible issuers = AMBIGUOUS with the candidate list in the row; a register error or timeout = SERVICE_FAULT.

**What counts as a completed check.** FOUND, NOT_FOUND and AMBIGUOUS are completed official answers and each is billed once. SERVICE_FAULT and an unparseable query are delivered with `unbilled_reason` and never charged. A run in which no query could be answered fails loud and charges nothing.

**Batch size.** Up to the input's hard maximum of queries per run; each query is one request to the register.

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

### 💰 Pricing example

| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Prospectus check (`prospectus_check`) | $0.05 | $0.045 | $0.04 | $0.0335 |

Worked at the live Free-tier price:

- 3 prospectus checks: $0.02 start + 3 × $0.05 = **$0.17**
- 25 prospectus checks: $0.02 start + 25 × $0.05 = **$1.27**
- 100 prospectus checks: $0.02 start + 100 × $0.05 = **$5.02**

A run that delivers zero rows charges the $0.02 start fee only. 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 4096 MB.

Yield on the sample run: `PARTIAL: 2 resolved (1 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 3 | answers billable=2 | prospectus_check charged=2`.

### ⚖️ Legal & ToS

This actor reads public, logged-out pages and feeds published by registers.esma.europa.eu. 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 (registers.esma.europa.eu) 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; 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 only.

**Q: How fresh is the data?**\
A: Every run reads the source live at run time; nothing is cached between runs. 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 NexGen Watch actors actors?**\
A: Same output shape and billing model; this one covers registers.esma.europa.eu. The siblings under **Related Actors** cover the other sources or slices — run several on one schedule for a combined feed.

**Q: Are there rate limits?**\
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

### 🆘 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.
- **Fewer rows than expected** → the source had fewer items in scope → widen the input.
- **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.

### 🔗 Related Actors

- [Philadelphia L\&I Business Licenses](https://apify.com/nexgenwatch/philadelphia-li-business-licenses?fpr=2ayu9b) — One record per Philadelphia L\&I business licence (licence number, type, status, business + legal name, issue/expiration/inactive dates, address, and…
- [Poland KRS Company Registry](https://apify.com/nexgenwatch/poland-krs-company-registry?fpr=2ayu9b) — One record per requested KRS number — company name, legal form, REGON, NIP, address and registration dates from the official current extract. This is…
- [Poland VAT Whitelist Verifier](https://apify.com/nexgenwatch/poland-vat-whitelist-verifier?fpr=2ayu9b) — One vat_check verdict per queried identifier against Poland's official Ministry of Finance VAT whitelist (Wykaz podatników VAT) — keyless, logged-out…
- [Seattle Business License Tax Certificates](https://apify.com/nexgenwatch/seattle-business-license-tax-certificates?fpr=2ayu9b) — One record per active Seattle business-licence tax certificate (legal + trade name, ownership type, NAICS activity, licence start date, address, city…
- [Slovakia Public-Sector Partners Register](https://apify.com/nexgenwatch/slovakia-public-sector-partners?fpr=2ayu9b) — One record per registered public-sector partner from the official RPVS OData — official ID, business name, validity dates, and beneficial owners when…
- [Spain AEMPS Medicines Registry (CIMA)](https://apify.com/nexgenwatch/spain-aemps-medicines-registry?fpr=2ayu9b) — One record per authorized medicine from the official CIMA REST API — national code, name, laboratory, authorization status; presentation/route/docume…
- 🏢 **About NexGenData** — NexGen Watch is NexGenData's fleet 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/prospectus-check?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

## `queries` (type: `array`):

Issuer names to resolve against the official ESMA prospectus register (approved prospectus / final-terms documents). Use the exact registered issuer name for a definitive FOUND, e.g. 'UBS AG'. Only a FOUND resolution is billed; NOT_FOUND, AMBIGUOUS and service-fault are emitted and never billed.

## Actor input object example

```json
{
  "queries": [
    "UBS AG",
    "Barclays Bank PLC",
    "ZZZ Notareal Issuer 999"
  ]
}
```

# 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 = {
    "queries": [
        "UBS AG",
        "Barclays Bank PLC",
        "ZZZ Notareal Issuer 999"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/prospectus-check").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 = { "queries": [
        "UBS AG",
        "Barclays Bank PLC",
        "ZZZ Notareal Issuer 999",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/prospectus-check").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 '{
  "queries": [
    "UBS AG",
    "Barclays Bank PLC",
    "ZZZ Notareal Issuer 999"
  ]
}' |
apify call nexgenwatch/prospectus-check --silent --output-dataset

```

## MCP server setup

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

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/HMYcV7QU989fg6d5q/builds/r5davnQSgEdzq6j4i/openapi.json