latestOpenAPI 3.1.02026-08-194237902.5 MB

563848e0ecc0

CredentialingWorkflow

Bulk-delete application-verification records from a credentialing workflow

Deletes multiple appVerifications records in one action. Each recordId uses the '{section}-{index}' format (e.g. 'appVerifications-3'); section must be appVerifications. Deletion is a single read-modify-write and hard-deletes the records (no tombstone, nothing written to deletedData), matching single-record delete behaviour for this section — which is why appVerifications has its own endpoint rather than being served by the generic section bulk-delete. Partial failures (malformed, wrong section, out-of-bounds, duplicate recordIds) are reported per record and do not block the valid deletions. NOTE: recordIds are positional, so this request must not be retried automatically — a replay after a successful-but-unseen response would delete whatever records shifted into those indices, and because this section hard-deletes with no deletedData tombstone that loss is unrecoverable. Re-fetch the section and rebuild recordIds before any retry.

post/credentialing-workflows/{workflowId}/app-verifications/bulk-delete

Path parameters

workflowIdstring required

Credentialing workflow ID

Headers

tenant-idstring required

Tenant ID

Request body

recordIdsstring[] required

Record identifiers in '{section}-{index}' format; section must be appVerifications. At most 500 per request.

Example request

{
  "recordIds": [
    "appVerifications-0",
    "appVerifications-3"
  ]
}

Response

At least one record was deleted; body reports the deleted and failed records

deletedstring[] required

Record identifiers that were successfully deleted.

Example response

{
  "deleted": [
    "appVerifications-0",
    "appVerifications-3"
  ],
  "failed": [
    {
      "recordId": "appVerifications-9",
      "reason": "Record index 9 out of bounds for section 'appVerifications' (size: 4)"
    }
  ]
}