Confirm or reject match candidates

POST/api/v1/advisory-firms/{firm_id}/candidates/bulk-resolve

Confirming applies the booking side effects: same-business pairs retarget to the transfers ledger, cross-entity pairs book due-to/due-from plus an elimination entry, parent legs book due-from-parent on our side only. Every confirmation also feeds rule learning and the account map's known description strings.

Operation ID: bulk_resolve_candidates_api_v1_advisory_firms__firm_id__candidates_bulk_resolve_post·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Parameters

Path

firm_idstringrequired

Request body

Schema: BulkResolveRequest

candidate_idsarray · stringrequired
actionstringrequired: 'confirm' or 'reject'

Responses

201Successful Response

Schema: SuccessEnvelope_BulkResolveResponse_

successboolean
messagestring
codestring
dataBulkResolveResponse

401Unauthorized - Authentication required

403Forbidden - Insufficient permissions

404Not Found - Resource does not exist

422Validation Error - Invalid data format

Code samples

POST/api/v1/advisory-firms/{firm_id}/candidates/bulk-resolve

bash

curl -X POST 'https://api.ondayzero.com/api/v1/advisory-firms/{firm_id}/candidates/bulk-resolve' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "candidate_ids": [],
  "action": "string"
}'