EU Insolvencies & Restructurings,
one polling API.
Every distressed filing and judicial auction across 17 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 read local government registries and court notices directly, so every row links back to its official source. Field names stay the same across countries; values a registry does not publish are left empty.
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.
Read from official registries and court notices; every row carries a link to its source.
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://www.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://www.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
Direct read-only SQL access is not offered yet. Tell us your use case and we will scope it with you.
Snowflake / AWS S3
Bulk nightly snapshot files into your data lake are not offered yet. Tell us the format you need and we will scope it with you.
Why a feed instead of building it yourself
Every country has its own registry, format and language, and registries change their pages without notice. We read them, keep the parsers current, filter the noise and put the result in one schema. You decide whether that is cheaper than maintaining it yourself.
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?
We monitor each source and repair the parser when a registry changes its format. Until it is repaired, that country can be delayed or incomplete, and the country page says what we hold. Field names stay the same.
Can we pull 5+ years of historical data for backtesting?
No. The REST API is a live, forward-looking feed and depth varies by country. Bulk historical files are not offered yet; tell us what you need and we will scope it.
How do you handle data privacy and compliance?
We read official registries and court notices through public access paths, and every row carries a source_url back to the original filing. Registry terms differ by country and we review them country by country; this is not legal advice, so check the terms for any country you rely on. Owner age is stored as a band only.
What is the exact ingestion latency?
We operate on a T+1 basis: the pipeline runs nightly, so filings published on Tuesday are normally available on Wednesday morning. Some registries publish in batches, so timing varies by country. We do not offer intraday polling at this time.
Do you support Snowflake, S3, or direct DB connections?
Not yet. REST is the default. Direct read-only SQL access and nightly bulk files are not offered yet; tell us your use case and we will scope it.
Do you offer a contractual SLA?
Not as standard. If you need uptime or repair-time commitments, tell us and we will scope it. We cannot guarantee upstream registry uptime: if a government portal goes offline, we cannot fetch data until it returns.
What are the Sandbox API limits?
The trial Sandbox key is restricted in scope (a limited set of countries and a short trailing lookback window). It is designed to validate our schema shape and connectivity.
Will you add more countries to Tier 1?
Yes. Countries move from leads to fund-grade as we build and verify their sources; the country pages show where each one stands.
Executive Pitch Deck
Download our 8-slide platform overview outlining our data coverage, technical architecture, and return on investment for your partners.
Download PDF DeckRequest 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 to test the live feed and the schema.
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.