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

Read Concept Metadata

Request

Provides basic metadata for a concept, identified by its technical key.

Security
basicAuth
Path
technicalKeystringrequired

Technical key of the concept.

Example: BUSINESS_PARTNER_NAME_TYPE
Query
parentConceptTechnicalKeystring

Optional parameter useful when the concept of a technicalKey is not unique.

Example: parentConceptTechnicalKey=ADDRESS_TYPE
curl -i -X GET \
  -u <username>:<password> \
  https://idp.cdq.com/_mock/apis/metadata-api/api-v5/v3/concepts/BUSINESS_PARTNER_NAME_TYPE

Responses

OK

Bodyapplication/json
urlstring

URL of the concept.

Example: "https://meta.cdq.com/Category:Data_model_concept"
namestring

Name of the concept.

Example: "Address"
technicalKeystring

Technical key of the concept.

Example: "ADDRESS"
parentConceptTechnicalKeystring

Technical key of the parent concept.

Example: "BUSINESS_PARTNER"
descriptionstring

Description of the concept.

Example: "Address data."
Response
application/json
{
  "url": "https://meta.cdq.com/Category:Data_model_concept",
  "name": "Address",
  "technicalKey": "ADDRESS",
  "parentConceptTechnicalKey": "BUSINESS_PARTNER",
  "description": "Address data."
}

List Data Model Value Mappings

Request

Provides metadata on mappings from values of external data models to values of CDQ Data Model.

Security
basicAuth
Query
dataSourcePrefixstring

Alei prefix of the database to load values for.

Example: dataSourcePrefix=CDQ.POOL
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/datamodelvaluemappings

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(DataModelValueMapping)

List of data model value mappings.

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

Read Objects By Subject And Property

Request

Provides objects from knowledge graph for a given subject and a given property. Generic endpoint to browse metadata.

Security
basicAuth
Query
subjectstringrequired

Subject in terms of triple representation, without base URI.

Example: subject=Dummy post-code detected (MK)
predicatestringrequired

Predicate in terms of triple representation, without base URI and wiki prefix 'Property:'

Example: predicate=Has_country_scope
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/objects?subject=Dummy+post-code+detected+%28MK%29&predicate=Has_country_scope'

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(StatementObject)

List of statement object metadata.

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

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

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