Bulk accept payment suggestions

POST/api/v1/payment-suggestions/bulk-accept

Accept many pending invoice (deposit -> invoice) or bill (payment -> bill) match suggestions at once: the suggestion_ids you name, or every pending suggestion at or above min_confidence (default 0.85), optionally for one customer / vendor (party_id) and a bank-transaction date range. Each accept is isolated, so a bad row never loses the rest (results lists every one). The batch is one payment_match automation run: undo it with POST /automation-runs/{run_id}/undo. dry_run lists what would be accepted.

Operation ID: bulk_accept_payment_suggestions·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.

Request body

Schema: BulkAcceptPaymentSuggestionsRequest

kindstringrequired

invoice = deposits matched to invoices, bill = payments to bills

One of: invoice, bill

suggestion_idsarray · string

Accept exactly these suggestions (the filter is then ignored)

min_confidencenumber

Filter: lowest confidence to accept (default 0.85)

party_idstring

Filter: one customer (invoice) or vendor (bill)

start_datestring · date

Filter: earliest bank-transaction date

end_datestring · date

Filter: latest bank-transaction date

limitinteger

dry_runboolean

List what would be accepted; change nothing

plan_hashstring

plan_hash of the dry run; refused if the suggestions moved since

Responses

200Successful Response

Schema: SuccessEnvelope_BulkAcceptPaymentSuggestionsResponse_

successboolean
messagestring
codestring
dataBulkAcceptPaymentSuggestionsResponse

400Bad Request - Invalid input

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

401Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

403Forbidden - Insufficient permissions

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

422Validation Error

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

Code samples

POST/api/v1/payment-suggestions/bulk-accept

bash

curl -X POST 'https://api.ondayzero.com/api/v1/payment-suggestions/bulk-accept' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "kind": "invoice"
}'