---
title: Submit a batch of accounts for verification
description: Submit a collection of accounts for batch validation using the DebiPay checks API.
openapi: /openapi/debi-pay-api.yaml POST /api/v1/checks/verify/{batchId}/accounts
---

> **For AI agents:** the complete documentation index is at [llms.txt](/llms.txt). Append `.md` to any page URL for its markdown version.

This operation submits a batch of account verification requests to DebiPay using a batch identifier. It is intended for higher-volume scenarios where you want to validate many accounts together and then retrieve the consolidated results later.

<Info>
Use this endpoint when you already have a batch identifier and want to submit the accounts that belong to that batch for verification.
</Info>

## Typical workflow

1. Create or identify a batch for your verification workload.
2. Submit the accounts that should be validated in that batch.
3. Retrieve the results by calling the batch result endpoint.

## Request details

The path parameter `batchId` identifies the batch being processed. The exact payload structure is defined in the generated request schema in the right panel for your API instance.

## Response handling

The response confirms that the batch submission was accepted and that verification processing can continue. Follow up with the result endpoint to inspect the detailed outcomes.

<Tip>
If you are onboarding a large number of accounts, this endpoint is preferable to single-account verification because it scales better and keeps the checks grouped.
</Tip>

## Related pages

- [Verify a single account](./checks-verify-account)
- [Upload accounts for batch verification](./checks-verify-upload-accounts)
- [Get verification results for a batch](./checks-verification-batch-id-accounts-get)


---

📦 **OpenAPI specs:** Every OpenAPI specification referenced by this documentation is available as a single download — https://mutex-core-apis.jamdesk.app/api-specs.zip