Bulk manually reconcile records
Marks multiple reconciliation records as manually reconciled in a single bulk operation, capturing operator supplied reasons and comments. Records must not already be in a reconciled resolution. The response includes a summary of successes and failures.
Authorizations
You can use an OAuth2 JWT bearer token in the Authorization header of your API requests for supported endpoints: Authorization: Bearer <YOUR_JWT_HERE>.
These tokens are valid for 10 minutes and can be requested via the access token endpoint endpoint.
Body
Payload used to bulk manually reconcile multiple records. Both tagSlugs
and reasons are optional — manual reconciliation can run without any
tags. When both are supplied, tagSlugs is the source of truth and
reasons is ignored. The same tag set applies to every record in the batch.
List of record identifiers to reconcile.
1Slugs of merchant-catalog tags to attach to every record in the batch as part of the reconcile action. Validated against the merchant tag catalog once before any DB write.
Deprecated. Use tagSlugs instead. Existing values continue to work and are coerced into the tag slug list when tagSlugs is empty; they will also be persisted on the published manual-reconciliation-action analytics event so downstream dashboards keep working. This field may be removed in a future major release.
Operator-provided reason for manual reconciliation action.
FEE_ADJUSTMENT, FX_ADJUSTMENT, RECONCILES_WITH_OTHER_TRANSACTIONS, WITHIN_TOLERANCE, SEPARATE_REFUND_OR_VOUCHER_ISSUED, DUPLICATE_RECORD, DATA_ERROR, OTHER Optional operator comments associated with the manual reconciliation.
Response
Bulk reconciliation completed. See response for individual record outcomes.
Response containing the outcome of a bulk manual reconciliation operation.