Replay practitioner.terminated webhooks for given practitioners
POST/webhooks/replay/practitioner-terminated
Accepts a list of certifyPractitionerIds and asynchronously republishes the practitioner.terminated event for each one. Returns 202 immediately; replay runs in the background and there is no polling endpoint to track completion. Progress is logged server-side under the [termination-webhook-replay] prefix.
Each event is rebuilt from the practitioner's current record (npi, terminationDate, terminationReason), so subscribers receive the same payload shape as the original delivery. Exception: terminationType is not persisted with the termination and cannot be reconstructed — the replayed payload carries the terminationType supplied in this request, or an explicit null when it is omitted.
A practitioner with no recorded terminationDate is skipped rather than published: there is no termination to report. Ids that cannot be loaded are logged and skipped so one bad entry cannot abort the batch.
This delivers to live subscriber endpoints. Replays are published on the dedicated overflow queue so a large batch cannot starve normal single-event delivery, and are capped at 500 practitioners per request.
Request
Responses
- 202
- 400
- 401
- 500
Replay accepted and processing in the background
Invalid request - empty certifyPractitionerIds, a blank id, or more than 500 entries
Unauthorized - Authentication required
Internal Server Error - An unexpected error occurred