---
title: "Data pipeline callback"
method: POST
path: "/credentialing-workflows/data-pipeline-callback"
tags: ["CredentialingWorkflow"]
---

# Data pipeline callback

`POST /credentialing-workflows/data-pipeline-callback`

Receives callback from DI team after MDM Orchestration completes. Marks workflow data-pipeline status and syncs practitioner OV sections. The pipeline is identified by the referenced data pipeline request's pipelineName (CAQH, NPDB or LICENSE), not by the request body. The referenced request must already carry a CROSSWALK_INGESTION step in SUCCESS or ERROR status. CAQH and NPDB callbacks sync while the workflow is in any editable status; LICENSE (ODDP state license) callbacks sync only while the workflow is still NOT_STARTED and otherwise return 200 with status "skipped" and the skip reason.

## Headers

- `tenant-id` string, required
- `user-id` string

## Request body

- DataPipelineCallbackRequest
  - `dataPipelineRequestId` string, required
  - `eventSource` string

## Response `200`

Callback processed successfully

- DataPipelineCallbackResponse
  - `status` string
  - `message` string
  - `workflowId` string
  - `dataPipelineRequestId` string

## Other responses

- `400` — Bad request - missing or invalid parameters
- `401` — Invalid or missing X-Credentialing-Api-Key
- `404` — Data pipeline request not found
- `500` — Internal server error

---

[API](https://skmtc.net/certifyos/apis/certify-api-layer.md) · [All operations](https://skmtc.net/certifyos/apis/certify-api-layer/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/certifyos/certify-api-layer/revisions/563848e0ecc0/schema)