EU Insolvencies & Restructurings,
one polling API.
Every distressed filing and judicial auction across 16 European markets — aggregated, normalized, tier-graded for freshness, and pollable with a one-line curl. Self-serve trial key, no intro call required to look at the data.
European registries use disparate formats and languages. We absorb the maintenance overhead.
We do not use third-party aggregators. We ingest directly from local government registries via proprietary pipelines, ensuring full compliance and eliminating multi-hop data corruption. You get a perfectly structured JSON contract that never breaks.
Data is normalized and available the morning after it is published by the registry.
Whether it's a UK Administration or a French Redressement, the JSON shape remains identical.
Ingested strictly from official state registries, avoiding secondary aggregator hallucination.
We caught the Administration filing 42 days before the Liquidation.
On May 21st, 2024, our pipeline ingested a Notice of Appointment of an Administrator for a major UK automotive retailer (Reg ID: 11664165) published via The London Gazette. The API delivered this row the next morning.
On July 2nd, 2024, the company entered Creditors' Voluntary Liquidation. Your model would have received the initial distressed signal 42 days before the assets hit the final liquidation stage. We track the entire lifecycle across 16 jurisdictions using the exact same schema.
What you actually get — live numbers
Every cell below comes from the same Postgres views our API serves. No marketing decoration.
Corporate Insolvencies (Pan-European)
Granular Data Coverage
Same JSON schema everywhere. What varies is enrichment depth from the host registry.
Sample Row
Field-by-field documentation available in the Schema Doc.
{
"id": "uk-2024-05-21-11664165",
"country": "UK",
"name": "CAZOO LTD",
"stage": "Administration",
"registrationId": "11664165",
"sector": "Retail",
"filed_date": "2024-05-21",
"source_url": "https://www.thegazette.co.uk/notice/4631315",
"last_seen_at": "2024-05-22T02:30:35Z"
}The API is one endpoint
/api/v1/insolvencies is the only endpoint you need. Load data directly into a Pandas DataFrame.
import requests
import pandas as pd
# Fetch delta payload for everything since yesterday
headers = {"Authorization": "Bearer ms-live-xxx..."}
url = "https://acquireeu.com/api/v1/insolvencies?since=2026-06-29T22:00:00Z"
response = requests.get(url, headers=headers)
# Load into DataFrame
df = pd.DataFrame(response.json()["data"])
print(df[["name", "stage", "filed_date", "registrationId"]].head())curl -H "Authorization: Bearer ms-live-xxx..." \ "https://acquireeu.com/api/v1/insolvencies?country=UK&date_from=2026-06-20"
How you receive it
REST is the self-serve default. The other two are real options — ask and we'll set them up.
Polling REST API
Bearer auth, cursor + delta-since pagination. The trial key plugs in here. Build orchestration around it.
PostgreSQL Direct
Connection string into our Read-Replica. Your engineers write SQL, no pagination ceiling. Best when you want absolute flexibility.
Snowflake / AWS S3
Atomic nightly snapshot in Parquet or CSV. Drop directly into your data lake on a schedule. Zero API engineering required.
Why AcquireEU vs the incumbents
vs Generic Aggregators
Most aggregators buy their EU data from a secondary vendor, who bought it from a scraping farm. We maintain the scrapers natively. If a registry changes, we fix it same-day, not next month.
vs Terminals (Bloomberg/Pitchbook)
Terminals charge per-seat and force analysts to use clunky Excel plugins. We provide an API-first headless data feed for your quant models, with zero front-end lock-in and flat licensing.
vs Building it Yourself
14 regulators means 14 different HTML/PDF parsers. Building them takes 6 months of engineering; maintaining them when courts redesign their websites is a permanent tax on your data team.
Everything You Need to Know Before Buying
Do you provide LEIs or standard entity identifiers?
We pass through the native national registration IDs (e.g., UK Company Number, FR SIREN) to preserve absolute ground-truth accuracy. We do not attempt fuzzy matching on our end. If LEI mapping is a hard requirement for your pipeline, we can enable a deterministic GLEIF integration for production licenses.
What happens when a country changes its registry portal?
This is the primary reason funds buy this feed instead of building it. We absorb all maintenance overhead. If the French registry updates its HTML structure overnight, our internal monitoring alerts us, and we patch the parser within hours. Your JSON schema contract never breaks.
Can we pull 5+ years of historical data for backtesting?
Our REST API is optimized as a live, forward-looking feed for T+1 signals. For historical backtesting, we provide static data dumps (CSV or Parquet format) for the specific jurisdictions you need. Historical depth varies by country (usually 2 to 7 years) based on what is legally accessible.
How do you handle data privacy and compliance?
We ingest directly from public government registries using logged-out, public access paths. We comply fully with registry Terms of Service. Our pipeline guarantees clean provenance without violating third-party platform agreements. Every row carries a `source_url` pointing directly back to the original filing.
What is the exact ingestion latency?
We operate on a T+1 basis. Our bulk pipelines run nightly between 00:00 and 04:00 UTC. Filings published by a court on Tuesday are normalized, translated, and available in the API by Wednesday morning. We do not offer intraday polling at this time.
Do you support Snowflake, S3, or direct DB connections?
Yes. While REST is the default, Enterprise production licenses include the option for direct Postgres read-replica access (write SQL directly against our schema), or automated nightly Parquet dumps to an AWS S3 bucket.
Do you offer a contractual SLA?
For Enterprise customers, yes. We provide a custom SLA guaranteeing pipeline uptime and parser repair timeframes. However, we cannot guarantee upstream registry uptime (if the German government portal goes offline, we cannot fetch data until they return).
What are the Sandbox API limits?
The trial Sandbox key you request below is restricted in two ways to protect our IP: (1) It only returns data for Tier 1 countries, and (2) It enforces a strict 3-day trailing lookback window. It is designed solely to validate our schema shape and connectivity.
Will you add more countries to Tier 1?
Yes. We are constantly upgrading Tier 2 countries to Tier 1 as we establish more robust, fail-safe extraction methods for their respective registries. Enterprise clients can sponsor specific jurisdictions to accelerate their roadmap priority.
Request a sample
Download a static 20-row sample of perfectly normalized UK insolvency data to test against your internal models immediately. No signup required.
Get a 7-day trial key
Apply for a free 7-day API sandbox key restricted to our Tier 1 jurisdictions to backtest the live feed.
Ready to talk integration?
Book 15 minutes with the Founder to walk through the schema, your ingestion pipeline, and custom coverage options.
Book your demo call →What we're honest about
- — Tier is per-country: Every row carries its country's tier so you can filter at query time.
- — Source-side delays are surfaced: If the Spanish court publishes a filing 6 days late, we don't hide that. It's flagged in the data.
- — No financial advice: We are a data infrastructure layer. We do not provide investment advice, credit scores, or predictive analytics overlays.