Send Docs Upload Confirmation
This endpoint is used to confirm the completion of a document upload session in the Netevia Banking platform. When invoked, it finalizes the upload process, signaling the system to begin processing and storing the submitted documents. Once confirmed, the session is marked as finalized and no further uploads can be added to it.
Endpoint
POST /endUploadDocumentSession
Authentication
Bearer token required. Obtain via:
POST https://api.banking.netevia.dev/api/auth/v2
Include in header: Authorization: Bearer {token} Token lifetime: 10 minutes. Refresh via POST /api/auth/refresh.
When to use
Use this endpoint after all documents have been uploaded for a given document upload session. It is typically called at the end of an onboarding or verification flow when all required files (e.g., identity documents, business registration papers) have been submitted. Calling this endpoint triggers downstream processing such as document verification or application approval.
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
| profileId | integer (int32) | No | The ID of the customer profile associated with the document upload session. |
| documentUploadSessionId | string | No | The unique identifier of the document upload session to be finalized. |
| verificatedEntity | string | No | The entity type or identifier being verified as part of this document upload session. |
{
"profileId": 104823,
"documentUploadSessionId": "sess_a1b2c3d4e5f6",
"verificatedEntity": "business"
}Response
200 OK
A 200 status indicates that the document upload session was successfully finalized. The system will proceed with processing and storing the uploaded documents.
{}Error Codes
| Code | When it happens |
|---|---|
| 400 | Missing required fields or validation error |
| 401 | Token missing, expired, or invalid |
| 403 | Insufficient permissions |
| 404 | Resource not found — profile or session ID does not exist |
| 500 | Internal server error |
Common Mistakes
- Calling this endpoint before all intended documents have been uploaded, which permanently closes the session and may result in incomplete document submissions.
- Providing an invalid or already-finalized
documentUploadSessionId, which will result in a 404 or 400 error. - Omitting
profileIdwhen the session is tied to a specific customer profile, causing the system to be unable to associate the documents correctly.
Related Endpoints
POST /startUploadDocumentSession— Initiates a new document upload session and returns adocumentUploadSessionIdto use when uploading files.POST /uploadDocument— Uploads an individual document file within an active session before calling this confirmation endpoint.
Example
curl -X POST https://api.banking.netevia.dev/endUploadDocumentSession \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"profileId": 104823,
"documentUploadSessionId": "sess_a1b2c3d4e5f6",
"verificatedEntity": "business"
}' 200Success
