ESMA Prospectus Register Check avatar

ESMA Prospectus Register Check

Pricing

from $33.50 / 1,000 prospectus checks

Go to Apify Store
ESMA Prospectus Register Check

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).

Pricing

from $33.50 / 1,000 prospectus checks

Rating

0.0

(0)

Developer

NexGen Watch

NexGen Watch

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Share

πŸ”” 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

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):

inputqueryverdictissuer_namelatest_approval_filing_datesample_doc_types
UBS AGUBS AGFOUNDUBS AG2026-09-16T00:00:00ZFinal terms, including the summary of the individual issue annexed to
Barclays Bank PLCBarclays Bank PLCFOUNDBarclays Bank PLC2021-04-16T00:00:00ZFinal terms, including the summary of the individual issue annexed to
ZZZ Notareal Issuer 999ZZZ Notareal Issuer 999NOT_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)

{
"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):

{
"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

EventFreeBronzeSilverGold
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.

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.
  • Philadelphia L&I Business Licenses β€” 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 β€” 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 β€” 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 β€” 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 β€” 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) β€” 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.

⭐ Found this useful?

If this actor saved you a manual check, a quick review on the Apify Store helps other teams find it. Feature request or a source that changed? Open it from the Issues tab β€” every one is read.