Jurisdictions
How the API works in every jurisdiction, and the guide for each one
The API is called the same way in every jurisdiction; this page covers that. Each jurisdiction page covers what differs: the operations available, how to search, the identifiers used, the documents you can order, and whether you need your own registry account.
How to read a jurisdiction page
Each page lists operations with a platform-wide status. To compare jurisdictions side by side, use the coverage matrix.
| Status | What it means |
|---|---|
| Live | Callable now. |
| Credentialed | Callable once you have connected your own registry account. See below. |
| Limited access | Available, but switched on per organisation. Ask us to enable it. |
| Coming soon | Not available here yet. Calling it returns an error, so do not build against it until it is live. |
| On request | We can fulfil it, but not through a self-service API call. |
An operation that is not listed is not available there.
Every jurisdiction page has the same sections in the same order. A section with nothing to show for that jurisdiction says so in one line rather than disappearing, so two pages can be compared side by side.
The Data sources tables name the registers used for Basic information and Finances (under Company report) and for Legal Representatives, Shareholders and UBOs (under Officers and ownership). Only available categories are listed. Where researched, a short note identifies the underlying register records and filings used. Filings describe the company at their filing or reporting date. Multiple registers mean the source depends on the company or that several records can contribute; they do not promise every field for every company.
The Company report fields table lists the fields the company report returns in that jurisdiction and the registers that supply each one; a dash means the register is not named. A listed field is filled only when the register holds it for that company.
The Legal forms, Company statuses and Roles tables list the values
the register uses and what the company report returns for each:
legalForm.normalized, category and iso20275LegalFormCode;
status.normalized and isActive; a role's englishTranslation and
normalized. A linked column heading leads to what its values mean on
Normalized values. The register value is what the report
returns as original,
though its case can differ. A value listed twice is used by the register for
two kinds of company, such as a domestic and a foreign registration, and each
row gives one result. A dash means the report returns no value there. A role
with no normalized value listed is normalized from each record's wording. A
jurisdiction without one of these tables still returns the fields; its values
are simply not listed.
For the records used in a particular result, inspect its sources and the
source references attached to individual values. A shareholder graph can cross
jurisdictions; its subsequent companies use the sources documented on their own
jurisdiction pages. Registered beneficial owners and ownership derived from
shareholders are different evidence and should be read separately.
Status is platform-wide. Whether your organisation may call an operation also
depends on your entitlements.
GET /v2/platform/jurisdictions
returns the status of every operation per jurisdiction, plus an enabled flag
scoped to your API key.
The operations
A jurisdiction page lists the operations available there. What each one does is the same everywhere:
| Operation | What it does |
|---|---|
| Autocomplete | Type-ahead company name lookup. |
| Company search | Find a company by name or identifier. |
| Company report | Registered details for one company. |
| Shareholder graph | Ownership structure, traversed through corporate shareholders. |
| Beneficial owners | Ultimate beneficial owners for one company. |
| Financials | Filed figures as structured data. |
| List documents | What this company has on file. |
| Retrieve a document | Fetch a filing as a PDF. |
| Prefill | Fill a form from a company identifier. |
Finding and identifying a company
kausateId— for exampleco_de_4JFFrsbQ99t1nmRw2JgzmG. Search returns it and it is stable: if a company is re-identified, the old ID keeps resolving. Report, ownership, financials and document operations take only this, so search first, then order.- Name or registration number — send
companyNameorcompanyNumberto search with thejurisdictionCode.companyNameworks wherever search is available.companyNumberis matched against that jurisdiction's identifier schemes and is not supported everywhere; the jurisdiction page says whether it is. advancedQuery— jurisdiction-specific search fields. Austria takesfnr,gisaCodeandzvrNumber; Italy takesrea,partitaIvaandcciaa; Germany takes a court, a register type and a register number.
The fields and combinations a register accepts are listed under Search on
its jurisdiction page. The identifier schemes that appear in a company's
identifiers are listed under Identifiers.
Ordering data
Every data operation can be called two ways:
- Asynchronous — returns an order immediately. Poll it, or receive a webhook when it completes.
- Synchronous — waits and returns the finished result.
Asynchronous is the default because registers can be slow. A report, ownership, financials or document order repeated on the same day is charged once. See Requests: sync & async for endpoints, polling, webhooks and timeouts.
Ordering documents
A document is ordered in one of three ways. The Documents table on each jurisdiction page says which applies:
- By shortcut — a name such as
register_extractorannual_accountsthat works in every jurisdiction that has that document. - By product code — for a document with no shortcut, such as
DEHRSI. The code goes in the same field as a shortcut. - By document ID — for filings that differ per company. Call list documents first, then order the ID it returns.
Connecting your own registry credentials
For most registers your Kausate API key is all you need. A few grant access only to a named entity, so there you connect your own registry account and we authenticate as you. A jurisdiction page says under Your own registry account, in Coverage at a glance, whether this applies and which fields that register expects.
Store the credentials
Send them to Create Integration with the datasource and the fields from the jurisdiction page:
curl -X POST "https://api.kausate.com/v2/integrations" \
-H "X-API-Key: $API_KEY" \
-H "Kausate-Version: 2026-08-01" \
-H "Content-Type: application/json" \
-d '{
"datasourceSlug": "de-transparenzregister",
"secretValues": {
"email": "registered-entity@example.com",
"password": "the-account-password"
}
}'The response does not include the values:
{
"datasourceSlug": "de-transparenzregister",
"datasourceName": "Transparenzregister",
"createdAt": "2026-06-06T10:00:00Z",
"updatedAt": "2026-06-06T10:00:00Z"
}Credential values are write-only: no endpoint returns them. Manage them with List, Update to rotate a password, and Delete.
Keep multiple customers separate
If you act for several end customers, store each customer's account under a
customerId:
curl -X POST "https://api.kausate.com/v2/integrations?customerId=acme-bank" \
-H "X-API-Key: $API_KEY" \
-H "Kausate-Version: 2026-08-01" \
-H "Content-Type: application/json" \
-d '{
"datasourceSlug": "de-transparenzregister",
"secretValues": { "email": "kyb@acme-bank.example", "password": "..." }
}'customerId must be URL-safe (letters, numbers, dashes, underscores) and at
most 150 characters. Omit it to store one set at the organisation level, used
for every call.
Call with those credentials
Send the customerId in the X-Customer-Id header. It selects the credential
set and scopes the order to that customer:
curl -X POST "https://api.kausate.com/v2/companies/ubo" \
-H "X-API-Key: $API_KEY" \
-H "Kausate-Version: 2026-08-01" \
-H "X-Customer-Id: acme-bank" \
-H "Content-Type: application/json" \
-d '{ "kausateId": "co_de_4JFFrsbQ99t1nmRw2JgzmG" }'Send the same header when polling the order. Omit it to use the organisation-level credentials. A call to a credentialed source with no credentials stored returns an error.
When something goes wrong
Errors have the same body, status codes and code values in every
jurisdiction. See Errors, including how a failed
asynchronous order is reported.
All jurisdictions
Type a name or a jurisdiction code to find one. Each card shows how many registers that jurisdiction's data comes from.
229 jurisdictions
Europe51
al1 source
at6 sources
by1 source
be2 sources
ba3 sources
bg2 sources
hr2 sources
cy1 source
cz4 sources
dk1 source
ee1 source
fo2 sources
fi1 source
fr6 sources
ge1 source
de4 sources
gi1 source
gr1 source
gl1 source
gg1 source
hu3 sources
is1 source
ie1 source
im1 source
it1 source
je1 source
xk1 source
lv1 source
li1 source
lt1 source
lu1 source
mt1 source
md1 source
mc1 source
me1 source
nl1 source
mk1 source
no1 source
pl6 sources
pt1 source
ro2 sources
ru2 sources
rs2 sources
sk4 sources
si1 source
es4 sources
se4 sources
ch1 source
tr2 sources
ua3 sources
gb1 source
Americas112
ai1 source
ag1 source
ar4 sources
aw1 source
bs1 source
bb1 source
bz1 source
bm1 source
bo1 source
bq1 source
br2 sources
ca1 source
ky2 sources
cl3 sources
co1 source
cr1 source
cu1 source
cw1 source
dm1 source
do3 sources
ec2 sources
sv1 source
fk1 source
gf6 sources
gp6 sources
gt1 source
gy1 source
ht1 source
hn1 source
jm1 source
mq6 sources
mx2 sources
ms1 source
ni2 sources
pa1 source
py2 sources
pe1 source
pr1 source
bl6 sources
kn1 source
lc1 source
mf6 sources
vc1 source
tt1 source
us1 source
uy3 sources
ve2 sources
vg1 source
vi1 source
Canada12
ca-ab2 sources
ca-bc2 sources
ca-mb2 sources
ca-nl1 source
ca-nt1 source
ca-ns1 source
ca-nu1 source
ca-on1 source
ca-pe1 source
ca-qc1 source
ca-sk1 source
ca-yt1 source
United States51
us-al1 source
us-ak1 source
us-az1 source
us-ar1 source
us-ca1 source
us-co1 source
us-ct1 source
us-de1 source
us-dc1 source
us-fl1 source
us-ga1 source
us-hi1 source
us-id1 source
us-il1 source
us-in1 source
us-ia1 source
us-ks1 source
us-ky1 source
us-la1 source
us-me1 source
us-md1 source
us-ma1 source
us-mi1 source
us-mn1 source
us-ms1 source
us-mo1 source
us-mt1 source
us-ne1 source
us-nv1 source
us-nh1 source
us-nj1 source
us-nm1 source
us-ny1 source
us-nc1 source
us-nd1 source
us-oh1 source
us-ok1 source
us-or1 source
us-pa1 source
us-ri1 source
us-sc1 source
us-sd1 source
us-tn1 source
us-tx1 source
us-ut1 source
us-vt1 source
us-va1 source
us-wa1 source
us-wv1 source
us-wi1 source
us-wy1 source
Asia Pacific35
am1 source
au4 sources
az2 sources
bd1 source
bt2 sources
bn1 source
cn2 sources
pf1 source
hk1 source
in1 source
id1 source
jp2 sources
kz1 source
kg1 source
la2 sources
mv1 source
mh1 source
mn3 sources
mm1 source
np1 source
nc1 source
nz1 source
pk1 source
pg1 source
ws1 source
sg1 source
sb1 source
kr1 source
tw2 sources
tj1 source
th1 source
to1 source
uz1 source
vu1 source
vn2 sources
Middle East & Africa30
dz1 source
ao1 source
bh1 source
cm1 source
eg1 source
et1 source
gh1 source
iq2 sources
il2 sources
jo1 source
lr3 sources
mg1 source
mw1 source
mu2 sources
yt6 sources
ma1 source
mz1 source
na1 source
ng2 sources
qa1 source
re6 sources
rw1 source
sa2 sources
sc3 sources
tz1 source
tn1 source
ug1 source
ae9 sources
zm1 source
zw1 source
Testing1
Last updated on