Send Docs Upload Confirmation

The POST /netevia/endUploadDocumentSession endpoint finalizes a document upload session for business customer boarding. It confirms that all required documents have been submitted, triggers processing and storage of those documents, and closes the session to prevent further modifications. This is the final step in the document submission workflow during business onboarding or account opening.

Endpoint

POST /netevia/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 required documents have been uploaded via the document upload session workflow during business customer boarding. Once called, the session is locked and no further documents can be added or modified. This endpoint should be called once all supporting documents (e.g., business verification, identity documents) have been successfully submitted for the associated profile.

Request Body

{
  "profileId": 100234,
  "documentUploadSessionId": "dus_8f3a2b1c-4d5e-6f7a-8b9c-0d1e2f3a4b5c",
  "verificatedEntity": "Acme Corp LLC"
}

Response

200 OK

The response is one of two possible objects depending on whether the session completion triggers a financial account opening.

BoardingResponse

changeLog item fields:

OpenFinancialAccountResponse (extends BoardingResponse — returned when session finalization triggers a financial account opening)

{
  "profileId": 100234,
  "errors": null,
  "success": true,
  "changeLog": [
    {
      "requestType": 5,
      "changes": "Document upload session finalized for entity Acme Corp LLC"
    }
  ],
  "financialAccountId": "fa_9c8b7a6d-5e4f-3c2b-1a0d-9e8f7c6b5a4d"
}

Error Codes

Common Mistakes

• Calling this endpoint before all required documents have been uploaded — once the session is closed it cannot be reopened.
• Providing a documentUploadSessionId that belongs to a different profileId — the session ID and profile ID must correspond to the same boarding workflow.
• Re-calling this endpoint on an already-finalized session, which will result in an error since the session is already closed.
• Omitting documentUploadSessionId — the system requires a valid session identifier to locate and finalize the correct upload session.

Related Endpoints

• POST /netevia/startUploadDocumentSession — Initiates a document upload session before documents are submitted
• POST /netevia/uploadDocument — Uploads individual documents within an active document upload session
• POST /netevia/boardBusiness — Initiates the business customer boarding process that precedes document upload

Example

curl -X POST https://api.banking.netevia.dev/netevia/endUploadDocumentSession \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "profileId": 100234,
    "documentUploadSessionId": "dus_8f3a2b1c-4d5e-6f7a-8b9c-0d1e2f3a4b5c",
    "verificatedEntity": "Acme Corp LLC"
  }'