Preview a Bulk Beneficiary Import
Upload a CSV file of beneficiaries (individual OR business — one type per
file). The server parses every row, runs the same validation as
POST /v1/beneficiaries, and returns per-row results. No beneficiaries
are created at this phase.
After reviewing the per-row errors, call
POST /v1/beneficiaries/import/{import_id}/confirm to materialize the rows
that passed validation. The preview row TTLs after 24 hours.
Distinct from the POST /v1/batches flow: that endpoint creates
beneficiaries + instruments + payouts in one shot. This endpoint creates
only beneficiaries — for the merchant-portal beneficiary onboarding
surface (ANT-241).
Requires an Idempotency-Key header.
Maximum file size: 8 MB. Only .csv is accepted in v1.
Authorizations
Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.
Headers
Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.
255Body
CSV file matching the individual or business template.
Response
Preview generated with per-row validation results.
Result of POST /v1/beneficiaries/import. Carries the persisted
import_id (which confirm references), top-line counts, and the full
per-row validation outcome so the merchant portal can render inline
per-cell errors.