Send Data to Complete Sign-Up Procedure

This endpoint finalizes the sign-up process for a banking application by submitting data linked to a specific user profile. It completes the user's registration and updates the profile with the provided information upon successful submission. Use this endpoint as the final step in the onboarding flow after all required profile data has been collected.

Endpoint

POST /netevia/submit/{profileId}

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 collecting all required customer information during the onboarding process. It is called once per profile to finalize registration and transition the user from a pending state to an active account. If the submission also triggers account opening, the response will include the new financial account identifier.

Path Parameters

Response

200 OK

The response is one of two schemas depending on whether a financial account was opened as part of the sign-up completion.

BoardingResponse (standard completion):

OpenFinancialAccountResponse (when a financial account is opened):

Extends BoardingResponse with the following additional field:

{
  "profileId": 10482,
  "success": true,
  "errors": null,
  "changeLog": [
    {
      "requestType": 1,
      "changes": "Profile finalized and activated."
    }
  ],
  "financialAccountId": "fa_8b3d92c1e4f5a607"
}

Error Codes

Common Mistakes

• Submitting a profileId that does not exist or belongs to a different partner will result in a 404 error.
• Calling this endpoint before all required onboarding steps are complete may result in a 400 validation error; ensure all prior boarding steps have been successfully submitted first.
• Using an expired Bearer token (lifetime is 10 minutes) will return a 401; refresh the token via POST /api/auth/refresh before retrying.
• Attempting to finalize the same profile more than once may return an error or a no-op; check the success field and errors in the response.

Related Endpoints

• POST /api/auth/v2 — Obtain a Bearer token for authentication
• POST /api/auth/refresh — Refresh an expiring Bearer token
• POST /netevia/profile — Create a new user profile to obtain a profileId before submission

Example

curl -X POST https://api.banking.netevia.dev/netevia/submit/10482 \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"