Transparent Data pricing: company hierarchy API
Is Transparent Data yours? Write to us about this page. We invite selected tool providers to our WhatsApp group.
POST / Transparent Data's only call for this API- Business verification API
- Company hierarchy API
- Company enrichment API
POST /, TD - CEIDG JSON{key}/ add - Company enrichment API
POST /, TD - KRS CEIDG REGON JSON{key}/ add - Company enrichment API
POST /, TD - Pełny odpis KRS JSON 2.0{key}/ add - Company enrichment API
POST /, TD - Raport Prześwietl JSON{key}/ add - Company enrichment API
POST /, TD - REGON JSON{key}/ add
About this item
- Freshness. We don't know how fresh this plan's data is.
- 1 of the 3 key fields we check. Company.
- No public price. You ask Transparent Data for one.
- One call. You send
params.tax_tonumber POST /. You set{key}/ add sourceto "company_relations" andmethodto "data". You can also sendparams.depth. The call returns a job. You fetch the answer once the job is done. - Who can get it: anyone who sends its contact form: an offer and test access follow. Keep data: no API terms. Use data: no API terms.
Transparent Data: company hierarchy API alternatives
Transparent Data alternatives: every company hierarchy API provider ranked
We list other providers' plans with no public price. These plans come closest to this plan in number of key fields.
| This planTransparent Data, contact us | UC, contact us | FactSet, contact us, Personalized proposal, GET /factset-entity/v1/entity-structures | Infocredit Group, contact us, API4ALL access, GET /a4a/3.0/api/report/structure/code/{code} | Kontur.Focus, contact us, Legal entity links (Связи юридического лица), GET /api3/beneficialOwners | |
|---|---|---|---|---|---|
| Completeness | 33% | 33% | 33% | 33% | 33% |
| Billing | contact | contact | contact | contact | contact |
| Freshness | unknown | 1 day | unknown | stored | unknown |
| Who can get it | anyone who sends its contact form: an offer and test access follow | businesses that contact UC sales | clients whose FactSet account team authorizes them for the API, after a personalized proposal from its sales team | customers whose Infocredit account manager issues a username, password and project code during onboarding | a legal entity, a sole proprietor or an individual who accepts its licence contract (the buyer's name, INN, phone and email on the invoice) |
Sources
From each provider's own pricing page and docs, and from what providers tell us. We read this row from these pages on 2026-11-04.
Product details
The key fields this plan's answer can hold, then each filled column in its row on the sheet.
- Company
- Parent, not in the answer
- Family tree, not in the answer
| Billing | contact |
|---|
| Aggregators | none |
|---|
| Their pitch | company connections (with other companies & physical persons) from KRS in JSON |
|---|
| Countries | Poland |
|---|---|
| Full family tree | no |
| Keep data | no API terms |
| Use data | no API terms |
| Answer | by polling |
|---|
| You send | source "company_relations", method "data", params.tax_number. Optional: params.depth |
|---|---|
| Method | POST |
| Path | /{key}/add |
| Plan | Get your API |
|---|---|
| Who can get it | anyone who sends its contact form: an offer and test access follow |
The 20 fields the plan's answer can hold
company name, KRS number, NIP, REGON number, legal form, share capital, registered address, related company name, related company KRS number, related company NIP, related company REGON number, related company legal form, related company share capital, related company address, related person name, related person birth date, relation type, relation date, relation depth, register type