Download OpenAPI specification:Download
A comprehensive suite of services that provides access to CDQ metadata. It is designed to offer basic services to apply such a metadata, for instance, for parsing.
-> Categorize the API endpoints related to operations on APIs. These operations include reading API metadata. The metadata provided includes endpoint descriptions, related features, and use cases.
-> Categorize the API endpoints related to operations on character sets. These operations include reading character sets metadata. The metadata provided includes character set names and technical keys.
-> Categorize the API endpoints related to operations on concepts. These operations include reading concept metadata. The metadata provided includes concept names, technical keys, and parent concept technical keys.
-> Categorize the API endpoints related to operations on counties. These operations include reading county metadata. The metadata provided includes county names, region short names, and region values.
-> Categorize the API endpoints related to operations on countries. These operations include reading country metadata. The metadata provided includes country names, country short names, and country technical keys.
-> Categorize the API endpoints related to operations on data sources. These operations include reading data source metadata. The metadata provided includes data source names, data source technical keys, and data source categories.
Provides metadata on external data sources such as legal forms, address data, or legal entity data. Results are paged by optional query parameters and filtered by additional parameters such as country short name or concepts provided by the particular data source.
| aleiPrefix | string Prefix of the database name, according to ALEI standard. Example: aleiPrefix=DE.RC |
| countryShortName | string Country short name, i.e., the 2-digit ISO code. Example: countryShortName=CH |
| implementationStatus | string DEPRECATED, use 'releaseStatus' instead. Example: implementationStatus=ACTIVE |
| managedConceptTechnicalKey | string Technical key of a CDQ data model concept. Example: managedConceptTechnicalKey=LEGAL_FORM |
| preferredInCountry | string ISO code of a country this data source is used in as a preferred data source for compiling golden records. Example: preferredInCountry=CH |
| primaryInCountry | string ISO code of a country this data source is used in as a primary data source for compiling golden records. Example: primaryInCountry=CH |
| releaseStatus | Array of integers See https://meta.cdq.com/Property:Release_status for semantics. According to CDLD-22386 list of 4,5,6,7, corresponds to active data sources Example: releaseStatus=4,5,6,7 |
| technicalKey | string Technical key. Example: technicalKey=DE_RC |
| unallowedInCountry | string ISO code of a country this data source is not allowed to be used in for compiling golden records. Example: unallowedInCountry=CH |
OK
{- "pageSize": "10",
- "page": "1",
- "total": "100",
- "values": [
- {
- "aleiPrefix": "VIES",
- "technicalKey": "VIES",
- "shortName": "VIES",
- "fullName": "VAT Information Exchange System",
- "localName": "VAT Information Exchange System",
- "shortDescription": "Official interface to the European MIAS database.",
- "businessRegistryCode": "RA000274",
- "countryScope": "CH",
- "countryScopeList": [
- "CH"
], - "managedConceptTechnicalKeys": [
- "ADDRESS"
], - "managedIdentifierTypes": [
- "CH_VAT_ID"
], - "categories": [
- "VAT"
], - "implementationStatus": "N/A",
- "releaseStatus": "1",
- "dataOwnership": "GOVERNMENTAL",
- "dataProvision": "OPEN",
- "termsType": "EU_PUBLIC",
- "numberOfRecords": "50000000",
- "provider": "European Commission",
- "credentialTypes": [
- "USERNAME"
]
}
]
}-> Categorize the API endpoints related to operations on identifiers. These operations include reading identifier metadata. The metadata provided includes identifier names, identifier technical keys, and identifier issuing bodies.
-> Categorize the API endpoints related to operations on languages. These operations include reading language metadata. The metadata provided includes language names, language technical keys, and language codes.
-> Categorize the API endpoints related to operations on legal forms. These operations include reading legal form metadata. The metadata provided includes legal form names, legal form technical keys, and legal form categories.
-> Categorize the API endpoints related to operations on linkage strategies. These operations include reading linkage strategy metadata. The metadata provided includes linkage strategy names, linkage strategy technical keys, and linkage strategy categories.
-> Categorize the API endpoints related to operations on postal delivery points. These operations include reading postal delivery point metadata. The metadata provided includes postal delivery point names, postal delivery point technical keys, and postal delivery point categories.
-> Categorize the API endpoints related to operations on premises. These operations include reading premise metadata. The metadata provided includes premise names, premise technical keys, and premise categories.
-> Categorize the API endpoints related to operations on regions. These operations include reading region metadata. The metadata provided includes region names, region short names, and region values.
-> Categorize the API endpoints related to operations on regular expressions. These operations include reading regular expressions metadata. The metadata provided includes regular expression names, regular expression technical keys, and regular expression categories.
-> Categorize the API endpoints related to operations on terms. These operations include reading term metadata. The metadata provided includes term names, term technical keys, and term categories.