Submits the batch file process request. Returns the details of the accepted request.
The file is checked in the background. The upload starts as submitted and moves on from there, for example to rejected when rows fail validation. Use Return Batch Upload File Details to follow its status, and download the error file to see why rows failed. A file without the template's header row, including an empty file, is rejected straight away with 400 Invalid Batch Upload Headers.
Optional. The team to work in, using a team id from List Teams. If left out, the default team is used. Records created in a team can only be seen by sending that team's id. A team id that doesn't exist, or a team being deleted, is rejected with 404 Team Not Found.
- Sandbox serverhttps://connect.sandbox.creditsafe.com/v1/compliance/kyc-protect/batchUploads
- Production serverhttps://connect.creditsafe.com/v1/compliance/kyc-protect/batchUploads
curl -i -X POST \
https://connect.sandbox.creditsafe.com/v1/compliance/kyc-protect/batchUploads \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: multipart/form-data' \
-H 'X-Team-Id: 6b78aed4-9ba6-441b-80b9-df9bea3b7c97' \
-F File=@File.binSuccess
Batch upload status
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "filename": "string", "status": "submitted", "rowCount": 0, "successCount": 0, "uploadedAt": "2019-08-24T14:15:22Z", "uploadedById": 0, "uploadedBy": "string", "completedAt": "2019-08-24T14:15:22Z", "correlationId": "string" }