Skip to content

Data Matching API (2)

This API provides services for maintaining matching definitions used as configuration for matching jobs, as well as services for matching data with a job.

Overview
URL

https://www.cdq.ch/team

Sebastian Kaczmarski

sebastian.kaczmarski@cdq.ch

Languages
Servers
Mock server

https://idp.cdq.com/_mock/apis/data-matching-api/api-v2/

Production SOAP

https://api.corporate-data-league.ch/data-matching/soap/v2/

Production

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

Business Partner

Provides functionalities for managing business partners. These endpoints support matching business partners against data matching definitions, ensuring comprehensive analytics for data matching activities.

Operations

Analytics

Provides functionalities for generating and polling data matching reports. These endpoints support creating reports and checking their status, ensuring comprehensive analytics for data matching activities.

Operations

Build Matching Reports

Request

Requests the building of data matching reports.

Security
basicAuth
Headers
X-Credential-Usernamestringrequired

Parameter used for passing the username. The header can take form of:

  • username (e.g. "lukaszmichta")
  • user id (e.g. "87b1bdb1-ba87-4522-b363-c5a0e6e917b3")
Example: 87b1bdb1-ba87-4522-b363-c5a0e6e917b3
Bodyapplication/jsonrequired

cmd

matchingJobIdstring(JobId)

Unique identifier of a job.

Example: "35f23c03-1c22-45fe-9484-3ffe769325de"
reportsConfigurationobject(MatchingReportsConfiguration)

Configuration for generating matching reports.

tagsArray of strings(JobTags)<= 10 items

List of tags that can be used to tag the job.

Example: ["Custom tag"]
curl -i -X POST \
  -u <username>:<password> \
  https://idp.cdq.com/_mock/apis/data-matching-api/api-v2/public/matchingreports \
  -H 'Content-Type: application/json' \
  -H 'X-Credential-Username: 87b1bdb1-ba87-4522-b363-c5a0e6e917b3' \
  -d '{
    "matchingJobId": "35f23c03-1c22-45fe-9484-3ffe769325de",
    "reportsConfiguration": {
      "duplicateMatching": {
        "build": "false",
        "includeSingles": "false"
      },
      "duplicateConsolidation": {
        "build": "false",
        "includeSingles": "false"
      },
      "linkage": {
        "build": "false",
        "includeSingles": "false"
      }
    },
    "tags": [
      "Custom tag"
    ]
  }'

Responses

OK

Bodyapplication/json
idstring(JobId)

Unique identifier of a job.

Example: "35f23c03-1c22-45fe-9484-3ffe769325de"
statusstring(schemas-JobStatus)

Job execution status.

Example: "RUNNING"
statusMessagestring(JobStatusMessage)

Additional information to explain the status.

Example: "The job failed because storage is empty."
createdAtstring(CreatedAt)

Date of creation (ISO 8601-compliant).

Example: "2020-08-31T16:47+00:00"
startedAtstring

ISO 8601 representation of the timestamp when the Matching Report was created.

Example: "2019-08-31T16:47:00.000Z"
finishedAtstring

ISO 8601 representation of the timestamp when the Matching Report was finished.

Example: "2019-08-31T16:47:00.000Z"
userstring(UserId)

Unique ID of a user.

Example: "johndoe"
attachmentsArray of objects(Attachment)

List of attachments that are part of the report.

progressinteger(JobProgress)[ 0 .. 100 ]

Progress (%) of the job.

Example: "77"
reportsConfigurationobject(MatchingReportsConfiguration)

Configuration for generating matching reports.

Response
application/json
{
  "id": "35f23c03-1c22-45fe-9484-3ffe769325de",
  "status": "RUNNING",
  "statusMessage": "The job failed because storage is empty.",
  "createdAt": "2020-08-31T16:47+00:00",
  "startedAt": "2019-08-31T16:47:00.000Z",
  "finishedAt": "2019-08-31T16:47:00.000Z",
  "user": "johndoe",
  "attachments": [
    { … }
  ],
  "progress": "77",
  "reportsConfiguration": {
    "duplicateMatching": { … },
    "duplicateConsolidation": { … },
    "linkage": { … }
  }
}

Poll Matching Reports

Request

Polls the status of the matching reports.

Security
basicAuth
Path
idstringrequired

ID of the matching report.

Example: 65dcc3c60cecd503bcc88c92
Headers
X-Credential-Usernamestringrequired

Parameter used for passing the username. The header can take form of:

  • username (e.g. "lukaszmichta")
  • user id (e.g. "87b1bdb1-ba87-4522-b363-c5a0e6e917b3")
Example: 87b1bdb1-ba87-4522-b363-c5a0e6e917b3
curl -i -X GET \
  -u <username>:<password> \
  https://idp.cdq.com/_mock/apis/data-matching-api/api-v2/public/matchingreports/65dcc3c60cecd503bcc88c92 \
  -H 'X-Credential-Username: 87b1bdb1-ba87-4522-b363-c5a0e6e917b3'

Responses

OK

Bodyapplication/json
idstring(JobId)

Unique identifier of a job.

Example: "35f23c03-1c22-45fe-9484-3ffe769325de"
statusstring(schemas-JobStatus)

Job execution status.

Example: "RUNNING"
statusMessagestring(JobStatusMessage)

Additional information to explain the status.

Example: "The job failed because storage is empty."
createdAtstring(CreatedAt)

Date of creation (ISO 8601-compliant).

Example: "2020-08-31T16:47+00:00"
startedAtstring

ISO 8601 representation of the timestamp when the Matching Report was created.

Example: "2019-08-31T16:47:00.000Z"
finishedAtstring

ISO 8601 representation of the timestamp when the Matching Report was finished.

Example: "2019-08-31T16:47:00.000Z"
userstring(UserId)

Unique ID of a user.

Example: "johndoe"
attachmentsArray of objects(Attachment)

List of attachments that are part of the report.

progressinteger(JobProgress)[ 0 .. 100 ]

Progress (%) of the job.

Example: "77"
reportsConfigurationobject(MatchingReportsConfiguration)

Configuration for generating matching reports.

Response
application/json
{
  "id": "35f23c03-1c22-45fe-9484-3ffe769325de",
  "status": "RUNNING",
  "statusMessage": "The job failed because storage is empty.",
  "createdAt": "2020-08-31T16:47+00:00",
  "startedAt": "2019-08-31T16:47:00.000Z",
  "finishedAt": "2019-08-31T16:47:00.000Z",
  "user": "johndoe",
  "attachments": [
    { … }
  ],
  "progress": "77",
  "reportsConfiguration": {
    "duplicateMatching": { … },
    "duplicateConsolidation": { … },
    "linkage": { … }
  }
}

Data Matching

Provides functionalities for managing Data Matching Definitions, which are configurations for matching jobs to identify duplicates or link records across data sources. These endpoints support creating, reading, updating, and deleting these configurations.

Operations

Duplicate Matching

Provides functionalities for managing duplications within a single data source. These endpoints support creating Deduplication Job and checking the Deduplication Job Status.

Operations

Entity Matching

Provides functionalities for matching business partners. These endpoints support matching business partners against data matching definitions, ensuring comprehensive analytics for data matching activities.

Operations

Identity Resolution

Provides functionalities for managing identity resolution configurations and operations.

Operations

Linkage Matching

Provides functionalities for managing linkages across multiple data sources. These endpoints support creating Linkage Job and checking the Linkage Job Status.

Operations

Public

Provides functionalities for polling the Matching Reports.

Operations

User Feedback

Provides functionalities for managing user feedback related to data matching decisions.

Operations

Configurations

Operations