Skip to content

Metadata API (5)

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.

Languages
Servers
Mock server

https://idp.cdq.com/_mock/apis/metadata-api/api-v5/

Production SOAP

https://api.corporate-data-league.ch/metadata-api/soap/v5/

Production

https://api.corporate-data-league.ch/metadata-api/

Knowledge Graphs

-> Categorize the API endpoints related to operations on Knowledge Graphs. These operations include reading Knowledge Graphs, reading a Knowledge Graph by ID, downloading a Knowledge Graph, reading Business Rules, and getting custom validation settings.

Operations

SAP mappings

-> Categorize the API endpoints related to operations on SAP identifier mappings. These operations include reading SAP identifier mappings and analyzing SAP identifier mappings.

Operations

APIs

-> 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.

Operations

Character Sets

-> 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.

Operations

Concepts

-> 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.

Operations

Counties

-> 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.

Operations

Countries

-> 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.

Operations

DataSources

-> 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.

Operations

Identifiers

-> Categorize the API endpoints related to operations on identifiers. These operations include getting a list of identifier issuing bodies, which can be filtered and paged by optional query parameters. The metadata provided includes technical keys, names, descriptions, jurisdictions, and associated identifier types among others.

Operations

List Issuing Bodies

Request

Provides a list of identifier issuing bodies, paged by optional query parameters. Country short name can be used for filtering.

Security
basicAuth
Query
technicalKeystring

Technical key of the issuing body.

Example: technicalKey=DE_RA000197
languageTechnicalKeystring

Language technical key, i.e., the 2-char ISO code.

Example: languageTechnicalKey=EN
jurisdictionCountryShortNamestring

Country short name of the jurisdiction, i.e., the 2-digit ISO code.

Example: jurisdictionCountryShortName=DE
jurisdictionAdministrativeAreasRegionIsoCodestring

Technical key of the region, i.e., the 2-digit ISO code.

Example: jurisdictionAdministrativeAreasRegionIsoCode=DE-NW
jurisdictionAdministrativeAreasCountyValuestring

Value of the region.

Example: jurisdictionAdministrativeAreasCountyValue=Aachen
gleifCodestring

International identifier of the local authority which issues the identifier.

Example: gleifCode=RA000274
localAuthorityCodestring

Identifier of the local authority which issues the identifier.

Example: localAuthorityCode=T3201
namestring

Name of the issuing body, matches case-insensitive.

Example: name=Amtsgericht Ulm
identifierTypeTechnicalKeystring

Technical key of the identifier, matches case-insensitive.

Example: identifierTypeTechnicalKey=Amtsgericht Ulm
pageinteger

The number of the page to read, starting with '0'.

Default 0
Example: page=1
pageSizeinteger

Maximum number of elements on the page to read.

Default 10
Example: pageSize=10
curl -i -X GET \
  -u <username>:<password> \
  https://idp.cdq.com/_mock/apis/metadata-api/api-v5/v5/identifiers/issuingbodies

Responses

OK

Bodyapplication/json
pageSizeinteger(PageSize)

< The size of the provided page, as specified in the request, or by the default value.

Example: "10"
pageinteger(Page)

< The number of the page, as specified in the request, or '0' as default.

Example: "1"
totalinteger(Total)

< Total number of elements across all pages.

Example: "100"
valuesArray of objects(IssuingBodyMetadata)

List of issuing body metadata.

Response
application/json
{
  "pageSize": "10",
  "page": "1",
  "total": "100",
  "values": [
    { … }
  ]
}

List Identifier Metadata

Request

Provides a list of identifier metadata, paged by optional query parameters. Optional filter parameters, e.g., short name for country or SAP codes can be used to filter results.

Security
basicAuth
Query
countryShortNamestring

Country short name, i.e., the 2-digit ISO code.

Example: countryShortName=CH
sapDefaultMappingstring

SAP identifier code to filter results. Together with country short name, these parameters provide metadata for a specific identifier.

Example: sapDefaultMapping=STCD1
sapTaxCategorystring

SAP identifier for tax-related identifier, unique across countries.

Example: sapTaxCategory=BR1
technicalKeystring

Technical key of a specific identifier.

Example: technicalKey=EU_VAT_ID_PL
pageinteger

The number of the page to read, starting with '0'.

Default 0
Example: page=1
pageSizeinteger

Maximum number of elements on the page to read.

Default 10
Example: pageSize=10
curl -i -X GET \
  -u <username>:<password> \
  https://idp.cdq.com/_mock/apis/metadata-api/api-v5/v3/identifiers

Responses

OK

Bodyapplication/json
pageSizeinteger(PageSize)

< The size of the provided page, as specified in the request, or by the default value.

Example: "10"
pageinteger(Page)

< The number of the page, as specified in the request, or '0' as default.

Example: "1"
totalinteger(Total)

< Total number of elements across all pages.

Example: "100"
valuesArray of objects(IdentifierMetadata)

List of identifier metadata.

Response
application/json
{
  "pageSize": "10",
  "page": "1",
  "total": "100",
  "values": [
    { … }
  ]
}

Languages

-> 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.

Operations

LegalForms

-> 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.

Operations

Linkage Strategies

-> 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.

Operations

Postal Delivery Points

-> 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.

Operations

Premises

-> 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.

Operations

Regions

-> 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.

Operations

Regular Expressions

-> 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.

Operations

Terms

-> 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.

Operations

Thoroughfares

-> Categorize the API endpoints related to operations on thoroughfares. These operations include reading thoroughfare metadata. The metadata provided includes thoroughfare names, thoroughfare technical keys, and thoroughfare categories.

Operations

Service Quotas

Operations

Release Notes

Operations

Compliance Lists

Operations