Poland MSiG Court Gazette Scraper
Pricing
Pay per event
Poland MSiG Court Gazette Scraper
Search public Polish MSiG court and economic gazette notices for credit-risk, restructuring, creditor-call, and compliance watchlists.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Stas Persiianenko
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Share
Search the public Monitor Sądowy i Gospodarczy (MSiG) archive from Poland’s Ministry of Justice.
Turn company names, KRS numbers, NIP numbers, court references, dates, and legal-notice wording into structured, auditable records.
What does it do?
This actor searches public MSiG Court and Economic Gazette notices and enriches every result from the official notice-detail endpoint.
It is designed for repeatable watchlists, rather than manual browsing through individual gazette issues.
Who is it for?
- ⚖️ Legal and restructuring teams tracking court notices
- 💳 Credit-risk teams monitoring counterparties
- 🧾 Debt collection teams finding creditor calls
- 🛡️ Compliance teams maintaining company evidence trails
- 📊 Data teams building Polish company watchlists
Why use it?
MSiG is an official publication source, but searches can produce many notices.
This actor gives each result a consistent JSON record with identifiers, official text, and official download links.
Official source
Data comes from the public MSiG archive operated by the Polish Ministry of Justice.
The actor does not require login credentials, an API key, or browser automation.
Typical workflows
- Monitor a KRS number for new notices
- Search a company name before credit approval
- Find notices mentioning liquidation or restructuring
- Export public evidence into a case-management system
- Build a scheduled counterparty watchlist
Quick start
- Enter a company name, KRS, NIP, or notice wording.
- Select a publication date range.
- Choose a small maximum notice count for the first run.
- Run the actor.
- Export the dataset as JSON, CSV, Excel, or through the Apify API.
Company-name searches
Use entityName for the public entity-name search field.
Partial names are useful when the legal entity suffix or exact punctuation is unknown.
KRS searches
Use krs for a National Court Register number.
Leading zeroes are accepted by the source archive and are recommended when known.
Example: 0000143973.
NIP searches
Use nip for a Polish tax identification number.
Use this filter when a name is common or has changed over time.
Notice-text searches
textInPosition searches the formal notice heading.
textInBody searches the public full-text body returned by MSiG.
Use these fields for targeted concepts such as a creditor call or liquidation terminology.
Case and court filters
Use signatureOfCase, signatureKRS, and court when an internal case reference or issuing court is known.
Leave them blank for a broader company watchlist.
Date range
dateFrom and dateTo use YYYY-MM-DD format.
The prefill is deliberately small to make an inexpensive first run.
For ongoing monitoring, schedule the actor with a rolling date range in your own workflow.
Maximum notices
maxItems limits saved records and all corresponding detail requests.
Start with 10 records to validate filters, then increase it for an established watchlist.
The maximum is 1,000 records per run.
Output fields
| Field | Meaning |
|---|---|
noticeId | Stable official MSiG notice identifier |
noticeNumber | Number within the notice publication |
monitorNumber | Gazette issue number |
publicationDate | Official publication date |
entityName | Published entity or person name |
krs | Public National Court Register number |
nip | Public tax identifier when present |
caseSignature | Public court case reference |
chapterName | MSiG chapter/category |
textInPosition | Official notice heading text |
textInBody | Official full notice text |
detailUrl | Official public detail API URL |
downloadUrl | Official public download URL |
scrapedAt | UTC time this actor retrieved the record |
Output quality
A search result is enriched one notice at a time from the official detail endpoint.
If an individual detail record is temporarily unavailable, it is logged and skipped without failing the full search.
No legal classification is inferred from a notice.
Pricing
How much does it cost to scrape Poland MSiG notices?
Pricing uses Apify pay-per-event billing: a small start fee and a charge for each saved notice.
Your exact price depends on your Apify subscription tier and is shown before a run starts.
Use a low maxItems value to control scope.
Export formats
Use the dataset tab to export JSON, JSONL, CSV, Excel, XML, or RSS formats supported by Apify.
Each output row is a single enriched MSiG notice.
API usage: Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: process.env.APIFY_TOKEN });const run = await client.actor('automation-lab/poland-msig-court-gazette-scraper').call({krs: '0000143973', dateFrom: '2026-01-01', dateTo: '2026-01-31', maxItems: 10,});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
API usage: Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_APIFY_TOKEN')run = client.actor('automation-lab/poland-msig-court-gazette-scraper').call(run_input={'entityName': 'Haberbusch', 'dateFrom': '2026-01-01', 'dateTo': '2026-01-31', 'maxItems': 10,})for item in client.dataset(run['defaultDatasetId']).iterate_items():print(item['entityName'], item['downloadUrl'])
API usage: cURL
curl -X POST 'https://api.apify.com/v2/acts/automation-lab~poland-msig-court-gazette-scraper/runs?token=YOUR_APIFY_TOKEN' \-H 'content-type: application/json' \-d '{"krs":"0000143973","dateFrom":"2026-01-01","dateTo":"2026-01-31","maxItems":10}'
Integrations
- 🔔 Send new KRS matches to Slack or Microsoft Teams
- 🗃️ Store notice IDs in an internal compliance database
- 📈 Join MSiG notices to a CRM account list
- 📬 Create a case ticket when a watchlisted company appears
- 🧑⚖️ Attach the official download URL to a legal-review record
Scheduled monitoring
Use an Apify schedule with a short date window and a KRS or company-name filter.
Deduplicate downstream on noticeId, which is the stable public identifier.
MCP
Use this actor through Apify MCP in Claude Desktop or Claude Code.
Connect with https://mcp.apify.com?tools=automation-lab/poland-msig-court-gazette-scraper.
Claude Code setup:
$claude mcp add apify --transport http https://mcp.apify.com?tools=automation-lab/poland-msig-court-gazette-scraper
Claude Desktop configuration:
{"mcpServers":{"apify":{"url":"https://mcp.apify.com?tools=automation-lab/poland-msig-court-gazette-scraper"}}}
Example prompt: “Search MSiG notices for KRS 0000143973 published this month and summarize creditor-related items.”
Tips
- ✅ Prefer KRS for the most specific company watch
- ✅ Keep date windows short for scheduled runs
- ✅ Retain
noticeIdanddownloadUrlin your audit trail - ✅ Use
textInBodyfor a specific legal phrase - ⚠️ Treat source text as public notice content, not legal advice
Troubleshooting: no results
Try a wider date range, a partial entity name, or remove optional court and signature filters.
The archive can legitimately have no notices for a particular entity and period.
Troubleshooting: a notice is missing text
The actor returns the public detail response supplied by MSiG.
Use detailUrl or downloadUrl to inspect the official source directly.
Data freshness
The actor queries the source at run time.
scrapedAt tells you when this actor retrieved the record; publicationDate is the official MSiG publication date.
Legality and responsible use
Use public MSiG data lawfully and in accordance with your organization’s compliance policies.
Do not use output as the sole basis for legal, credit, or employment decisions.
FAQ
Does this actor bypass access controls?
No. It calls public archive endpoints available without a login.
Does it download documents automatically?
It returns the official download URL for every saved notice.
Can I monitor multiple companies?
Run separate scheduled inputs per company or combine downstream datasets using noticeId.
Is browser automation required?
No. The first release uses the public HTTP API for reliable, efficient retrieval.
Related scrapers
For related public-registry workflows, see KRS Full Names Scraper.
For broader compliance pipelines, export this actor’s dataset and join it to your internal company records.
Limitations
Availability and searchable fields are controlled by the public MSiG archive.
The actor does not interpret notices, guarantee legal completeness, or replace professional advice.
Support
Include your input filters, run ID, and one noticeId when reporting an issue.
This helps reproduce public-source behavior without sharing unnecessary data.
Version
Initial release: public MSiG search, detail enrichment, official source URLs, bounded pagination, and retry handling.