Bulk Approve Vendor Deposits
POST/api/vendor-deposits/bulk-approve
Approve multiple vendor deposits in one operation. Deposit IDs must be unique and refer to existing deposits.
accounting:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
The approvals are processed asynchronously in the background — the endpoint returns 202 Accepted immediately with a tracked_job_log_id you can use to follow progress.
Approval policy: While the vendor-deposit approval policy is enabled each deposit is checked against your eligibility: deposits you cannot approve are skipped with the reason, and deposits where your approval only completed your step are reported as waiting on the next step. Skipped rows appear in the tracked job's result.
Request
Responses
- 202
- 401
- 403
- 422
- 429
Accepted
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.