Retry a single failed record from a prior import
Dmp Import
Retry a single failed record from a prior import
POST /dmp/import/retry-record
POST
Retry a single failed record from a prior import
This endpoint requires authentication. Include your Bearer token in the Authorization header.
Description
POST /dmp/import/retry-record Description: Re-runs the full import phase pipeline (writers → … → acknowledgements) for exactly one work record, in its own transaction — commits only if every phase produces zero errors, otherwise rolls back and returnsstatus: failed. Intended for
re-processing a record that errored during a prior
/dmp/import/execute call, optionally with overrides shallow-merged
onto the original record to fix the field that caused the failure.
importJobId is a client-generated session id scoping a batch of
retries. Idempotency: a retry of the same
(tenantId, importJobId, recordIndex) within a 1-hour window replays
the cached response instead of re-processing — this is separate
from (and in addition to) the standard Idempotency-Key header
support also wired on this route.
Authorization:
- Required role:
useror higher - Requires an active
publisheraddon
Code Examples
Authorizations
JWT Authorization header using the Bearer scheme. Format: "Bearer {token}"
Headers
Body
application/json
Client-generated id identifying the originating import batch.
0-based index of this record in the original works[] array.
Required range:
x >= 0The single DMP work record to re-process (same shape as one entry in the original worksFile's works[]). Must include at minimum code and work_title.
Optional field-level corrections, shallow-merged onto record before reprocessing.
Optional acknowledgement CSV rows for this record (usually empty on retry).
Response
Record reprocessed (check status — a 200 is returned for both success and failed outcomes)